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.
3.36 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.54 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
22 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.057
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.77 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.
7.54 s
Page Load Progression
FPage Weight BudgetAction3.8 MB transferred, 130 requestsFIX
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
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
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
DPage Weight InventoryAction130 resources · 3.8 MB · 36 KB savings availableFIX
~36.3 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 130 resources | 3.8 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization72 images, 0 KB saveableREVIEW
CJS Execution CostAction1168ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.tistory.com/_next/static/chunks/6577-a1b69c920e4c21fc.js | 912ms | 459ms | 7ms | 3rd |
| https://www.tistory.com/ | 131ms | 1ms | 1ms | 3rd |
| Unattributable | 126ms | 6ms | 0ms | 3rd |
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 Loading1 fonts (1999 KB)PASS
Web fonts
1
1999 KB total
Render-blocking
0
of 1
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 ~1000 KB and ~2000 ms
A+JS Bundles31 scripts, 36 KB unusedPASS
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.tistory.com/_next/static/chunks/6577-a1b69c920e4c21fc.js | 94 KB | 36 KB (39%) | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/7197-a591224da3d640a3.js | 29 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/8941-91cdc0076b398122.js | 4 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/52774a7f-e9ce7c41311a062a.js | 38 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/fd9d1056-9eb7428098c010a8.js | 53 KB | — | ✓ | 3rd |
| https://t1.kakaocdn.net/kakao_js_sdk/2.7.3/kakao.min.js | 27 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/main-app-4efe8cc02ce86f84.js | 1 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/1589-547d8038de15aa62.js | 4 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/1632-2931d458da1ab461.js | 7 KB | — | ✓ | 3rd |
| https://www.tistory.com/_next/static/chunks/3464-512b3c2f6a51976a.js | 20 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
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall130 requests over 13610msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.tistory.com www.tistory.com | Other | 912ms | 94 KB | 39% | ₩3600/mo | Costly |
www.tistory.com www.tistory.com | Other | 131ms | 12 KB | — | ₩515/mo | Costly |
Unattributable Unattributable | Other | 126ms | 0 KB | — | ₩496/mo | Costly |
These scripts may cost more than they're worth
- www.tistory.com adds 912ms and costs ~₩3600/month
- www.tistory.com adds 131ms and costs ~₩515/month
- Unattributable adds 126ms and costs ~₩496/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
www.tistory.com takes 912ms 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
www.tistory.com takes 131ms 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
Unattributable takes 126ms 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