Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.30 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.32 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.083
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.30 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.32 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
22
11 PASS6 REVIEW2 FIX
D
Third-Party Impact
Action
100% third-party, 0 ms blocking
FIX
100% third-party, 0 ms blocking
Warning::
!
Third-party code accounts for 100% of page weight (446.2 KiB of 446.4 KiB)
Info::
✓
Third-party blocking time is low (0 ms)
100%
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.
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
C
Image Optimization
Action
48 images, 0 KB saveable
REVIEW
48 images, 0 KB saveable
Warning::
!
https://www9.sitiscommesse24.com/wp-content/upload... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www9.sitiscommesse24.com/wp-content/upload... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www9.sitiscommesse24.com/wp-content/upload... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www9.sitiscommesse24.com/wp-content/upload... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://www10.sitiscommesse24.com/wp-content/uploa... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
48images322 KB
0oversized-0 KB
18legacy 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
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
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.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A+
Page Weight Budget
446 KB transferred, 65 requests
PASS
446 KB transferred, 65 requests
Info::
✓
Page weighs 610 KB (446 KB transferred)
Info::
i
65 HTTP requests
Info::
i
Estimated 0.09 g CO2 per page load
446 KBtransferred
65 requests
0.09 g CO2 per page load
Images322.0 KiB72%
Fonts86.0 KiB19%
HTML15.4 KiB3%
CSS14.1 KiB3%
JavaScript6.7 KiB1%
Other2.3 KiB1%
02.4 MB4.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
223ms total JS execution
PASS
223ms total JS execution
Info::
i
https://www10.sitiscommesse24.com/: 169ms CPU time
Info::
i
Unattributable: 54ms CPU time
Warning::
!
Third-party scripts: 169ms (76% of total)
Main Thread Breakdown
Style & Layout 37% Other 37% Script Evaluation 12% Rendering 10% Parse HTML & CSS 3%
Script
Total
Scripting
Parse/Compile
Party
https://www10.sitiscommesse24.com/
169ms
18ms
1ms
3rd
Unattributable
54ms
1ms
0ms
1st
A+
Font Loading
2 fonts (86 KB)
PASS
2 fonts (86 KB)
Info::
i
2 font(s) use font-display: swap (FOUT risk but functional)
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+
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.
Per-script blocking time, transfer cost, and cache headers
INFO
76%of JavaScript execution is third-party
First-party Third-party169ms · 15KB · €1/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www10.sitiscommesse24.com
www10.sitiscommesse24.com
Other
169ms
15 KB
—
€1/mo
Optional
www10.sitiscommesse24.com
Other
Optional
Execution169ms
Transfer15 KB
Monthly Cost€1/mo
76% 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.
375 ms
750 ms
1.1 s
1.5 s