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 ·

anchorthemes.com

https://anchorthemes.com/

100 87 100 100 –CWV 232AXE

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

Built Awesome · 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.

Netlify Hosted by Netlify

Scores

100
Performance
no change
87
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.21 s — — 1.21 s 1.21 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 906 ms — — 906 ms 906 ms
Speed Index 906 ms — — 906 ms 906 ms
TTFB Time to First Byte 606 ms — — 606 ms 606 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 52 ms
resource load delay 23 ms
time to first byte 7 ms
resource load duration 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 447.1 kB — — 447.1 kB 447.1 kB
Requests 28 — — 28 28
Third-party Weight 0 B — — 0 B 0 B
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

image 430.6 kB · 26 req
document 12.9 kB · 1 req
stylesheet 3.6 kB · 1 req

Page health

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

Main thread work

other 236 ms
paint composite render 118 ms
style layout 78 ms
script evaluation 47 ms
parse HTML 22 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

232 violating nodes across 4 rules, 1791 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 218 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 11 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 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. 218 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 11 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 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:26 PM UTC 100 1.21 s 0 0 ms 447.1 kB 3/3 ±0 2,416 27.4s

Embed this score

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