Website review, no card needed

alanpaine-germany.com logo

alanpaine-germany.com website review

Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 80 checks

This review found 28 issues worth fixing on alanpaine-germany.com, 8 of them high impact, across 80 checks. The most urgent: page weight: 19.7 MB in 291 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.2 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
196 ms102 msMay 16Oct 31185 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026114 ms
May 30, 2026122 ms
Jun 6, 2026137 ms
Jun 13, 2026136 ms
Jun 20, 2026137 ms
Jun 27, 2026140 ms
Jul 4, 2026137 ms
Jul 11, 2026154 ms
Jul 18, 2026153 ms
Jul 25, 2026155 ms
Aug 1, 2026172 ms
Aug 8, 2026167 ms
Aug 15, 2026169 ms
Aug 22, 2026170 ms
Aug 29, 2026171 ms
Sep 5, 2026178 ms
Sep 12, 2026179 ms
Sep 19, 2026183 ms
Sep 26, 2026178 ms
Oct 3, 2026179 ms
Oct 10, 2026182 ms
Oct 17, 2026179 ms
Oct 24, 2026178 ms
Oct 31, 2026185 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of alanpaine-germany.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alanpaine-germany.com at 0.4 s0.4 s
  2. alanpaine-germany.com at 0.8 s0.8 s
  3. alanpaine-germany.com at 1.1 s1.1 s
  4. alanpaine-germany.com at 1.5 s1.5 s
  5. alanpaine-germany.com at 1.9 s1.9 s
  6. alanpaine-germany.com at 2.3 s2.3 s
  7. alanpaine-germany.com at 2.6 s2.6 s
  8. alanpaine-germany.com at 3.0 s3.0 s

Speed

8 to fix74
  • Render-blocking requests

    1.3 s

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

  • 3,334 HTML elements

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

  • Mobile performance score: 74

    74/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Yotpo and Shopify and others), adding 1.2 MB and 635 ms of main-thread time.

  • Improve image delivery

    300 ms · 359 KiB

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

  • Reduce unused JavaScript

    150 ms · 308 KiB

    About 308 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.

  • Klaviyo adds 262 ms

    262 ms

    Klaviyo costs a phone 262 ms of main-thread work and 636 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.

  • Main-thread work: 3.0 s

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

  • Use efficient cache lifetimes

    150 ms · 153 KiB

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

  • Reduce unused CSS

    150 ms · 52 KiB

    About 52 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 long tasks on the main thread

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

  • Legacy JavaScript

    27 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 6.6 s

    6.6 s

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

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Tap response (INP) got 60% slower for real visitors

    +60%

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

  • Real-user TTFB: 916 ms

    916 ms

    Real visitors wait 916 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.8 s

    3.8 s

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 123 ms

    123 ms

    Scripts block the page for only 123 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.012

    0.012

    The layout barely moves while loading (CLS 0.012, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 19.7 MB in 291 requests

    19.7 MB

    Your homepage downloads 19.7 MB in 291 requests on a phone: media 15.8 MB (3), scripts 1.3 MB (104) and images 1.3 MB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (182 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.6 g of CO₂ per visit

    5.58 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8996
  • 1 text element with low contrast

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

  • 3 images without alt text

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9292
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “OVER A CENTURY OF CRAFT”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 288 internal links, 16 external

    The homepage links to 288 pages on alanpaine-germany.com and 16 external pages.

6 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Shop the official Alan Paine website. Discover our entire collection of designer knitwear & countryside essentials.”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Alan Paine Country Clothing & Knitwear | Official Alan Paine”.

  • Canonical URL set

    The canonical URL is https://www.us.alanpaine.co.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.us.alanpaine.co.uk/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,465 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.us.alanpaine.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.us.alanpaine.co.uk/collections/mens-best-sellers, https://www.us.alanpaine.co.uk/collections/knitwear-essentials, https://www.us.alanpaine.co.uk/collections/the-gentlemans-edit and https://www.us.alanpaine.co.uk/collections/mens-british-classics have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.us.alanpaine.co.uk/collections/autumn-arrivals, https://www.us.alanpaine.co.uk/collections/mens-lambswool-jumpers, https://www.us.alanpaine.co.uk/collections/alan-paine-combrook-collection, https://www.us.alanpaine.co.uk/collections/mens-shetland-wool-jumpers, https://www.us.alanpaine.co.uk/collections/cardigans and https://www.us.alanpaine.co.uk/collections/rutland-range and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.us.alanpaine.co.uk/collections/mens-best-sellers and https://www.us.alanpaine.co.uk/collections/the-gentlemans-edit took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    18 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • Only about 220 words

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

  • No risk reducer

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP COLLECTION”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SHOP BY COLOUR”, “Shop collection” and “Shop”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 21 cookies set on arrival

    21

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

  • No consent tool detected

    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.

  • 36 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at alanpaine-germany.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geoip Country Redirect · Gorgias Live Chat Helpdesk · Yotpo Loyalty Rewards · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Store Locator · Propel Replays · Bestpush · roseperl.com · amazonaws.com · Selleasy

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on alanpaine-germany.com, including 14 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25