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 ·

frontenddogma.com

https://frontenddogma.com/

95 93 100 85 –CWV 2AXE

Data from Aug 20, 2026, 10:36 PM UTC — 20h old.

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

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.

Self-hosted · Apache Hosted by Self-hosted

Scores

95
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
85
SEO
no change

Lab metrics Lighthouse, mobile

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

time to first byte 597 ms
element render delay 41 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 56.8 kB — — 56.8 kB 56.8 kB
Requests 7 — — 7 7
Third-party Weight 7.0 kB — — 7.0 kB 7.0 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

document 42.1 kB · 1 req
image 4.3 kB · 4 req
stylesheet 2.7 kB · 1 req
third party 7.0 kB · 5 req

Third parties 1 entities

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

cloudfront.net 7.0 kB · 0 ms CPU

Page health

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

Main thread work

style layout 285 ms
other 198 ms
parse HTML 47 ms
paint composite render 45 ms
script evaluation 12 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 13568 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 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 18 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. 1 node

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, 10:36 PM UTC 95 2.32 s 0 0 ms 56.8 kB 3/3 ±0 3,120 50.4s

Embed this score

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