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
19 images, 0 KB saveable
REVIEW
19 images, 0 KB saveable
Warning::
!
https://app-assets.project1content.com/tour/assets... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://images-assets.project1content.com/assets/b... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://media-public-ht.project1content.com/m=eeEa... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://images-assets-ht.project1content.com/Mofos... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://app-assets.project1content.com/tour/assets... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://images-assets-ht.project1content.com/Commo... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://images-assets.project1content.com/assets/b... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://media-public-ht.project1content.com/m=eeEa... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static-landing-assets.project1content.com/... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://static-landing-assets.project1content.com/... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
19images2.0 MB
0oversized-0 KB
19legacy format
10missing 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
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
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
i
Main HTML response has no Content-Encoding (uncompressed)
The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.
B
Main HTML Cache-Control
No Cache-Control header on main HTML response
REVIEW
No Cache-Control header on main HTML response
Info::
i
Main HTML response has no Cache-Control header
Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
No Server-Timing header found
Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 JS blocking issue(s) detected
Warning::
!
2 render-blocking <script src> tag(s) without async/defer
Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
Warning::
!
Total JS execution time is 30.0 s -- over the 3.5s budget
Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.
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
3 fonts (87 KB)
PASS
3 fonts (87 KB)
Info::
i
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
87 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
KFOMCnqEu92Fr1ME7kSn66a...woff2swap
Size16 KB
Load time19 ms
Start496 ms
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size37 KB
Load time20 ms
Start497 ms
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size34 KB
Load time28 ms
Start2.2 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)
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+
HTTP/3 (QUIC)
HTTP/3 advertised via Alt-Svc
PASS
HTTP/3 advertised via Alt-Svc
Info::
✓
HTTP/3 (QUIC) is supported
First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
✓
LCP image preload audit not available for this scan
A+
Server Response Intelligence
1 server-response signal(s) detected
PASS
1 server-response signal(s) detected
Info::
i
No `ETag` or `Last-Modified` -- conditional GET not supported
Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.
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+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
✓
No CSS performance depth issues detected
Network Waterfall
109 requests over 4069ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
91%of JavaScript execution is third-party
First-party Third-party27268ms · 2409KB · $362/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
app-assets.project1content.com
app-assets.project1content.com
Other
16303ms
708 KB
56%
$216/mo
Costly
app-assets.project1content.com
app-assets.project1content.com
Other
2991ms
133 KB
50%
$40/mo
Costly
www.gstatic.com
www.gstatic.com
Other
2975ms
0 KB
48%
$39/mo
Costly
www.mofos.com
www.mofos.com
Other
1921ms
75 KB
—
$26/mo
Costly
app-assets.project1content.com
app-assets.project1content.com
Other
1184ms
898 KB
52%
$16/mo
Costly
onenavigation.project1content.com
onenavigation.project1content.com
Other
831ms
195 KB
49%
$11/mo
Costly
onelist.project1content.com
onelist.project1content.com
Other
790ms
384 KB
66%
$10/mo
Costly
www.mofos.com
www.mofos.com
Other
273ms
15 KB
—
$4/mo
Costly
app-assets.project1content.com
Other
Costly
Execution16303ms
Transfer708 KB
Unused56%
Monthly Cost$216/mo
app-assets.project1content.com
Other
Costly
Execution2991ms
Transfer133 KB
Unused50%
Monthly Cost$40/mo
www.gstatic.com
Other
Costly
Execution2975ms
Transfer0 KB
Unused48%
Monthly Cost$39/mo
www.mofos.com
Other
Costly
Execution1921ms
Transfer75 KB
Monthly Cost$26/mo
app-assets.project1content.com
Other
Costly
Execution1184ms
Transfer898 KB
Unused52%
Monthly Cost$16/mo
onenavigation.project1content.com
Other
Costly
Execution831ms
Transfer195 KB
Unused49%
Monthly Cost$11/mo
onelist.project1content.com
Other
Costly
Execution790ms
Transfer384 KB
Unused66%
Monthly Cost$10/mo
www.mofos.com
Other
Costly
Execution273ms
Transfer15 KB
Monthly Cost$4/mo
These scripts may cost more than they're worth
app-assets.project1content.com adds 16303ms and costs ~$216/month
app-assets.project1content.com adds 2991ms and costs ~$40/month
www.gstatic.com adds 2975ms and costs ~$39/month
www.mofos.com adds 1921ms and costs ~$26/month
app-assets.project1content.com adds 1184ms and costs ~$16/month
onenavigation.project1content.com adds 831ms and costs ~$11/month
onelist.project1content.com adds 790ms and costs ~$10/month
www.mofos.com adds 273ms and costs ~$4/month
91% 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
app-assets.project1content.com takes 16303ms 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
56% of app-assets.project1content.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.
Source: web.dev
app-assets.project1content.com takes 2991ms 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 2975ms 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.mofos.com takes 1921ms 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
app-assets.project1content.com takes 1184ms 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
52% of app-assets.project1content.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.
Source: web.dev
onenavigation.project1content.com takes 831ms 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
onelist.project1content.com takes 790ms 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
66% of onelist.project1content.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.
Source: web.dev
www.mofos.com takes 273ms 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.