Performance
· 15 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.57 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.99 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
19 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.055
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.59 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.
2.99 s
Page Load Progression
DPage Weight BudgetAction2.1 MB transferred, 28 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
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DPage Weight InventoryAction28 resources · 2.1 MB · 240 KB savings availableFIX
~240.0 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 28 resources | 2.1 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction5 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
CJS BundlesAction7 scripts, 240 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://cdn.jsdelivr.net/ghost/portal@~2.68/umd/portal.min.js | 436 KB | 91 KB (23%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-LCVWBFR9YN | 155 KB | 66 KB (43%) | ✓ | 3rd |
| https://cdn.jsdelivr.net/ghost/sodo-search@~1.8/umd/sodo-search.min.js | 98 KB | 54 KB (56%) | ✓ | 3rd |
| https://ilya.grigorik.com/assets/js/app.min.js?v=35da3834ca | 58 KB | 28 KB (49%) | ✓ | 3rd |
| https://ilya.grigorik.com/public/cards.min.js?v=35da3834ca | 2 KB | — | ✓ | 3rd |
| https://ilya.grigorik.com/public/member-attribution.min.js?v=35da3834ca | 2 KB | — | ✓ | 3rd |
| https://ilya.grigorik.com/public/ghost-stats.min.js?v=35da3834ca | 13 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
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost390ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://cdn.jsdelivr.net/ghost/portal@~2.68/umd/portal.min.js | 139ms | 76ms | 46ms | 3rd |
| https://ilya.grigorik.com/ | 81ms | 2ms | 1ms | 3rd |
| Unattributable | 57ms | 7ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-LCVWBFR9YN | 57ms | 48ms | 9ms | 3rd |
| https://ilya.grigorik.com/assets/js/app.min.js?v=35da3834ca | 56ms | 34ms | 11ms | 3rd |
A+Font Loading1 fonts (39 KB)PASS
Web fonts
1
39 KB total
Render-blocking
0
of 1
Dominant font-display
swap
Most common across fonts
Font loading timeline
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)
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall28 requests over 1400msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
jsDelivr cdn.jsdelivr.net | CDN | 139ms | 436 KB | 23% | $0/mo | Optional |
ilya.grigorik.com ilya.grigorik.com | Other | 81ms | 19 KB | — | $0/mo | Optional |
Unattributable Unattributable | Other | 57ms | 0 KB | — | $0/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 57ms | 155 KB | 43% | $0/mo | Optional |
ilya.grigorik.com ilya.grigorik.com | Other | 56ms | 58 KB | 49% | $0/mo | Optional |
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