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

https://progressionapp.com/

Data from Aug 21, 2026, 2:39 PM UTC — 3h old.

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

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

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

40
Performance
no change
65
Accessibility
no change
77
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 10.94 s — — 10.94 s 10.94 s
CLS Cumulative Layout Shift 0.029 — — 0.029 0.029
TBT Total Blocking Time 930 ms — — 930 ms 930 ms
FCP First Contentful Paint 5.57 s — — 5.57 s 5.57 s
Speed Index 5.58 s — — 5.58 s 5.58 s
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 292 ms
time to first byte 21 ms
resource load duration 16 ms
resource load delay 14 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.90 MB — — 7.90 MB 7.90 MB
Requests 148 — — 148 148
Third-party Weight 6.63 MB — — 6.63 MB 6.63 MB
Third-party CPU 629 ms — — 629 ms 629 ms
Unused JS 644.6 kB — — 644.6 kB 644.6 kB
Unused CSS 13.0 kB — — 13.0 kB 13.0 kB

By resource type

image 4.97 MB · 61 req
script 2.13 MB · 52 req
font 628.1 kB · 7 req
stylesheet 84.3 kB · 6 req
document 45.2 kB · 3 req
other 39.8 kB · 18 req
media 5.6 kB · 1 req
third party 2.37 MB · 86 req

Third parties 18 entities

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

progression.co 5.53 MB · 75 ms CPU
Google Tag Manager 314.5 kB · 113 ms CPU
Hubspot 313.1 kB · 217 ms CPU
Facebook 113.4 kB · 95 ms CPU
Google Optimize 113.2 kB · 19 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 4.30 s — — 4.30 s 4.30 s
Long Tasks 20 — — 20 20
DOM Elements 821 — — 821 821
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 82 — — 82 82
A11y Failures 10 — — 10 10
A11y Failing Nodes 67 — — 67 67

Main thread work

script evaluation 2.35 s
other 812 ms
script parse compile 571 ms
style layout 356 ms
paint composite render 95 ms
parse HTML 73 ms
garbage collection 47 ms

Axe violations axe-core 4.13.0, full rule set

82 violating nodes across 11 rules, 962 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 47 nodes
  • moderate region — All page content should be contained by landmarks 15 nodes
  • critical aria-roles — ARIA roles used must conform to valid values 5 nodes
  • critical aria-required-parent — Certain ARIA roles must be contained by particular parents 4 nodes
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 4 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 aria-required-children — Certain ARIA roles must contain particular children 1 node
  • critical image-alt — Images must have alternative text 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 10 of 31 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. 47 nodes
  • aria-roles — `[role]` values are not valid 5 nodes
  • aria-required-parent — `[role]`s are not contained by their required parent element 4 nodes
  • listitem — List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements. 4 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
  • aria-required-children — Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 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

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, 2:39 PM UTC 40 10.94 s 0.029 930 ms 7.90 MB 3/3 ±1 2,495 42.6s

Embed this score

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