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 ·

mapledesign.co.uk

https://www.mapledesign.co.uk/

72 97 100 100 –CWV 1AXE

Data from Aug 21, 2026, 1:48 PM UTC — 5h old.

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

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

72
Performance
no change
97
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 3.43 s — — 3.43 s 3.43 s
CLS Cumulative Layout Shift 0.251 — — 0.251 0.251
TBT Total Blocking Time 37 ms — — 37 ms 37 ms
FCP First Contentful Paint 3.36 s — — 3.36 s 3.36 s
Speed Index 3.36 s — — 3.36 s 3.36 s
TTFB Time to First Byte 732 ms — — 732 ms 732 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.21 s
time to first byte 134 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 319.2 kB — — 319.2 kB 319.2 kB
Requests 22 — — 22 22
Third-party Weight 219.5 kB — — 219.5 kB 219.5 kB
Third-party CPU 45 ms — — 45 ms 45 ms
Unused JS 78.2 kB — — 78.2 kB 78.2 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 193.6 kB · 3 req
font 53.1 kB · 3 req
image 49.0 kB · 9 req
stylesheet 12.5 kB · 4 req
document 8.0 kB · 1 req
third party 219.5 kB · 5 req

Third parties 2 entities

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

Google Tag Manager 191.7 kB · 45 ms CPU
Adobe TypeKit 27.8 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 675 ms — — 675 ms 675 ms
Long Tasks 4 — — 4 4
DOM Elements 251 — — 251 251
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 258 ms
style layout 183 ms
other 145 ms
script parse compile 46 ms
paint composite render 23 ms
parse HTML 20 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 471 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 14 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 21, 2026, 1:48 PM UTC 72 3.43 s 0.251 37 ms 319.2 kB 3/3 ±2 2,457 28.1s

Embed this score

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