Skip to content
https://blog.jp

Performance

· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
91
GRADE
A
FIX
2
REVIEW
2
PASS
9
INFO
2

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

93
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
57
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.21 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.29 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.

1.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.

1.29 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 s
Checks
15
9 PASS 2 REVIEW 2 FIX
D
Third-Party Impact
Action
98% third-party, 0 ms blocking
FIX
98% third-party, 0 ms blocking
Warning::
Third-party code accounts for 98% of page weight (266.8 KiB of 270.9 KiB)
Info::
Third-party blocking time is low (0 ms)
98%
First-party Third-party
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
No Cache-Control header found
Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
Info::
Last-Modified header present

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

B
Image Optimization
19 images, 0 KB saveable
REVIEW
19 images, 0 KB saveable
Info::
All images are well-optimized
19 images 182 KB
0 oversized -0 KB
19 legacy format
0 missing dimensions CLS risk
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
271 KB transferred, 26 requests
PASS
271 KB transferred, 26 requests
Info::
Page weighs 605 KB (271 KB transferred)
Info::
26 HTTP requests
Info::
Estimated 0.06 g CO2 per page load
271 KB / 2.4 MB budget
271 KB transferred
26 requests
0.06 g CO2 per page load
Images 182.3 KiB 67%
CSS 45.5 KiB 17%
JavaScript 20.7 KiB 8%
Other 16.9 KiB 6%
HTML 4.2 KiB 2%
Other 1.1 KiB 0%
Other 206 B 0%
0 2.4 MB 4.9 MB
Under budget
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
All text resources are compressed
All text resources are properly compressed.
A+
JS Execution Cost
116ms total JS execution
PASS
116ms total JS execution
Info::
https://blog.jp/: 65ms CPU time
Info::
Unattributable: 51ms CPU time
Info::
Third-party scripts: 51ms (44% of total)

Main Thread Breakdown

