Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
Why this matters
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
i
HTTP/3 (QUIC) is not advertised
HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.
C
Document Compression
Action
Document response served uncompressed
REVIEW
Document 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.
C
Asset Compression
Action
1 of 3 asset hosts serve text uncompressed
REVIEW
1 of 3 asset hosts serve text uncompressed
Info::
✓
s1.wp.com serves assets with brotli (assets: 8)
Got: s1.wp.com (text/css)
Warning::
!
fonts.googleapis.com serves text assets uncompressed (assets: 4)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Got: fonts.googleapis.com (text/css)
Info::
i
bat.bing.com serves assets with gzip; brotli would be ~20% smaller (assets: 3)
Every current browser accepts brotli. On a CDN this is a per-pull-zone toggle (Cloudflare, Fastly, CloudFront, CDN77, Bunny all expose it); on an origin it needs the brotli module (nginx-brotli, Apache mod_brotli). The saving lands on the assets this host serves, not on the HTML document -- the document's own encoding is reported separately.
Got: bat.bing.com (application/javascript)
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.
Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.
Info::
i
1 `@import` rule(s) in inline `<style>` blocks -- chains an extra round-trip
Each `@import` in CSS forces a serial dependency: the parent stylesheet must download and parse before the browser even knows which URL to fetch next. This used to be catastrophic on HTTP/1.1; HTTP/2 and HTTP/3 multiplexing make it less painful but still strictly worse than declaring `<link rel="stylesheet">` siblings. Replace `@import url(...)` with `<link rel="stylesheet" href="...">` in HTML so the browser discovers and fetches in parallel.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A
Page Weight Budget
801 KB transferred, 45 requests
PASS
801 KB transferred, 45 requests
Info::
✓
Page weighs 2.7 MB (801 KB transferred)
Warning::
!
JavaScript is 671 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 671 KB
Info::
✓
45 HTTP requests
Info::
i
Estimated 0.16 g CO2 per page load
801 KBtransferred
45 requests
0.16 g CO2 per page load
JavaScript670.8 KiB84%
CSS90.0 KiB11%
HTML30.1 KiB4%
Other6.4 KiB1%
Other1.7 KiB0%
Images1.3 KiB0%
Other556 B0%
02.4 MB4.9 MB
Under budget
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Why this matters
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
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
2 hints, 0 missing preconnects
PASS
2 hints, 0 missing preconnects
Info::
✓
Page uses 2 resource hint(s)
Current Resource Hints
preconnect—
preload—
dns-prefetch
2
prefetch—
2 resource hints configured
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-Timing Observability
3 Server-Timing entries advertised
PASS
3 Server-Timing entries advertised
Info::
✓
Server-Timing header advertises 3 timing entries
A+
Server Response Intelligence
2 server-response signal(s) detected
PASS
2 server-response signal(s) detected
Info::
✓
`Vary` header declared: Cookie
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
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
JavaScript Blocking
1 JS blocking issue(s) detected
PASS
1 JS blocking issue(s) detected
Warning::
!
3 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.
Network Waterfall
45 requests over 1448ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
89%of JavaScript execution is third-party
First-party Third-party2612ms · 643KB · $15/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
wordpress.com
wordpress.com
Other
704ms
30 KB
—
$4/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
533ms
184 KB
37%
$3/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
517ms
156 KB
37%
$3/mo
Costly
Facebook Pixel
connect.facebook.net
Advertising
318ms
93 KB
36%
$2/mo
Costly
Facebook Pixel
connect.facebook.net
Advertising
237ms
112 KB
35%
$1/mo
Costly
wordpress.com
wordpress.com
Other
145ms
42 KB
66%
$1/mo
Optional
cdn.parsely.com
cdn.parsely.com
Other
97ms
22 KB
—
$1/mo
Optional
s0.wp.com
s0.wp.com
Other
62ms
4 KB
—
$0/mo
Optional
wordpress.com
Other
Costly
Execution704ms
Transfer30 KB
Monthly Cost$4/mo
Google Tag Manager
Tag Manager
Costly
Execution533ms
Transfer184 KB
Unused37%
Monthly Cost$3/mo
Google Tag Manager
Tag Manager
Costly
Execution517ms
Transfer156 KB
Unused37%
Monthly Cost$3/mo
Facebook Pixel
Advertising
Costly
Execution318ms
Transfer93 KB
Unused36%
Monthly Cost$2/mo
Facebook Pixel
Advertising
Costly
Execution237ms
Transfer112 KB
Unused35%
Monthly Cost$1/mo
wordpress.com
Other
Optional
Execution145ms
Transfer42 KB
Unused66%
Monthly Cost$1/mo
cdn.parsely.com
Other
Optional
Execution97ms
Transfer22 KB
Monthly Cost$1/mo
s0.wp.com
Other
Optional
Execution62ms
Transfer4 KB
Monthly Cost$0/mo
These scripts may cost more than they're worth
wordpress.com adds 704ms and costs ~$4/month
Google Tag Manager adds 533ms and costs ~$3/month
Google Tag Manager adds 517ms and costs ~$3/month
Facebook Pixel adds 318ms and costs ~$2/month
Facebook Pixel adds 237ms and costs ~$1/month
89% 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
wordpress.com takes 704ms 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 533ms 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 517ms 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
Facebook Pixel takes 318ms 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
Facebook Pixel takes 237ms 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 wordpress.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.