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 and Bluesky.
Last updated ago. 1,763 measurements in the last week.

Charts Compare Measurement runs Embed a score Open to Work

andreiaramos.pt

https://andreiaramos.pt/

100PERF 100A11Y 100BEST 100SEO ✓AXE –CWV

Ranks Overall #156 Built Awesome #117

Data from Nov 21, 2026, 6:08 PM UTC old Measured once a week · 14 runs since Aug 20, 2026

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

The measuring machine was faster than most in this project.

Lighthouse benchmark index was 4,018, 61% faster than this project's median of 2,493. CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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

Stack

Eleventy 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify
Rendered At build time Eleventy builds static pages

Lighthouse Scores LAB Simulated

100
Performance
↑ +1 (+1%)
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 1.70 s good ↓ -125 ms (-6.8%) significant 1.23 s – 2.44 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0 good → no change 0 – 0
TBT Total Blocking Time 0 ms good → no change 0 ms – 0 ms
FCP First Contentful Paint 953 ms good ↓ -231 ms (-19.5%) significant 946 ms – 1.18 s
Speed Index 953 ms good ↓ -231 ms (-19.5%) significant 946 ms – 1.18 s
TTFB Time to First Byte 630 ms good ↓ -98 ms (-13.5%) significant 604 ms – 728 ms
RTT Round-trip time to the server — field only, and ungraded: Google publishes no threshold for it n/a —

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.

resource load duration 41 ms
time to first byte 27 ms
element render delay 27 ms
resource load delay 7 ms

Page weight

Metric Value Change / range Trend
Page Weight 71.7 kB ↓ -1.1 kB (-1.5%) 67.8 kB – 234 kB
Requests 7 → no change 7 – 8
Third-party Weight 5.3 kB ↓ -1.0 kB (-16.3%) significant 3.3 kB – 6.3 kB
Third-party CPU 2 ms ↓ -0 ms (-9.1%) 2 ms – 6 ms
Unused JS 0 B → no change 0 B – 0 B
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
image 50.5% 35.1 kB 1
document 41.3% 28.7 kB 1
script 6.7% 4.7 kB 1
other 1.5% 1.0 kB 3
Total 71.7 kB 7

Third parties 1 entities

Entity Transfer Size Main thread Simulated
umami.is script 5.3 kB 2 ms
Total 5.3 kB 2 ms

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Page health

Metric Value Change / range Trend
Main Thread Work 158 ms ↓ -178 ms (-53%) significant 144 ms – 337 ms
Long Tasks 0 ↓ -1 (-100%) significant 0 – 1
DOM Elements 297 → no change 292 – 297
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 0 → no change 0 – 3
A11y Failures 0 → no change 0 – 1
A11y Failing Nodes 0 → no change 0 – 3

Main thread work

Task Time Share Duration Simulated
other 47% 74 ms
style layout 21% 33 ms
script evaluation 12% 19 ms
parse HTML 12% 19 ms
paint composite render 5% 9 ms
script parse compile 3% 4 ms
Total 158 ms

Axe violations axe-core 4.14.0, full rule set

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

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Origin field history 25 weeks SITE-WIDE

Weekly p75 from the CrUX History API, backfilled in a single request. For andreiaramos.pt as a whole — CrUX has no per-week data for this URL, so these are the site's numbers and not this page's.

Week ending LCPINPCLSFCPTTFB
2026-06-27 → 2026-11-14 No data — 21 weeks under the CrUX reporting threshold
2026-06-20 1.31 s — 0 1.13 s 830 ms —
2026-05-30 → 2026-06-13 No data — 3 weeks under the CrUX reporting threshold

Runs

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchLighthouseTook Archive
Nov 21, 2026, 6:08 PM UTC 100 1.70 s 0 0 ms 71.7 kB 3/3 ±1 4,018 +61% 13.6.0 23.5s Wayback
Nov 14, 2026, 2:17 PM UTC 99 1.83 s 0 0 ms 72.8 kB 3/3 ±1 3,493 +40% 13.6.0 22.1s Wayback
Nov 7, 2026, 2:14 PM UTC 100 1.68 s 0 0 ms 71.4 kB 3/3 ±1 2,974 +19% 13.6.0 23.8s Wayback
Oct 31, 2026, 1:21 PM UTC 100 1.23 s 0 0 ms 70.9 kB 3/3 ±1 4,483 +80% 13.4.1 23.7s Wayback
Oct 24, 2026, 10:23 AM UTC 100 1.66 s 0 0 ms 69.4 kB 3/3 ±1 2,476 -1% 13.4.1 26.5s Wayback
Oct 17, 2026, 6:38 AM UTC 100 1.70 s 0 0 ms 69.5 kB 3/3 ±0 2,463 -1% 13.4.1 27.6s Wayback
Oct 10, 2026, 2:08 AM UTC 100 1.69 s 0 0 ms 69.6 kB 3/3 ±2 2,534 +2% 13.4.1 27.2s Wayback
Oct 2, 2026, 10:59 PM UTC 100 1.69 s 0 0 ms 69.6 kB 3/3 ±1 3,243 +30% 13.4.1 25.1s Wayback
Sep 25, 2026, 12:34 AM UTC 100 1.68 s 0 0 ms 69.6 kB 3/3 ±0 2,483 0% 13.4.1 30.3s Wayback
Sep 17, 2026, 11:30 PM UTC 100 1.66 s 0 0 ms 68.8 kB 3/3 ±1 2,461 -1% 13.4.1 26.5s Wayback
Sep 10, 2026, 9:32 PM UTC 100 1.67 s 0 0 ms 68.7 kB 3/3 ±1 2,481 0% 13.4.1 25.9s Wayback
Sep 3, 2026, 7:23 PM UTC 100 1.70 s 0 0 ms 67.8 kB 3/3 ±1 2,433 -2% 13.4.1 26.6s Wayback
Aug 27, 2026, 4:13 PM UTC 98 2.44 s 0 0 ms 234 kB 3/3 ±1 2,463 -1% 13.4.1 26.3s Wayback
Aug 20, 2026, 3:42 PM UTC 98 2.44 s 0 0 ms 233 kB 3/3 ±1 2,306 -8% 13.4.1 25.4s Wayback

Embed this score

Use this web component to show andreiaramos.pt'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://andreiaramos.pt/"></speedlify2-score>