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 ·

clioandcalliope.com

https://clioandcalliope.com/

85 96 96 91 –CWV 18AXE

Data from Aug 20, 2026, 7:38 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.

Netlify Hosted by Netlify

Scores

85
Performance
no change
96
Accessibility
no change
96
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.43 s — — 4.43 s 4.43 s
CLS Cumulative Layout Shift 0.009 — — 0.009 0.009
TBT Total Blocking Time 35 ms — — 35 ms 35 ms
FCP First Contentful Paint 817 ms — — 817 ms 817 ms
Speed Index 817 ms — — 817 ms 817 ms
TTFB Time to First Byte 640 ms — — 640 ms 640 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.

resource load duration 75 ms
resource load delay 44 ms
element render delay 35 ms
time to first byte 30 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 525.4 kB — — 525.4 kB 525.4 kB
Requests 16 — — 16 16
Third-party Weight 310.1 kB — — 310.1 kB 310.1 kB
Third-party CPU 56 ms — — 56 ms 56 ms
Unused JS 138.3 kB — — 138.3 kB 138.3 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 310.1 kB · 3 req
image 130.7 kB · 6 req
font 68.0 kB · 4 req
document 7.9 kB · 1 req
stylesheet 3.6 kB · 1 req
third party 310.1 kB · 3 req

Third parties 2 entities

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

Google Tag Manager 289.3 kB · 44 ms CPU
Google Analytics 20.9 kB · 12 ms CPU

Page health

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

Main thread work

script evaluation 228 ms
other 104 ms
style layout 49 ms
script parse compile 45 ms
paint composite render 15 ms
parse HTML 11 ms

Axe violations axe-core 4.13.0, full rule set

18 violating nodes across 2 rules, 327 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 17 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 23 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. 17 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

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, 7:38 PM UTC 85 4.43 s 0.009 35 ms 525.4 kB 3/3 ±11 4,170 22.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show clioandcalliope.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://clioandcalliope.com/"></speedlify-score>