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 ·

cw2architects.com

https://cw2architects.com/

88 97 100 92 –CWV 1AXE

Data from Aug 20, 2026, 7:32 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.

Self-hosted · nginx Hosted by Self-hosted

Scores

88
Performance
no change
97
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 3.39 s — — 3.39 s 3.39 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 78 ms — — 78 ms 78 ms
FCP First Contentful Paint 2.51 s — — 2.51 s 2.51 s
Speed Index 2.51 s — — 2.51 s 2.51 s
TTFB Time to First Byte 684 ms — — 684 ms 684 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 122 ms
time to first byte 86 ms
resource load duration 11 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 806.6 kB — — 806.6 kB 806.6 kB
Requests 23 — — 23 23
Third-party Weight 776.1 kB — — 776.1 kB 776.1 kB
Third-party CPU 79 ms — — 79 ms 79 ms
Unused JS 138.1 kB — — 138.1 kB 138.1 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 443.9 kB · 13 req
script 310.6 kB · 4 req
font 35.5 kB · 1 req
stylesheet 9.6 kB · 2 req
document 5.6 kB · 1 req
other 1.4 kB · 2 req
third party 776.1 kB · 14 req

Third parties 4 entities

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

imagekit.io 429.9 kB · 0 ms CPU
Google Tag Manager 289.0 kB · 70 ms CPU
Google Fonts 36.4 kB · 0 ms CPU
Google Analytics 20.9 kB · 9 ms CPU

Page health

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

Main thread work

script evaluation 304 ms
other 215 ms
script parse compile 73 ms
style layout 49 ms
paint composite render 16 ms
parse HTML 15 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 211 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.

  • moderate heading-order — Heading levels should only increase by one 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 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, 7:32 PM UTC 88 3.39 s 0 78 ms 806.6 kB 3/3 ±15 2,490 24.5s

Embed this score

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