speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

seccl.tech

https://seccl.tech/

38PERF 96A11Y 77BEST 100SEO ✗AXE ✓CWV

Ranks Overall #1,729 Built Awesome #1,104

Data from Oct 4, 2026, 7:21 PM UTC old Measured once a week · 7 runs since Aug 21, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

Uses ReactReact
Netlify Hosted by Netlify

Lighthouse Scores LAB Simulated

38
Performance
↓ -20 (-34.5%)
96
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Metrics LAB FIELD

Core Web Vitals: passing 3 of 3 assessed from real Chrome users.

Field figures are the p75 across real Chrome users over a 28-day trailing window (2026-09-05 → 2026-10-02), url-level.

Metric Lab Simulated Field
Value Change / range Trend p75 Distribution
LCP CWV Largest Contentful Paint 5.33 s poor ↑ +2589 ms (+94.5%) significant 2.74 s – 5.33 s 1.40 s good 89.6% 5.2% 5.2%
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a — 113 ms good 94.5% 4.1% 1.5%
CLS CWV Cumulative Layout Shift 0.001 good → no change 0 – 0.065 0.010 good 94.4% 3.2% 2.5%
TBT Total Blocking Time 5.00 s poor ↑ +437 ms (+9.6%) 2.59 s – 5.37 s n/a —
FCP First Contentful Paint 3.60 s poor ↑ +1124 ms (+45.3%) significant 2.44 s – 3.76 s 1.33 s good 83.6% 9.2% 7.2%
Speed Index 6.16 s poor ↑ +421 ms (+7.3%) 5.74 s – 44.73 s n/a —
TTFB Time to First Byte 605 ms good ↓ -24 ms (-3.8%) 605 ms – 27.73 s 647 ms good 80.8% 13% 6.2%

LCP Subparts LAB Unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.

element render delay 153 ms
time to first byte 13 ms

LCP LAB Simulated vs LCP FIELD

Lab 5.33 s
Field p75 1.40 s

The lab LCP is 3.81× the field p75 — real users likely have above-average hardware or network connectivity.

Page weight

Metric Value Change / range Trend
Page Weight 2.49 MB ↓ -6.3 kB (-0.3%) 2.49 MB – 2.49 MB
Requests 62 → no change 62 – 62
Third-party Weight 1.27 MB ↓ -6.9 kB (-0.6%) 1.27 MB – 1.27 MB
Third-party CPU 2.31 s ↑ +405 ms (+21.2%) 1.32 s – 2.46 s
Unused JS 264 kB ↓ -22.6 kB (-8%) significant 264 kB – 287 kB
Unused CSS 49.3 kB ↑ +385 B (+0.8%) 48.4 kB – 49.3 kB

By resource type

Type Transfer Share Size Requests
other 51.7% 1.28 MB 12
script 25.6% 635 kB 11
font 9.9% 245 kB 4
image 9.6% 239 kB 19
stylesheet 1.7% 41.3 kB 5
document 1.6% 38.5 kB 2
Total 2.49 MB 62

Third parties 7 entities

Entity Transfer Size Main thread Simulated
JSDelivr CDN other 667 kB 2.16 s
Hubspot script 206 kB 49 ms
Google Tag Manager script 158 kB 41 ms
Cookiebot script 126 kB 33 ms
Netlify 55.4 kB 25 ms
All 7 1.27 MB 2.31 s

Page health

Metric Value Change / range Trend
Main Thread Work 18.46 s ↑ +1635 ms (+9.7%) 12.04 s – 19.13 s
Long Tasks 20 → no change 15 – 20
DOM Elements 1,611 → no change 1,586 – 1,611
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 37 → no change 37 – 38
A11y Failures 2 → no change 2 – 2
A11y Failing Nodes 9 → no change 9 – 9

Main thread work

Task Time Share Duration Simulated
script evaluation 89% 16.37 s
other 7% 1.27 s
style layout 2% 307 ms
parse HTML 1% 184 ms
script parse compile 1% 179 ms
paint composite render 0% 81 ms
garbage collection 0% 68 ms
Total 18.46 s

Axe violations axe-core 4.13.0, full rule set

