Performance

· 23 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop

Performance

Accessibility

100

Best Practices

100

SEO

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.18 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.95 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.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.38 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.96 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

14 PASS 5 REVIEW 1 FIX

Third-Party Impact

Action

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (761.3 KiB of 761.9 KiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

Image Optimization

Action

125 images, 0 KB saveable

REVIEW

125 images, 0 KB saveable

https://www.sitiscommesse.com/immagini/migliori-si... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

https://www.sitiscommesse.com/immagini/authors/den... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

125 images 404 KB

0 oversized -0 KB

43 legacy format

2 missing dimensions CLS 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

JS Execution Cost

Action

1393ms total JS execution

REVIEW

1393ms total JS execution

https://www.sitiscommesse.com/: 1004ms CPU time

Unattributable: 329ms CPU time

https://www.sitiscommesse.com/wp-content/themes/ge...: 60ms CPU time

Third-party scripts: 1064ms (76% of total)

Main Thread Breakdown

Style & Layout 47% Other 33% Rendering 8% Script Evaluation 8% Parse HTML & CSS 4%

Script	Total	Scripting	Parse/Compile	Party
https://www.sitiscommesse.com/	1004ms	57ms	9ms	3rd
Unattributable	329ms	5ms	0ms	1st
https://www.sitiscommesse.com/wp-content/themes/generel/minified/js/functions-f501d7aac58b120d753532adfd30f5e9.js?version=1790852346	60ms	29ms	3ms	3rd

Document Compression

Action

Document response served uncompressed

REVIEW

Document response served uncompressed

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.

Server-Timing Observability

No Server-Timing header found

REVIEW

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.

HTTP Caching

no-cache

REVIEW

no-cache

Cache-Control header is set

Got: no-cache

No ETag or Last-Modified header

Conditional requests (304 Not Modified) are not possible without validators.

Cache-Control

no-cache

Directive	Value	Meaning
no-cache	—	Cache but always revalidate first

Page Weight Budget

762 KB transferred, 147 requests

PASS

762 KB transferred, 147 requests

Page weighs 1.9 MB (762 KB transferred)

147 HTTP requests — consider bundling or reducing

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Estimated 0.16 g CO2 per page load

762 KB transferred

147 requests

0.16 g CO2 per page load

Images 404.5 KiB 53%

Fonts 131.8 KiB 17%

HTML 109.8 KiB 14%

CSS 59.3 KiB 8%

JavaScript 53.1 KiB 7%

Other 1.8 KiB 0%

Other 1.7 KiB 0%

0 2.4 MB 4.9 MB

Under budget

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Why this matters

High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.

Source: web.dev

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

9 fonts (132 KB)

PASS

9 fonts (132 KB)

9 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

132 KB total

Render-blocking

of 9

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

saira-condensed-v6-lati... woff2 swap

Size 17 KB

Load time 22 ms

Start 676 ms