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 ·

artificial.design

https://artificial.design/

68 80 100 91 CWV 22AXE

Data from Aug 20, 2026, 4:29 PM UTC — 26h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 26h

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.

Self-hosted · nginx Hosted by Self-hosted

Scores

68
Performance
no change
80
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 23.73 s 23.73 s 23.73 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 31 ms 31 ms 31 ms
FCP First Contentful Paint 2.77 s 2.77 s 2.77 s
Speed Index 4.40 s 4.40 s 4.40 s
TTFB Time to First Byte 925 ms 925 ms 925 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.

resource load duration 1.21 s
element render delay 968 ms
time to first byte 175 ms
resource load delay 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.38 MB 4.38 MB 4.38 MB
Requests 15 15 15
Third-party Weight 191.0 kB 191.0 kB 191.0 kB
Third-party CPU 43 ms 43 ms 43 ms
Unused JS 86.3 kB 86.3 kB 86.3 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 4.14 MB · 6 req
script 185.3 kB · 5 req
font 43.0 kB · 1 req
document 5.8 kB · 1 req
stylesheet 5.6 kB · 2 req
third party 191.0 kB · 4 req

Third parties 3 entities

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

Google Tag Manager 125.4 kB · 33 ms CPU
Google Fonts 44.8 kB · 0 ms CPU
Google Analytics 20.9 kB · 10 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 554 ms 554 ms 554 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 22 22 22
A11y Failures 3 3 3
A11y Failing Nodes 19 19 19

Main thread work

other 237 ms
script evaluation 189 ms
script parse compile 47 ms
style layout 41 ms
paint composite render 14 ms
garbage collection 13 ms
parse HTML 13 ms

Axe violations axe-core 4.13.0, full rule set

22 violating nodes across 5 rules, 187 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 17 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-name — Links must have discernible text 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 3 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 17 nodes
  • link-name — Links do not have a discernible name 1 node
  • landmark-one-main — Document does not have a main landmark. 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 20, 2026, 4:29 PM UTC 68 23.73 s 0 31 ms 4.38 MB 3/3 ±3 2,378 30.7s

Embed this score

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