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.
6.97 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
55.11 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.49 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.73 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.
56.10 s
Page Load Progression
FPage Weight BudgetAction11.8 MB transferred, 105 requestsFIX
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
Source: web.dev
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FJS Execution CostAction5528ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://yastatic.net/s3/psf/ps-tuning/common-pc.1e45b69b41aecf712af1.js | 1998ms | 1441ms | 523ms | 3rd |
| Unattributable | 1094ms | 35ms | 0ms | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/7998.d3d7f1021e4ad1213e09.js | 1015ms | 795ms | 1ms | 3rd |
| https://360.yandex.com/disk/ | 921ms | 16ms | 6ms | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/9435.cf948657f883fab60d53.js | 169ms | 140ms | 28ms | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/545.48ea946478be38cf7f97.js | 135ms | 100ms | 23ms | 3rd |
| https://mc.yandex.ru/metrika/tag.js | 134ms | 100ms | 26ms | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/common-pc.1e45b69b41aecf712af1.css | 63ms | 0ms | 0ms | 3rd |
FJS BundlesAction17 scripts, 731 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://yastatic.net/s3/psf/ps-tuning/common-pc.1e45b69b41aecf712af1.js | 905 KB | 547 KB (61%) | ✓ | 3rd |
| https://mc.yandex.ru/metrika/tag.js | 85 KB | 56 KB (66%) | ✓ | 3rd |
| https://mc.yandex.ru/metrika/tag.js | 85 KB | 56 KB (66%) | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/9435.cf948657f883fab60d53.js | 63 KB | 46 KB (74%) | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/545.48ea946478be38cf7f97.js | 49 KB | 27 KB (55%) | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/6006.6a13a365b79f391b4e7f.js | 4 KB | — | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/9833.bf3f976ac955f6a251ec.js | 3 KB | — | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/8246.f5181afe7de4c547503b.js | 5 KB | — | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/4323.0b19336e99130f3b2288.js | 4 KB | — | ✓ | 3rd |
| https://yastatic.net/s3/psf/ps-tuning/7923.5397f92ba7396eaa066c.js | 4 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
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
FPage Weight InventoryAction105 resources · 11.8 MB · 731 KB savings availableFIX
~731.5 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 105 resources | 11.8 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization53 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Performance issues directly impact user engagement and conversion rates.
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading4 fonts (673 KB)PASS
Web fonts
4
673 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
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 ~267 KB and ~534 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall105 requests over 3952msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
yastatic.net yastatic.net | Other | 1998ms | 905 KB | 61% | ₽592/mo | Costly |
Unattributable Unattributable | Other | 1094ms | 0 KB | — | ₽324/mo | Costly |
yastatic.net yastatic.net | Other | 1015ms | 1 KB | — | ₽300/mo | Costly |
360.yandex.com 360.yandex.com | Other | 921ms | 456 KB | — | ₽273/mo | Costly |
yastatic.net yastatic.net | Other | 169ms | 63 KB | 74% | ₽50/mo | Costly |
yastatic.net yastatic.net | Other | 135ms | 49 KB | 55% | ₽40/mo | Optional |
mc.yandex.ru mc.yandex.ru | Other | 134ms | 85 KB | 66% | ₽40/mo | Optional |
yastatic.net yastatic.net | Other | 63ms | 120 KB | — | ₽19/mo | Optional |
These scripts may cost more than they're worth
- yastatic.net adds 1998ms and costs ~₽592/month
- Unattributable adds 1094ms and costs ~₽324/month
- yastatic.net adds 1015ms and costs ~₽300/month
- 360.yandex.com adds 921ms and costs ~₽273/month
- yastatic.net adds 169ms and costs ~₽50/month
100% 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
yastatic.net takes 1998ms 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
61% of yastatic.net'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
Unattributable takes 1094ms 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
yastatic.net takes 1015ms 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
360.yandex.com takes 921ms 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
yastatic.net takes 169ms 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
74% of yastatic.net'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
55% of yastatic.net'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
66% of mc.yandex.ru'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