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 ·

progressionapp.com/blog

https://progressionapp.com/blog

Data from Aug 21, 2026, 6:50 AM UTC — 11h old.

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

This URL redirects to https://progression.co/blog.

Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.

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

38
Performance
no change
79
Accessibility
no change
73
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 36.87 s — — 36.87 s 36.87 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 693 ms — — 693 ms 693 ms
FCP First Contentful Paint 9.69 s — — 9.69 s 9.69 s
Speed Index 11.21 s — — 11.21 s 11.21 s
TTFB Time to First Byte 604 ms — — 604 ms 604 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.15 s
time to first byte 149 ms
resource load duration 16 ms
resource load delay 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 8.17 MB — — 8.17 MB 8.17 MB
Requests 129 — — 129 129
Third-party Weight 7.71 MB — — 7.71 MB 7.71 MB
Third-party CPU 566 ms — — 566 ms 566 ms
Unused JS 665.8 kB — — 665.8 kB 665.8 kB
Unused CSS 13.5 kB — — 13.5 kB 13.5 kB

By resource type

image 5.25 MB · 42 req
script 2.13 MB · 51 req
font 627.7 kB · 7 req
stylesheet 84.5 kB · 6 req
document 44.4 kB · 3 req
other 39.9 kB · 19 req
media 5.6 kB · 1 req
third party 2.37 MB · 85 req

Third parties 18 entities

7.71 MB transferred, 566 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

progression.co 5.81 MB · 75 ms CPU
Hubspot 1.12 MB · 196 ms CPU
Google Tag Manager 314.5 kB · 114 ms CPU
Facebook 113.4 kB · 68 ms CPU
Google Optimize 113.2 kB · 21 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.87 s — — 3.87 s 3.87 s
Long Tasks 19 — — 19 19
DOM Elements 741 — — 741 741
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 43 — — 43 43
A11y Failures 6 — — 6 6
A11y Failing Nodes 36 — — 36 36

Main thread work

script evaluation 2.43 s
script parse compile 547 ms
other 505 ms
style layout 253 ms
parse HTML 77 ms
garbage collection 37 ms
paint composite render 22 ms

Axe violations axe-core 4.13.0, full rule set

43 violating nodes across 8 rules, 927 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 30 nodes
  • moderate region — All page content should be contained by landmarks 4 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 3 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes
  • serious aria-dialog-name — ARIA dialog and alertdialog nodes should have an accessible name 1 node
  • critical image-alt — Images must have alternative text 1 node
  • serious link-name — Links must have discernible text 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 6 of 27 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. 30 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes
  • aria-dialog-name — Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names. 1 node
  • image-alt — Image elements do not have `[alt]` attributes 1 node
  • link-name — Links do not have a discernible name 1 node
  • target-size — Touch targets do not have sufficient size or spacing. 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 1 console error

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:50 AM UTC 38 36.87 s 0.003 693 ms 8.17 MB 3/3 ±5 2,465 42.4s

Embed this score

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