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 ·

westwarwicks.club

https://westwarwicks.club/

56 92 73 100 ✗CWV 10AXE

Data from Aug 21, 2026, 8:50 AM UTC — 10h old.

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

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.

El Built with Elementor 4.2.2
Self-hosted · nginx Hosted by Self-hosted

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.69 s good
INP — no data
CLS 0.270 poor

Scores

56
Performance
no change
92
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 21.13 s — — 21.13 s 21.13 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 54 ms — — 54 ms 54 ms
FCP First Contentful Paint 5.54 s — — 5.54 s 5.54 s
Speed Index 11.02 s — — 11.02 s 11.02 s
TTFB Time to First Byte 737 ms — — 737 ms 737 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 1.46 s
resource load duration 703 ms
time to first byte 263 ms
resource load delay 15 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.69 s good 85.5% good
CLS CWV 0.270 poor 55.9% good
FCP 1.43 s good 83.8% good
TTFB 537 ms good 85.3% good

Lab vs field

Lab LCP 21.13 s · field p75 1.69 s · real users are 0.08× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.74 s 116 ms 0.270 1.34 s 432 ms
2026-08-08 1.63 s 105 ms 0.270 1.20 s 415 ms
2026-08-01 — — — — —
2026-07-25 1.35 s 100 ms 0.260 968 ms 296 ms
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 1.53 s 94 ms 0.290 1.03 s 347 ms
2026-06-13 1.48 s 89 ms 0.290 975 ms 329 ms
2026-06-06 1.42 s 93 ms 0.270 934 ms 342 ms
2026-05-30 1.53 s 97 ms 0.280 956 ms 357 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.25 MB — — 7.25 MB 7.25 MB
Requests 167 — — 167 167
Third-party Weight 227.7 kB — — 227.7 kB 227.7 kB
Third-party CPU 73 ms — — 73 ms 73 ms
Unused JS 115.5 kB — — 115.5 kB 115.5 kB
Unused CSS 112.5 kB — — 112.5 kB 112.5 kB

By resource type

image 5.12 MB · 25 req
script 1.40 MB · 54 req
font 350.4 kB · 9 req
stylesheet 277.1 kB · 61 req
document 88.7 kB · 2 req
other 8.8 kB · 16 req
third party 1.29 MB · 31 req

Third parties 5 entities

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

Google Tag Manager 171.9 kB · 60 ms CPU
Google Fonts 33.7 kB · 0 ms CPU
cleantalk.org 12.4 kB · 7 ms CPU
YouTube 9.7 kB · 6 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 911 ms
other 806 ms
style layout 346 ms
parse HTML 213 ms
script parse compile 158 ms
paint composite render 60 ms
garbage collection 25 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 6 rules, 999 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 4 nodes
  • serious link-name — Links must have discernible text 2 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-contentinfo-is-top-level — Contentinfo landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-contentinfo — Document should not have more than one contentinfo landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 3 of 32 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. 4 nodes
  • link-name — Links do not have a discernible name 2 nodes
  • 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 3 console errors

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 21, 2026, 8:50 AM UTC 56 21.13 s 0 54 ms 7.25 MB 3/3 ±0 2,767 65.7s

Embed this score

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