speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

chocolatesculptress.com

https://chocolatesculptress.com/

99 96 100 92 –CWV 5AXE

Data from Aug 20, 2026, 4:37 PM UTC — 26h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 26h

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Astro 5.7.13 Built with Astro 5.7.13
Netlify Hosted by Netlify

Scores

99
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.13 s — — 2.13 s 2.13 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 28 ms — — 28 ms 28 ms
FCP First Contentful Paint 850 ms — — 850 ms 850 ms
Speed Index 850 ms — — 850 ms 850 ms
TTFB Time to First Byte 636 ms — — 636 ms 636 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 82 ms
time to first byte 37 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 645.7 kB — — 645.7 kB 645.7 kB
Requests 19 — — 19 19
Third-party Weight 527.9 kB — — 527.9 kB 527.9 kB
Third-party CPU 42 ms — — 42 ms 42 ms
Unused JS 72.6 kB — — 72.6 kB 72.6 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 501.9 kB · 8 req
script 131.8 kB · 6 req
stylesheet 6.0 kB · 1 req
document 4.9 kB · 1 req
other 1.2 kB · 2 req
third party 527.9 kB · 13 req

Third parties 2 entities

527.9 kB transferred, 42 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Cloudinary 400.8 kB · 0 ms CPU
posthog.com 127.1 kB · 42 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 434 ms — — 434 ms 434 ms
Long Tasks 2 — — 2 2
DOM Elements 147 — — 147 147
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 5 — — 5 5
A11y Failures 1 — — 1 1
A11y Failing Nodes 5 — — 5 5

Main thread work

script evaluation 165 ms
other 120 ms
style layout 94 ms
script parse compile 36 ms
paint composite render 11 ms
parse HTML 10 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 1 rule, 334 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 5 nodes

Accessibility failures 1 of 24 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 5 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 4:37 PM UTC 99 2.13 s 0 28 ms 645.7 kB 3/3 ±9 3,327 24.4s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show chocolatesculptress.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site! 

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://chocolatesculptress.com/"></speedlify-score>