Style & Layout 40% Other 39% Script Evaluation 13% Parse HTML & CSS 4%
ScriptTotalScriptingParse/CompileParty
https://blog.jp/65ms6ms0ms1st
Unattributable51ms1ms0ms3rd
A+
Font Loading
No web fonts (system fonts)
PASS
No web fonts (system fonts)
Info::
No web fonts loaded — system fonts are fastest
No web fonts loaded — system fonts are optimal.
A+
JS Bundles
2 scripts, 0 KB unused
PASS
2 scripts, 0 KB unused
0 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://pdn.adingo.jp/p.js21 KB3rd
https://cdn.sx.adingo.jp/cb.js0 KB3rd
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
No resource hint issues
A
Page Weight Inventory
26 resources · 271 KB · 0 KB savings available
PASS
26 resources · 271 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 271 KB
Warning::
25 third-party resources (98% of weight)
26 resources · 270.9 KiB · 25 third-party Within 1MB page-weight target
Image 74% · 199.4 KiB
CSS 17% · 45.5 KiB
JavaScript 8% · 20.7 KiB
Document 2% · 4.2 KiB
Other 0% · 1.1 KiB
Network Waterfall
26 requests over 2330ms
INFO
0 ms 500 ms 1.0 s 1.5 s 2.0 s FCP 1.2 s LCP 1.3 shttps://blog.jp// https://blog.jp/ — 200 — 4.2 KiB — 773 ms — http/1.1https://parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20240325parts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20240325 — 200 — 45.5 KiB — 74 ms — h2https://parts.blog.livedoor.jp/img/common/logo_w.svgparts.blog.livedoor.jp/img/common/l... https://parts.blog.livedoor.jp/img/common/logo_w.svg — 200 — 3.8 KiB — 93 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/h2_bg.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/h2_bg.svg — 200 — 5.3 KiB — 75 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_01.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_01.svg — 200 — 2.9 KiB — 68 ms — h2https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp.png — 200 — 77.7 KiB — 82 ms — h2https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_ios.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_ios.png — 200 — 5.1 KiB — 82 ms — h2https://pdn.adingo.jp/p.jspdn.adingo.jp/p.js https://pdn.adingo.jp/p.js — 200 — 20.7 KiB — 60 ms — h2https://parts.blog.livedoor.jp/img/common/logo.svgparts.blog.livedoor.jp/img/common/l... https://parts.blog.livedoor.jp/img/common/logo.svg — 200 — 3.6 KiB — 26 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_01.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_01.svg — 200 — 1.5 KiB — 35 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_02.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_02.svg — 200 — 1.4 KiB — 27 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_02.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_02.svg — 200 — 1.8 KiB — 28 ms — h2https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_android.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_android.png — 200 — 11.4 KiB — 36 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_03.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_03.svg — 200 — 2.4 KiB — 37 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_04.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_04.svg — 200 — 2.5 KiB — 29 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/iphone_02.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/iphone_02.png — 200 — 43.6 KiB — 31 ms — h2https://parts.blog.livedoor.jp/img/common/logo_posted_app.pngparts.blog.livedoor.jp/img/common/l... https://parts.blog.livedoor.jp/img/common/logo_posted_app.png — 200 — 3.4 KiB — 38 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_ios.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_ios.png — 200 — 4.2 KiB — 32 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_android.pngparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_android.png — 200 — 5.5 KiB — 33 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_05.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_05.svg — 200 — 1.5 KiB — 39 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_06.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_06.svg — 200 — 1.5 KiB — 38 ms — h2https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_07.svgparts.blog.livedoor.jp/blog_portal/... https://parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_07.svg — 200 — 3.2 KiB — 40 ms — h2https://cdn.sx.adingo.jp/cb.jscdn.sx.adingo.jp/cb.js https://cdn.sx.adingo.jp/cb.js — -1 — 0 B — 190 ms — https://sh.adingo.jp/p/?G=1000142573&href=https%3A%2F%2Fblog.jp%2F&R=&serial=24377011430198&guid=ON&kv=%7B%22page_title%22%3A%5B%22%E3%81%AF%E3%81%98%E3%82%81%E3%81%A6%E3%82%AC%E3%82%A4%E3%83%89%20-%20%E3%83%A9%E3%82%A4%E3%83%96%E3%83%89%E3%82%A2%E3%83%96%E3%83%AD%E3%82%B0%22%5D%7D&api=2&protocols=2%2C3%2C5%2C6&mimes=application%2Fjavascript%2Cvideo%2Fmp4%2Cvideo%2Fogg%2Cvideo%2Fwebm&fluct_uid=e69f7afc-67b2-42f3-8c65-4210d0c153e1&ch_pv=10.15.7sh.adingo.jp/p/?G=1000142573&href=h... https://sh.adingo.jp/p/?G=1000142573&href=https%3A%2F%2Fblog.jp%2F&R=&serial=24377011430198&guid=ON&kv=%7B%22page_title%22%3A%5B%22%E3%81%AF%E3%81%98%E3%82%81%E3%81%A6%E3%82%AC%E3%82%A4%E3%83%89%20-%20%E3%83%A9%E3%82%A4%E3%83%96%E3%83%89%E3%82%A2%E3%83%96%E3%83%AD%E3%82%B0%22%5D%7D&api=2&protocols=2%2C3%2C5%2C6&mimes=application%2Fjavascript%2Cvideo%2Fmp4%2Cvideo%2Fogg%2Cvideo%2Fwebm&fluct_uid=e69f7afc-67b2-42f3-8c65-4210d0c153e1&ch_pv=10.15.7 — 200 — 1.1 KiB — 688 ms — h2https://parts.blog.livedoor.jp/favicon.icoparts.blog.livedoor.jp/favicon.ico https://parts.blog.livedoor.jp/favicon.ico — 200 — 16.9 KiB — 20 ms — h2https://i.adingo.jp/?p=e8S9uW8zuYqSYMmC3GADbHnZ5a3XdA8mAw0QO2f-lNwDlzJhx7IWob6NkAjhi7khVMu6PElj_BldHdWZYjSwi_AWmZazWW8SrczqC9jGljXKxTi_guIWSRv2nJWyhyar_aBxxbrXC38bPIMHjlOsJrzR1MAK8ASaotTa7U9uZPRni3WnMJlmYpD-WSStavdmU1pdSbCvj0qPSN2W1rVKRy6WHDT_umS5uLmku0l7Nw2BHvzIkJa12YnjUwOYQZUp7fUBQInfBwjGC_sycypc5Ap3TooIXAm6OV8RKQ_vSd3rApKlZX3-hYGgoxTt7w4CRtZC8hRDzET7BG-kXN7e-gkcia8Qr1EDPmBmeCR_uU3aj0wC9KAgjmdROPCxLZ8ftN5JxdI8&k=3&v=UYpIYXrAkc3JL0fwi.adingo.jp/?p=e8S9uW8zuYqSYMmC3GAD... https://i.adingo.jp/?p=e8S9uW8zuYqSYMmC3GADbHnZ5a3XdA8mAw0QO2f-lNwDlzJhx7IWob6NkAjhi7khVMu6PElj_BldHdWZYjSwi_AWmZazWW8SrczqC9jGljXKxTi_guIWSRv2nJWyhyar_aBxxbrXC38bPIMHjlOsJrzR1MAK8ASaotTa7U9uZPRni3WnMJlmYpD-WSStavdmU1pdSbCvj0qPSN2W1rVKRy6WHDT_umS5uLmku0l7Nw2BHvzIkJa12YnjUwOYQZUp7fUBQInfBwjGC_sycypc5Ap3TooIXAm6OV8RKQ_vSd3rApKlZX3-hYGgoxTt7w4CRtZC8hRDzET7BG-kXN7e-gkcia8Qr1EDPmBmeCR_uU3aj0wC9KAgjmdROPCxLZ8ftN5JxdI8&k=3&v=UYpIYXrAkc3JL0fw — 200 — 206 B — 681 ms — h2
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
44% of JavaScript execution is third-party
First-party Third-party 51ms · 0KB · ¥70/mo
Unattributable
Other
Costly
Execution 51ms
Transfer 0 KB
Monthly Cost ¥70/mo

These scripts may cost more than they're worth

  • Unattributable adds 51ms and costs ~¥70/month

44% of JavaScript execution time comes from third-party scripts.

Why this matters

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 51ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback