eleventy-html5up-txt.appseed.us
https://eleventy-html5up-txt.appseed.us/
Ranks Overall #1,591 Built Awesome #1,054
Data from Sep 19, 2026, 3:18 AM UTC old, older than this category's 14 days freshness target Measured once a week · 15 runs since Aug 20, 2026
Elsewhere:
PageSpeed Insights ·
Calibre ·
Treo ·
CrUX Vis ·
Tame the Bots ·
Scoring Calculator ·
Wayback Machine
The most recent attempt failed (10 in a row).
CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests.
Numbers below are from the last successful run, old.
Retries are backing off, so this site is being attempted less often than the rest.
Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).
Stack
Hosted by
Self-hosted
Lighthouse Scores LAB Simulated
76
Performance
↓ -4 (-5%)
63
Accessibility
no change
96
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 | 5.37 s poor | ↑ +11 ms (+0.2%) 5.34 s – 5.39 s | |
| INP CWV Interaction to Next Paint — field only, no lab run can measure it | n/a | — | |
| CLS CWV (estimate) Cumulative Layout Shift | 0.036 good | → no change 0.036 – 0.036 | |
| TBT Total Blocking Time | 2 ms good | ↑ +2 ms 0 ms – 2 ms | |
| FCP First Contentful Paint | 2.67 s needs work | ↑ +1079 ms (+68%) 1.57 s – 2.67 s | |
| Speed Index | 2.67 s good | ↑ +1079 ms (+68%) 1.57 s – 2.67 s | |
| TTFB Time to First Byte | 665 ms good | ↑ +6 ms (+0.9%) 643 ms – 665 ms | |
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 delay
251 ms
resource load duration
87 ms
time to first byte
47 ms
element render delay
25 ms
Page weight
| Metric | Value | Change / range | Trend |
|---|---|---|---|
| Page Weight | 698 kB | ↓ -23 B 698 kB – 698 kB | |
| Requests | 24 | → no change 24 – 25 | |
| Third-party Weight | 55.6 kB | → no change 55.6 kB – 55.6 kB | |
| Third-party CPU | 0 ms | → no change 0 ms – 0 ms | |
| Unused JS | 0 B | → no change 0 B – 0 B | |
| Unused CSS | 11.7 kB | → no change 11.7 kB – 11.7 kB |
By resource type
| Type | Transfer | Share | Size | Requests |
|---|---|---|---|---|
| image | 60.1% | 420 kB | 8 | |
| font | 31.1% | 217 kB | 5 | |
| script | 5.4% | 37.7 kB | 7 | |
| stylesheet | 3% | 21.1 kB | 3 | |
| document | 0.3% | 2.4 kB | 1 | |
| Total | 698 kB | 24 |
Third parties 1 entities
| Entity | Transfer | Size | Main thread Simulated |
|---|---|---|---|
| Google Fonts | 55.6 kB | 0 ms | |
| Total | 55.6 kB | 0 ms |
Page health
| Metric | Value | Change / range | Trend |
|---|---|---|---|
| Main Thread Work | 387 ms | ↑ +11 ms (+2.8%) 354 ms – 387 ms | |
| Long Tasks | 1 | ↑ +1 0 – 1 | |
| DOM Elements | 254 | → no change 254 – 254 | |
| Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) | 47 | → no change 47 – 47 | |
| A11y Failures | 5 | → no change 5 – 5 | |
| A11y Failing Nodes | 40 | → no change 40 – 40 |
Main thread work
| Task | Time | Share | Duration Simulated |
|---|---|---|---|
| other | 36% | 139 ms | |
| style layout | 27% | 104 ms | |
| script evaluation | 20% | 79 ms | |
| paint composite render | 7% | 27 ms | |
| parse HTML | 6% | 25 ms | |
| script parse compile | 4% | 14 ms | |
| Total | 387 ms |
Axe violations axe-core 4.13.0, full rule set
47 violating nodes across 7 rules, 348 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.
-
serious
color-contrast— Elements must meet minimum color contrast ratio thresholds 23 nodes -
serious
link-name— Links must have discernible text 14 nodes -
moderate
region— All page content should be contained by landmarks 6 nodes -
serious
html-has-lang— <html> element must have a lang attribute 1 node -
moderate
landmark-one-main— Document should have one main landmark 1 node -
moderate
meta-viewport— Zooming and scaling must not be disabled 1 node -
moderate
page-has-heading-one— Page should contain a level-one heading 1 node
Accessibility failures 5 of 14 audits
-
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 23 nodes -
link-name— Links do not have a discernible name 14 nodes -
html-has-lang— `<html>` element does not have a `[lang]` attribute 1 node -
meta-viewport— `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node -
landmark-one-main— Document does not have a main landmark. 1 node
Best Practices failures 1 of 20 audits
-
errors-in-console— Browser errors were logged to the console 2 items
Hygiene
HTTPS
HSTS
CSP
Clickjacking protection
Origin isolation
Trusted Types
bfcache
h2
2 console errors
Measurement log
Every stored run for this URL, newest first.
| When | Scores | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took | Archive |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Oct 9, 2026, 10:23 AM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
16.9s | |||||||||
| Oct 8, 2026, 2:39 AM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
17.9s | |||||||||
| Oct 7, 2026, 2:10 AM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
17.6s | |||||||||
| Oct 3, 2026, 11:41 PM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
16.5s | |||||||||
| Oct 1, 2026, 2:20 PM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
16.6s | |||||||||
| Sep 30, 2026, 3:43 PM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
17.8s | |||||||||
| Sep 30, 2026, 1:06 AM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
16.7s | |||||||||
| Sep 29, 2026, 5:54 PM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
17.8s | |||||||||
| Sep 26, 2026, 2:11 PM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
18s | |||||||||
| Sep 26, 2026, 3:50 AM UTC | CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. |
18.6s | |||||||||
| Sep 19, 2026, 3:18 AM UTC | 76 | 5.37 s | 0.036 | 2 ms | 698 kB | 3/3 | ±3 | 2,465 -1% | 24.3s |
|
|
| Sep 12, 2026, 1:02 AM UTC | 80 | 5.36 s | 0.036 | 0 ms | 698 kB | 3/3 | ±4 | 2,246 -10% | 25.1s |
|
|
| Sep 4, 2026, 11:45 PM UTC | 76 | 5.35 s | 0.036 | 0 ms | 698 kB | 3/3 | ±1 | 2,483 0% | 25.1s |
|
|
| Aug 28, 2026, 11:24 PM UTC | 80 | 5.34 s | 0.036 | 0 ms | 698 kB | 3/3 | ±5 | 2,268 -9% | 25.7s |
|
|
| Aug 20, 2026, 9:29 PM UTC | 76 | 5.39 s | 0.036 | 0 ms | 698 kB | 3/3 | ±1 | 2,480 0% | 25.4s |
|
|
Embed this score
Use this web component to show eleventy-html5up-txt.appseed.us'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://eleventy-html5up-txt.appseed.us/"></speedlify2-score>