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.
2.56 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.16 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 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.56 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.
3.16 s
Page Load Progression
375 ms
750 ms
1.1 s
1.5 s 1.9 s 2.2 s 2.6 s 3.0 sDThird-Party ImpactAction98% third-party, 0 ms blockingFIX
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization19 images, 0 KB saveableREVIEW
BJS Execution Cost507ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://blog.jp/ | 243ms | 25ms | 1ms | 1st |
| Unattributable | 213ms | 8ms | 0ms | 3rd |
| https://pdn.adingo.jp/p.js | 50ms | 35ms | 7ms | 3rd |
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Page Weight Budget271 KB transferred, 26 requestsPASS
A+Text CompressionAll text resources are compressedPASS
A+Font LoadingNo web fonts (system fonts)PASS
A+JS Bundles2 scripts, 0 KB unusedPASS
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://pdn.adingo.jp/p.js | 21 KB | — | ✓ | 3rd |
| https://cdn.sx.adingo.jp/cb.js | 0 KB | — | ✓ | 3rd |
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints2 hints, 0 missing preconnectsPASS
Current Resource Hints
2 resource hints configured
APage Weight Inventory26 resources · 271 KB · 0 KB savings availablePASS
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 26 resources | 270.9 KiB | ||||||
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall26 requests over 2514msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 213ms | 0 KB | — | ¥295/mo | Costly |
pdn.adingo.jp pdn.adingo.jp | Other | 50ms | 21 KB | — | ¥70/mo | Costly |
These scripts may cost more than they're worth
- Unattributable adds 213ms and costs ~¥295/month
- pdn.adingo.jp adds 50ms and costs ~¥70/month
52% of JavaScript execution time comes from third-party scripts.
Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.
Learn more ▾ ▴
Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.
Source: web.dev / HTTP Archive Web Almanac
Unattributable takes 213ms 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
pdn.adingo.jp takes 50ms 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