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 ·

arturojofre.cl

https://www.arturojofre.cl/

85 93 100 100 CWV 2AXE

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

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 7h

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.

Astro 5.14.8 Built with Astro 5.14.8
Self-hosted · Apache Hosted by Self-hosted

Scores

85
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

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

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 727.5 kB 727.5 kB 727.5 kB
Requests 12 12 12
Third-party Weight 355.1 kB 355.1 kB 355.1 kB
Third-party CPU 91 ms 91 ms 91 ms
Unused JS 136.4 kB 136.4 kB 136.4 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 354.8 kB · 3 req
script 311.2 kB · 4 req
font 48.5 kB · 1 req
stylesheet 6.9 kB · 2 req
document 5.4 kB · 1 req
other 705 B · 1 req
third party 355.1 kB · 5 req

Third parties 3 entities

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

Google Tag Manager 284.8 kB · 81 ms CPU
Google Fonts 49.5 kB · 0 ms CPU
Google Analytics 20.9 kB · 10 ms CPU

Page health

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

Main thread work

other 931 ms
script evaluation 417 ms
style layout 115 ms
script parse compile 90 ms
paint composite render 66 ms
parse HTML 12 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 190 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 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 19 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. 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1

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, 11:25 AM UTC 85 3.77 s 0 101 ms 727.5 kB 3/3 ±1 2,471 23.6s

Embed this score

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