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 ·

photogabble.co.uk

https://photogabble.co.uk/

100 96 100 92 –CWV 2AXE

Data from Aug 21, 2026, 4:42 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

100
Performance
no change
96
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 1.80 s — — 1.80 s 1.80 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 771 ms — — 771 ms 771 ms
Speed Index 771 ms — — 771 ms 771 ms
TTFB Time to First Byte 605 ms — — 605 ms 605 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 72 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 130.4 kB — — 130.4 kB 130.4 kB
Requests 16 — — 16 16
Third-party Weight 4.8 kB — — 4.8 kB 4.8 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 104.2 kB · 4 req
stylesheet 7.7 kB · 1 req
image 6.6 kB · 5 req
script 5.0 kB · 2 req
document 4.7 kB · 1 req
other 2.1 kB · 3 req
third party 4.8 kB · 2 req

Third parties 2 entities

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

zgo.at 4.4 kB · 2 ms CPU
goatcounter.com 381 B · 0 ms CPU

Page health

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

Main thread work

other 231 ms
paint composite render 151 ms
style layout 82 ms
script evaluation 22 ms
parse HTML 11 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 598 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 definition-list — <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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

  • definition-list — `<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. 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, 4:42 AM UTC 100 1.80 s 0 0 ms 130.4 kB 3/3 ±4 2,468 22.6s

Embed this score

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