Performance

· 22 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

Best Practices

SEO

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

811 ms

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

1.34 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.014

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

1.99 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.34 s

Page Load Progression

454 ms

908 ms

1.4 s

1.8 s

2.3 s

2.7 s

3.2 s

3.6 s

Checks

13 PASS 6 REVIEW 1 FIX

HTTP Caching

Action

No cache headers

FIX

No cache headers

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.

Image Optimization

4 images, 0 KB saveable

REVIEW

4 images, 0 KB saveable

https://vernucciobeverage.it/wp-content/uploads/20... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

4 images 9 KB

0 oversized -0 KB

3 legacy format

1 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

JS Execution Cost

775ms total JS execution

REVIEW

775ms total JS execution

https://vernucciobeverage.it/wp-content/plugins/re...: 408ms CPU time

https://vernucciobeverage.it/wp-includes/js/jquery...: 132ms CPU time

https://vernucciobeverage.it/: 113ms CPU time

https://vernucciobeverage.it/wp-content/plugins/js...: 70ms CPU time

Unattributable: 52ms CPU time

Main Thread Breakdown

Script Evaluation 37% Style & Layout 29% Other 24% Rendering 5%

Script	Total	Scripting	Parse/Compile	Party
https://vernucciobeverage.it/wp-content/plugins/revslider/public/assets/js/revolution.tools.min.js?ver=6.0	408ms	147ms	3ms	1st
https://vernucciobeverage.it/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp	132ms	98ms	2ms	1st
https://vernucciobeverage.it/	113ms	26ms	3ms	1st
https://vernucciobeverage.it/wp-content/plugins/js_composer/assets/lib/bower/skrollr/dist/skrollr.min.js?ver=6.0.5	70ms	13ms	0ms	1st
Unattributable	52ms	1ms	0ms	1st

HTTP/3 (QUIC)

HTTP/3 not advertised

REVIEW

HTTP/3 not advertised

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.

Asset Compression

1 of 1 asset host serve text uncompressed

REVIEW

1 of 1 asset host serve text uncompressed

fonts.googleapis.com serves text assets uncompressed (assets: 6)

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)

Main HTML Cache-Control

No Cache-Control header on main HTML response

REVIEW

No Cache-Control header on main HTML response

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.

Green Hosting

Action

Whether the site is served from green-energy infrastructure

REVIEW

Green Hosting

No green hosting detected

Page Weight Budget

814 KB transferred, 48 requests

PASS

814 KB transferred, 48 requests

Page weighs 2.4 MB (814 KB transferred)

Fonts are 239 KB — consider subsetting or using system fonts

Subset fonts to include only used characters, or switch to system font stacks.

Got: 239 KB

48 HTTP requests

Estimated 0.17 g CO2 per page load

814 KB transferred

48 requests

0.17 g CO2 per page load

Fonts 238.9 KiB 29%

JavaScript 238.5 KiB 29%

Images 217.8 KiB 27%

CSS 104.3 KiB 13%

HTML 13.5 KiB 2%

Other 1.1 KiB 0%

0 2.4 MB 4.9 MB

Under budget

Subset fonts to include only used characters, or switch to system font stacks.

Why this matters

Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).

Source: web.dev font loading

A+

Third-Party Impact

14% third-party, 0 ms blocking

PASS

14% third-party, 0 ms blocking

Third-party code accounts for 14% of page weight (112.5 KiB of 814.1 KiB)

Third-party blocking time is low (0 ms)

86%

First-party Third-party

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

6 fonts (239 KB)

PASS

6 fonts (239 KB)

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

Web fonts

239 KB total

Render-blocking

of 6

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

1Ptug8zYS_SKggPNyC0IT4t... woff2 swap

Size 42 KB

Load time 39 ms

Start 990 ms