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 ·

seccl.tech

https://seccl.tech/

50 96 77 100 ✓CWV 38AXE

Data from Aug 21, 2026, 7:55 AM UTC — 11h old.

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

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

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.71 s good
INP 139 ms good
CLS 0.010 good

Scores

50
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.06 s — — 3.06 s 3.06 s
CLS Cumulative Layout Shift 0.065 — — 0.065 0.065
TBT Total Blocking Time 3.85 s — — 3.85 s 3.85 s
FCP First Contentful Paint 2.44 s — — 2.44 s 2.44 s
Speed Index 44.73 s — — 44.73 s 44.73 s
TTFB Time to First Byte 27.73 s — — 27.73 s 27.73 s

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.

time to first byte 27.73 s
element render delay 123 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.71 s good 88.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 139 ms good 84.6% good
CLS CWV 0.010 good 96.5% good
FCP 1.65 s good 77.9% good
TTFB 743 ms good 79.6% good

Lab vs field

Lab LCP 3.06 s · field p75 1.71 s · real users are 0.56× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.72 s 117 ms 0 1.66 s 763 ms
2026-08-08 1.79 s 106 ms 0.010 1.76 s 766 ms
2026-08-01 1.71 s 139 ms 0 1.63 s 732 ms
2026-07-25 1.69 s 128 ms 0 1.49 s 697 ms
2026-07-18 1.49 s 137 ms 0 1.35 s 680 ms
2026-07-11 1.47 s 137 ms 0 1.31 s 568 ms
2026-07-04 1.40 s 118 ms 0 1.22 s 549 ms
2026-06-27 1.42 s 143 ms 0.010 1.31 s 549 ms
2026-06-20 1.63 s 121 ms 0.030 1.54 s 583 ms
2026-06-13 1.39 s 143 ms 0.030 1.34 s 575 ms
2026-06-06 1.39 s 213 ms 0.020 1.34 s 583 ms
2026-05-30 1.37 s — 0.020 1.32 s —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.49 MB — — 2.49 MB 2.49 MB
Requests 62 — — 62 62
Third-party Weight 1.27 MB — — 1.27 MB 1.27 MB
Third-party CPU 1.60 s — — 1.60 s 1.60 s
Unused JS 284.1 kB — — 284.1 kB 284.1 kB
Unused CSS 48.5 kB — — 48.5 kB 48.5 kB

By resource type

other 1.28 MB · 12 req
script 638.9 kB · 11 req
font 245.5 kB · 4 req
image 238.5 kB · 19 req
stylesheet 40.5 kB · 5 req
document 38.2 kB · 2 req
third party 1.27 MB · 17 req

Third parties 7 entities

1.27 MB transferred, 1.60 s of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

JSDelivr CDN 667.4 kB · 1.44 s CPU
Hubspot 206.1 kB · 61 ms CPU
Google Tag Manager 154.0 kB · 35 ms CPU
Cookiebot 133.3 kB · 31 ms CPU
Netlify 55.5 kB · 23 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 14.77 s — — 14.77 s 14.77 s
Long Tasks 19 — — 19 19
DOM Elements 1,586 — — 1,586 1,586
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 38 — — 38 38
A11y Failures 2 — — 2 2
A11y Failing Nodes 9 — — 9 9

Main thread work

script evaluation 12.73 s
other 1.17 s
style layout 375 ms
script parse compile 207 ms
parse HTML 144 ms
paint composite render 94 ms
garbage collection 47 ms

Axe violations axe-core 4.13.0, full rule set

38 violating nodes across 4 rules, 1156 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 28 nodes
  • moderate heading-order — Heading levels should only increase by one 7 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 32 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.

  • heading-order — Heading elements are not in a sequentially-descending order 7 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 nodes

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, 7:55 AM UTC 50 3.06 s 0.065 3.85 s 2.49 MB 2/3 ±6 2,750 215.1s

Embed this score

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