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
14 images, 0 KB saveable
REVIEW
14 images, 0 KB saveable
Warning::
!
https://opensource.google/static/images/featured-b... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://opensource.google/static/images/featured-e... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://opensource.google/static/images/programs/G... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://opensource.google/static/images/home-proje... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://opensource.google/static/images/os-anim-ma... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
14images1.1 MB
0oversized-0 KB
10legacy 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
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
3 fonts (198 KB)
PASS
3 fonts (198 KB)
Info::
i
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
198 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
4UasrENHsxJlGDuGo1OIlJf...woff2swap
Size35 KB
Load time85 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
flUhRq6tzZclQEJ-Vdg-Iui...woff2swap
Size126 KB
Load time98 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size37 KB
Load time84 ms
Start1.1 s
RiskFOUT — text flashes from fallback to web font
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 ~63 KB and ~126 ms
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
3 hints, 0 missing preconnects
PASS
3 hints, 0 missing preconnects
Info::
✓
Page uses 3 resource hint(s)
Current Resource Hints
preconnect
3
preload—
dns-prefetch—
prefetch—
3 resource hints configured
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
A+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Google Cloud
Network Waterfall
70 requests over 3054ms
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-party2391ms · 653KB · €38/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
opensource.google
opensource.google
Other
832ms
15 KB
—
€13/mo
Costly
Unattributable
Unattributable
Other
523ms
0 KB
—
€8/mo
Costly
www.gstatic.com
www.gstatic.com
Other
262ms
58 KB
48%
€4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
260ms
143 KB
43%
€4/mo
Costly
www.gstatic.com
www.gstatic.com
Other
236ms
303 KB
54%
€4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
183ms
132 KB
46%
€3/mo
Optional
www.gstatic.com
www.gstatic.com
Other
96ms
2 KB
—
€2/mo
Optional
opensource.google
Other
Costly
Execution832ms
Transfer15 KB
Monthly Cost€13/mo
Unattributable
Other
Costly
Execution523ms
Transfer0 KB
Monthly Cost€8/mo
www.gstatic.com
Other
Costly
Execution262ms
Transfer58 KB
Unused48%
Monthly Cost€4/mo
Google Tag Manager
Tag Manager
Costly
Execution260ms
Transfer143 KB
Unused43%
Monthly Cost€4/mo
www.gstatic.com
Other
Costly
Execution236ms
Transfer303 KB
Unused54%
Monthly Cost€4/mo
Google Tag Manager
Tag Manager
Optional
Execution183ms
Transfer132 KB
Unused46%
Monthly Cost€3/mo
www.gstatic.com
Other
Optional
Execution96ms
Transfer2 KB
Monthly Cost€2/mo
These scripts may cost more than they're worth
opensource.google adds 832ms and costs ~€13/month
Unattributable adds 523ms and costs ~€8/month
www.gstatic.com adds 262ms and costs ~€4/month
Google Tag Manager adds 260ms and costs ~€4/month
www.gstatic.com adds 236ms and costs ~€4/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
opensource.google takes 832ms 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 523ms 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.gstatic.com takes 262ms 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 260ms 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.gstatic.com takes 236ms 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
54% of www.gstatic.com'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.