keithjames.com website review

Signyfyd costs a phone 1.3 s of main-thread work and 280 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Signyfyd, POWr and Google Tag Manager and others), adding 1,008 KiB and 1.7 s of main-thread time.

22 images could be 456 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

Shopify costs a phone 59 ms of main-thread work and 465 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.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

About 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

8 KiB could be saved by minifying JavaScript.

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.

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

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

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

The first text or image appears after 4.4 s on a phone. Good is under 1.8 s.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.7 MB in 209 requests on a phone: images 1,010 KiB (64), other files 747 KiB (85) and scripts 722 KiB (49). Under 2 MB keeps phones on slow connections fast.

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

18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 tap targets are too small or too close together to hit reliably with a finger.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

The homepage links to 79 pages on keithjames.com and 2 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://keithjames.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.

https://keithjames.com/collections/our-hat-collection has no meta description, so Google writes the search snippet from whatever text it finds.

https://keithjames.com/collections/our-hat-collection has no <h1> headline, so visitors and search engines get no clear main topic.

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

21 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 207 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 12 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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