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 ·

andreiaramos.pt

https://andreiaramos.pt/

98 96 100 100 CWV 3AXE

Data from Aug 20, 2026, 3:42 PM UTC — 27h old.

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

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.

Eleventy 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

98
Performance
no change
96
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 2.44 s 2.44 s 2.44 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 991 ms 991 ms 991 ms
Speed Index 991 ms 991 ms 991 ms
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 61 ms
resource load duration 17 ms
resource load delay 12 ms
time to first byte 10 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20 1.31 s 0 1.13 s 830 ms
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 233.0 kB 233.0 kB 233.0 kB
Requests 8 8 8
Third-party Weight 3.3 kB 3.3 kB 3.3 kB
Third-party CPU 3 ms 3 ms 3 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

other 149.6 kB · 4 req
image 53.1 kB · 1 req
document 25.4 kB · 1 req
script 2.7 kB · 1 req
third party 3.3 kB · 3 req

Third parties 1 entities

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

umami.is 3.3 kB · 3 ms CPU

Page health

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

Main thread work

other 167 ms
style layout 94 ms
script evaluation 29 ms
parse HTML 26 ms
paint composite render 11 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 1 rule, 482 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 aria-prohibited-attr — Elements must only use permitted ARIA attributes 3 nodes

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

  • aria-prohibited-attr — Elements use prohibited ARIA attributes 3 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 20, 2026, 3:42 PM UTC 98 2.44 s 0 0 ms 233.0 kB 3/3 ±1 2,306 25.4s

Embed this score

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