Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
C
Image Optimization
Action
44 images, 0 KB saveable
REVIEW
44 images, 0 KB saveable
Warning::
!
https://www.ocn.ne.jp/top_tools/center/online_shop... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www.ocn.ne.jp/top_tools/center/online_shop... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www.ocn.ne.jp/ocn_assets/sp/img/_smp02/ocn... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www.ocn.ne.jp/ocn_assets/sp/img/241101_doc... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www.ocn.ne.jp/top_tools/center/online_shop... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
44images2.5 MB
0oversized-0 KB
30legacy format
5missing dimensionsCLS risk
Set explicit width and height to prevent CLS.
Why this matters
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.
Why this matters
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.
Why this matters
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.
Why this matters
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.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
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+
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+
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+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
Network Waterfall
67 requests over 2168ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100%of JavaScript execution is third-party
First-party Third-party3448ms · 798KB · ¥4765/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.ocn.ne.jp
www.ocn.ne.jp
Other
1185ms
54 KB
—
¥1637/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
580ms
134 KB
45%
¥801/mo
Costly
Unattributable
Unattributable
Other
451ms
0 KB
—
¥623/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
326ms
151 KB
43%
¥450/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
261ms
133 KB
48%
¥361/mo
Costly
www.ocn.ne.jp
www.ocn.ne.jp
Other
232ms
32 KB
—
¥321/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
229ms
151 KB
50%
¥316/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
184ms
144 KB
51%
¥255/mo
Costly
www.ocn.ne.jp
Other
Costly
Execution1185ms
Transfer54 KB
Monthly Cost¥1637/mo
Google Tag Manager
Tag Manager
Costly
Execution580ms
Transfer134 KB
Unused45%
Monthly Cost¥801/mo
Unattributable
Other
Costly
Execution451ms
Transfer0 KB
Monthly Cost¥623/mo
Google Tag Manager
Tag Manager
Costly
Execution326ms
Transfer151 KB
Unused43%
Monthly Cost¥450/mo
Google Tag Manager
Tag Manager
Costly
Execution261ms
Transfer133 KB
Unused48%
Monthly Cost¥361/mo
www.ocn.ne.jp
Other
Costly
Execution232ms
Transfer32 KB
Monthly Cost¥321/mo
Google Tag Manager
Tag Manager
Costly
Execution229ms
Transfer151 KB
Unused50%
Monthly Cost¥316/mo
Google Tag Manager
Tag Manager
Costly
Execution184ms
Transfer144 KB
Unused51%
Monthly Cost¥255/mo
These scripts may cost more than they're worth
www.ocn.ne.jp adds 1185ms and costs ~¥1637/month
Google Tag Manager adds 580ms and costs ~¥801/month
Unattributable adds 451ms and costs ~¥623/month
Google Tag Manager adds 326ms and costs ~¥450/month
Google Tag Manager adds 261ms and costs ~¥361/month
www.ocn.ne.jp adds 232ms and costs ~¥321/month
Google Tag Manager adds 229ms and costs ~¥316/month
Google Tag Manager adds 184ms and costs ~¥255/month
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
Why this matters
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.ocn.ne.jp takes 1185ms 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
Google Tag Manager takes 580ms 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
Unattributable takes 451ms 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
Google Tag Manager takes 326ms 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
Google Tag Manager takes 261ms 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
www.ocn.ne.jp takes 232ms 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
Google Tag Manager takes 229ms 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
Google Tag Manager takes 184ms 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
51% of Google Tag Manager's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.