leestafford.de website review

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

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

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

69 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Accessibe Accessibility Overlay and others), adding 1.7 MB and 1.6 s of main-thread time.

About 669 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 532 ms of main-thread work and 773 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.

consentmanager.net costs a phone 308 ms of main-thread work and 136 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.

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

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

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

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

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.

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

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

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

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

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

87 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.7 MB in 387 requests on a phone: images 14.1 MB (201), scripts 1.8 MB (86) and other files 633 KiB (73). Under 2 MB keeps phones on slow connections fast.

32 images are downloaded at several times the size a phone draws them, for example LeeStafford-MoistureBurst_Treatment_Lifestyle-Shopify-1.jpg at 1,500 px wide, shown at 269 px. Resized copies would save about 2.7 MB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 link inside paragraphs relies on colour alone to stand out.

Some list items are not inside a list.

163 images have no alt text, which hurts accessibility and image search.

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

Your title is 84 characters, so Google will cut it off around 60: “Lee Stafford | Offizieller Online-Shop von Lee Stafford Haarpflege – Lee Stafford DE”.

Your canonical URL points to leestafford.com, not leestafford.de, so Google may credit that host instead.

29 links have no real href, so search engines can't follow them.

Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 356 pages on leestafford.de and 14 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 918 words of visible text.

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

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

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