Performance
· 17 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.79 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.72 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
107 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.21 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
6.75 s
Page Load Progression
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BThird-Party Impact56% third-party, 0 ms blockingREVIEW
BJS Execution Cost700ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| Unattributable | 181ms | 60ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-C9NP8Z7Z5F&cx=c&_slc=1 | 170ms | 128ms | 41ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-N8R3VWS | 143ms | 102ms | 27ms | 3rd |
| https://www.google-analytics.com/analytics.js | 86ms | 71ms | 4ms | 3rd |
| https://icq.com/mobile/en | 60ms | 3ms | 0ms | 1st |
| https://icq.com/cached/js/landing/mobile.min.js | 59ms | 43ms | 10ms | 1st |
CJS BundlesAction4 scripts, 152 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtm.js?id=GTM-N8R3VWS | 124 KB | 65 KB (52%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-C9NP8Z7Z5F&cx=c&_slc=1 | 150 KB | 64 KB (43%) | ✓ | 3rd |
| https://icq.com/cached/js/landing/mobile.min.js | 38 KB | 24 KB (65%) | ✓ | 1st |
| https://www.google-analytics.com/analytics.js | 21 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Page Weight Budget535 KB transferred, 21 requestsPASS
A+Text CompressionAll text resources are compressedPASS
AImage Optimization3 images, 0 KB saveablePASS
A+Font Loading2 fonts (157 KB)PASS
Web fonts
2
157 KB total
Render-blocking
0
of 2
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Convert to woff2 for ~30% smaller file size
- Convert to woff2 for ~30% smaller file size
Optimization checklist
- Preload critical fonts (priority=high)
- Use woff2 format for all fonts
- Set font-display to swap, optional, or fallback
- Subset large fonts (≤100 KB each)
Fixing the unchecked items could save ~47 KB and ~94 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
APage Weight Inventory21 resources · 535 KB · 152 KB savings availablePASS
~152.2 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 21 resources | 534.6 KiB | ||||||
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall21 requests over 1097msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 181ms | 0 KB | — | ₽54/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 170ms | 150 KB | 43% | ₽50/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 143ms | 124 KB | 52% | ₽42/mo | Optional |
Google Analytics www.google-analytics.com | Analytics | 86ms | 21 KB | — | ₽25/mo | Optional |
These scripts may cost more than they're worth
- Unattributable adds 181ms and costs ~₽54/month
- Google Tag Manager adds 170ms and costs ~₽50/month
83% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev
Unattributable takes 181ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 170ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
52% of Google Tag Manager's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev