speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

lingfest.uk

https://www.lingfest.uk/

71 84 81 92 76AXE CWV

Data from Aug 22, 2026, 1:10 AM UTC 45h old

Built Awesome #1,091 · 3 measurements · since Aug 21, 2026

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

Scores

71
Performance
no change
84
Accessibility
no change
81
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.86 s 6.86 s 6.86 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 74 ms 74 ms 74 ms
FCP First Contentful Paint 2.74 s 2.74 s 2.74 s
Speed Index 3.52 s 3.52 s 3.52 s
TTFB Time to First Byte 610 ms 610 ms 610 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.53 MB 1.53 MB 1.53 MB
Requests 65 65 65
Third-party Weight 311 kB 311 kB 311 kB
Third-party CPU 70 ms 70 ms 70 ms
Unused JS 271 kB 271 kB 271 kB
Unused CSS 52.6 kB 52.6 kB 52.6 kB

By resource type

image 634 kB · 37 req
script 507 kB · 8 req
font 290 kB · 6 req
stylesheet 85.3 kB · 10 req
document 6.9 kB · 1 req
other 676 B · 2 req
third party 311 kB · 9 req

Third parties 6 entities

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

Amazon Web Services 144 kB · 16 ms CPU
Google Tag Manager 134 kB · 39 ms CPU
Google Analytics 21.6 kB · 13 ms CPU
eep.io 6.4 kB · 0 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.66 s 1.66 s 1.66 s
Long Tasks 5 5 5
DOM Elements 332 332 332
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 76 76 76
A11y Failures 4 4 4
A11y Failing Nodes 8 8 8

Main thread work

script evaluation 565 ms
other 495 ms
style layout 353 ms
script parse compile 130 ms
parse HTML 64 ms
paint composite render 53 ms

Axe violations axe-core 4.13.0, full rule set

76 violating nodes across 6 rules, 592 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 56 nodes
  • moderate region — All page content should be contained by landmarks 13 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 2 nodes
  • critical image-alt — Images must have alternative text 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 4 of 22 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-in-text-block — Links rely on color to be distinguishable. 2 nodes
  • image-alt — Image elements do not have `[alt]` attributes 1 node
  • landmark-one-main — Document does not have a main landmark. 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 22, 2026, 1:10 AM UTC 71 6.86 s 0 74 ms 1.53 MB 2/3 ±0 2,333 53.6s
Aug 21, 2026, 5:27 PM UTC NO_FCP: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP) 102.3s
Aug 21, 2026, 11:26 AM UTC NO_FCP: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP) 100.3s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show lingfest.uk's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.lingfest.uk/"></speedlify2-score>