samuelhubbard.com website review

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

A phone's processor spends 4.9 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,277 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Klaviyo, Osano CMP and Clarity and others), adding 1.6 MB and 1.1 s of main-thread time.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

About 644 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

15 images could be 583 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Klaviyo costs a phone 362 ms of main-thread work and 621 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

ZenDesk costs a phone 106 ms of main-thread work and 386 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

16 files are served with short cache lifetimes, so returning visitors download them again (199 KiB).

14 long tasks block the main thread while loading, the longest for 141 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need.

About 25 KiB of CSS is downloaded but never applied on this page.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

The page becomes fully interactive after 19.8 s. Good is under 3.8 s.

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 319 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.9 MB in 485 requests on a phone: images 3.9 MB (182), scripts 1.8 MB (119) and other files 875 KiB (146). Under 2 MB keeps phones on slow connections fast.

Sneakers_Mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 1.95 g of CO₂e: 234.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

7 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 254 pages on samuelhubbard.com and 2 external pages.

There is no https://samuelhubbard.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

The homepage carries about 705 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.