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 ·

tactile.co.za

https://tactile.co.za/

99 91 100 91 CWV 2AXE

Data from Aug 21, 2026, 7:48 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.

GitHub Pages Hosted by GitHub Pages

Scores

99
Performance
no change
91
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.72 s 1.72 s 1.72 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 66 ms 66 ms 66 ms
FCP First Contentful Paint 784 ms 784 ms 784 ms
Speed Index 784 ms 784 ms 784 ms
TTFB Time to First Byte 607 ms 607 ms 607 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 31 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 199.8 kB 199.8 kB 199.8 kB
Requests 9 9 9
Third-party Weight 189.3 kB 189.3 kB 189.3 kB
Third-party CPU 45 ms 45 ms 45 ms
Unused JS 70.7 kB 70.7 kB 70.7 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 189.3 kB · 3 req
document 5.9 kB · 1 req
other 3.6 kB · 4 req
third party 189.3 kB · 4 req

Third parties 3 entities

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

Google Tag Manager 157.0 kB · 30 ms CPU
Google Analytics 20.9 kB · 13 ms CPU
Cloudflare 11.5 kB · 2 ms CPU

Page health

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

Main thread work

script evaluation 192 ms
other 85 ms
script parse compile 39 ms
style layout 28 ms
parse HTML 6 ms
paint composite render 4 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 140 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.

  • minor empty-heading — Headings should not be empty 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 1 of 13 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.

  • link-name — Links do not have a discernible name 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, 7:48 AM UTC 99 1.72 s 0 66 ms 199.8 kB 3/3 ±0 2,986 19.6s

Embed this score

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