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 ·

platforms.barnardos.org.uk

https://platforms.barnardos.org.uk/

98 100 100 100 CWV 1AXE

Data from Aug 21, 2026, 4:43 AM UTC — 14h old.

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

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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Scores

98
Performance
no change
100
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 2.02 s 2.02 s 2.02 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 17 ms 17 ms 17 ms
FCP First Contentful Paint 1.87 s 1.87 s 1.87 s
Speed Index 1.87 s 1.87 s 1.87 s
TTFB Time to First Byte 461 ms 461 ms 461 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 66 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 83.8 kB 83.8 kB 83.8 kB
Requests 7 7 7
Third-party Weight 66.6 kB 66.6 kB 66.6 kB
Third-party CPU 29 ms 29 ms 29 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

script 66.6 kB · 2 req
document 13.5 kB · 1 req
other 1.4 kB · 2 req
third party 66.6 kB · 2 req

Third parties 2 entities

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

Netlify 55.1 kB · 27 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 115 ms
other 83 ms
script parse compile 27 ms
style layout 22 ms
parse HTML 12 ms
paint composite render 4 ms

Axe violations axe-core 4.13.0, full rule set

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

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, 4:43 AM UTC 98 2.02 s 0 17 ms 83.8 kB 3/3 ±2 2,489 22s

Embed this score

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