37 violating nodes across 4 rules, 1158 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • moderate region — All page content should be contained by landmarks 27 nodes
    Offending elements (5 of 27)
    1. .notice-banner 
      <div class="notice-banner">
    2. .features-list--columns-4 
      <div class="features-list features-list--columns-4 home__logos features-list--logos ">
    3. .box-background 
      <header class="section__header section__header--left box-background">
    4. .features-list__item:nth-child(1) > .features-list__item-heading.text-md 
      <h3 class="text-md features-list__item-heading">Build for speed</h3>
    5. .features-list__item:nth-child(1) > .features-list__item-description 
      <div class="features-list__item-description"> <p>Go from idea to live platform in a matter of months – and harness digital investment journeys that are fast, seamless and always 100% paperless.</p> <…
  • moderate heading-order — Heading levels should only increase by one 7 nodes
    Offending elements (5 of 7)
    1. .box-background > h4 
      <h4 class="section__heading-prefix">Your proposition, future-proofed</h4>
    2. .section__header--inverse.columns-8.section__header > h4 
      <h4 class="section__heading-prefix">Robust and reliable</h4>
    3. .columns-6:nth-child(1) > .section__header.section__header--left > h4 
      <h4 class="section__heading-prefix">Diverse clients</h4>
    4. .section--lined > .section__content > .section__header.section__header--left > h4 
      <h4 class="section__heading-prefix">Diverse clients</h4>
    5. .section__header--spacious > h4 
      <h4 class="section__heading-prefix">Long-term ambition</h4>
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
    Offending elements
    1. button[onclick="openTab(event, 'wrappers')"] 
      <button type="button" class="home__services-tab-button" onclick="openTab(event, 'wrappers')"> Accounts and wrappers </button>
    2. .form-contact__footnote > a[href$="privacy"] 
      <a href="/privacy">Privacy Policy</a>
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
    Offending element
    1. .navigation--primary 
      <nav class="navigation navigation--primary navigation--inverse navigation--banner " data-toggle="navList">

Accessibility failures 2 of 32 audits

  • 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

Best Practices failures 2 of 19 audits

  • third-party-cookies — Uses third-party cookies 2 items
  • inspector-issues — Issues were logged in the `Issues` panel in Chrome Devtools 1 item

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-09-26 1.53 s 108 ms 0.020 1.40 s 640 ms
2026-09-19 1.42 s 103 ms 0.010 1.25 s 637 ms
2026-09-12 1.56 s 113 ms 0.010 1.46 s 660 ms
2026-09-05 1.65 s 113 ms 0.010 1.46 s 652 ms
2026-08-29 1.71 s 104 ms 0.010 1.65 s 677 ms
2026-08-22 1.73 s 104 ms 0.010 1.72 s 763 ms
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

Runs

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 4, 2026, 7:21 PM UTC 38 5.33 s 0.001 5.00 s 2.49 MB 3/3 ±25 2,377 -4% 91.5s Wayback
Sep 27, 2026, 5:40 PM UTC 58 2.74 s 0.001 4.56 s 2.49 MB 3/3 ±34 2,759 +11% 52.1s Wayback
Sep 20, 2026, 2:33 PM UTC 50 4.06 s 0.001 2.59 s 2.49 MB 3/3 ±30 3,105 +25% 37.6s Wayback
Sep 13, 2026, 1:47 PM UTC 41 4.51 s 0 5.00 s 2.49 MB 3/3 ±13 2,503 +1% 42.4s Wayback
Sep 6, 2026, 10:22 AM UTC 57 2.83 s 0 5.37 s 2.49 MB 3/3 ±31 2,296 -8% 42.7s Wayback
Aug 30, 2026, 7:56 AM UTC 57 2.83 s 0 4.27 s 2.49 MB 3/3 ±31 2,743 +10% 40.1s Wayback
Aug 21, 2026, 7:55 AM UTC 50 3.06 s 0.065 3.85 s 2.49 MB 2/3 ±6 2,750 +11% 215.1s Wayback

Embed this score

Use this web component to show seccl.tech's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://seccl.tech/"></speedlify2-score>