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 ·

reedinpartnership.co.uk

https://reedinpartnership.co.uk/

78 96 77 100 CWV 1AXE

Data from Aug 21, 2026, 6:47 AM UTC — 12h old.

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

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

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 2.00 s good
INP 82 ms good
CLS 0 good

Scores

78
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.79 s 3.79 s 3.79 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 282 ms 282 ms 282 ms
FCP First Contentful Paint 2.74 s 2.74 s 2.74 s
Speed Index 3.04 s 3.04 s 3.04 s
TTFB Time to First Byte 481 ms 481 ms 481 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 87 ms
time to first byte 78 ms
resource load duration 71 ms
resource load delay 64 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 2.00 s good 79.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 82 ms good 95.2% good
CLS CWV 0 good 98.5% good
FCP 1.52 s good 79.4% good
TTFB 962 ms needs-improvement 69.6% good

Lab vs field

Lab LCP 3.79 s · field p75 2.00 s · real users are 0.53× 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.99 s 84 ms 0 1.48 s 1.01 s
2026-08-08 2.00 s 80 ms 0 1.49 s 1.21 s
2026-08-01 1.94 s 80 ms 0 1.52 s 1.21 s
2026-07-25 1.93 s 80 ms 0 1.55 s 1.24 s
2026-07-18 1.93 s 80 ms 0 1.52 s 980 ms
2026-07-11 1.76 s 74 ms 0 1.34 s 862 ms
2026-07-04 1.64 s 74 ms 0 1.23 s 797 ms
2026-06-27 1.75 s 71 ms 0 1.34 s 833 ms
2026-06-20 2.08 s 74 ms 0 1.53 s 1.06 s
2026-06-13 2.15 s 79 ms 0 1.66 s 1.21 s
2026-06-06 2.33 s 75 ms 0 1.91 s 1.52 s
2026-05-30 2.25 s 75 ms 0 1.76 s 1.41 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.45 MB 2.45 MB 2.45 MB
Requests 53 53 53
Third-party Weight 420.4 kB 420.4 kB 420.4 kB
Third-party CPU 126 ms 126 ms 126 ms
Unused JS 141.5 kB 141.5 kB 141.5 kB
Unused CSS 0 B 0 B 0 B

By resource type

media 1.68 MB · 1 req
script 439.6 kB · 19 req
font 162.3 kB · 5 req
image 122.0 kB · 9 req
stylesheet 16.0 kB · 4 req
other 15.1 kB · 13 req
document 13.1 kB · 2 req
third party 447.7 kB · 34 req

Third parties 9 entities

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

Google Tag Manager 176.4 kB · 43 ms CPU
userway.org 98.1 kB · 13 ms CPU
Hubspot 67.7 kB · 22 ms CPU
cdn-cookieyes.com 29.3 kB · 12 ms CPU
Google Analytics 20.9 kB · 25 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.78 s 1.78 s 1.78 s
Long Tasks 6 6 6
DOM Elements 641 641 641
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 14 14 14

Main thread work

script evaluation 884 ms
other 374 ms
style layout 341 ms
script parse compile 111 ms
paint composite render 37 ms
parse HTML 32 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 685 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 region — All page content should be contained by landmarks 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 14 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 6:47 AM UTC 78 3.79 s 0 282 ms 2.45 MB 3/3 ±38 2,608 34.5s

Embed this score

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