Website review, no card needed

kxkshop.uk logo

kxkshop.uk website review

Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 82 checks

This review found 35 issues worth fixing on kxkshop.uk, 11 of them high impact, across 82 checks. The most urgent: render-blocking 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
5.6 s2.8 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.1 s
Jun 6, 20265.3 s
Jun 13, 20265.1 s
Jun 20, 20265.0 s
Jun 27, 20264.8 s
Jul 4, 20264.0 s
Jul 11, 20263.9 s
Jul 18, 20263.5 s
Jul 25, 20263.3 s
Aug 1, 20263.4 s
Aug 8, 20263.2 s
Aug 15, 20263.1 s
Aug 22, 20263.3 s
Sep 5, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.3 s
Oct 24, 20263.5 s
Oct 31, 20263.6 s
Nov 7, 20263.4 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
392 ms227 msMay 30Nov 7279 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026251 ms
Jun 6, 2026253 ms
Jun 13, 2026264 ms
Jun 20, 2026277 ms
Jun 27, 2026301 ms
Jul 4, 2026334 ms
Jul 11, 2026338 ms
Jul 18, 2026328 ms
Jul 25, 2026304 ms
Aug 1, 2026312 ms
Aug 8, 2026339 ms
Aug 15, 2026369 ms
Aug 22, 2026373 ms
Sep 5, 2026355 ms
Oct 17, 2026246 ms
Nov 7, 2026279 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 kxkshop.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kxkshop.uk at 0.5 s0.5 s
  2. kxkshop.uk at 1.0 s1.0 s
  3. kxkshop.uk at 1.4 s1.4 s
  4. kxkshop.uk at 1.9 s1.9 s
  5. kxkshop.uk at 2.4 s2.4 s
  6. kxkshop.uk at 2.9 s2.9 s
  7. kxkshop.uk at 3.4 s3.4 s
  8. kxkshop.uk at 3.9 s3.9 s

Speed

8 to fix70
  • Render-blocking requests

    1.1 s

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

  • 6,825 HTML elements

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

  • Improve image delivery

    150 ms · 1.0 MB

    35 images could be 1.0 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.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70. 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 (Shopify, loox.io and omnisnippet1.com and others), adding 3.1 MB and 597 ms of main-thread time.

  • Shopify adds 289 ms

    289 ms

    Shopify costs a phone 289 ms of main-thread work and 2.2 MB 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.1 s

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

  • loox.io adds 228 ms

    228 ms

    loox.io costs a phone 228 ms of main-thread work and 677 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.

  • Reduce unused JavaScript

    222 KiB

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

  • Reduce unused CSS

    150 ms · 67 KiB

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

  • Use efficient cache lifetimes

    214 KiB

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

  • Font display

    100 ms

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    7 KiB

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

  • 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.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

9 to fix0
  • 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.

  • Real-user CLS: 0.60

    0.60

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

  • Time to Interactive: 21.4 s

    21.4 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • 34 images without width and height

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

  • Cumulative Layout Shift: 0.115

    0.115

    The layout shifts by 0.115 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user TTFB: 601 ms

    601 ms

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

  • Largest content (LCP) got 33% faster for real visitors

    -33%

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

  • First Contentful Paint: 1.6 s

    1.6 s

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

  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

3 to fix60
  • Page weight: 5.1 MB in 448 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 448 requests on a phone: images 2.7 MB (86), scripts 1.1 MB (196) and other files 854 KiB (137). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    new-kxkshop-homepage-m_3.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).

  • 2 images far larger than shown

    97 KiB

    2 images are downloaded at several times the size a phone draws them, for example new-home-school-img1.png at 1,404 px wide, shown at 354 px. Resized copies would save about 97 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (227 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.45 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8692
  • 10 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 4 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 8588
  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “KXKSHOP Custom Kits | Football, Rugby, Basketball & More – Made for Eu – KXK-EU”.

  • No social preview image

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

  • 1 link with vague text

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

  • 1,032 internal links, 3 external

    The homepage links to 1,032 pages on kxkshop.uk and 3 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “KXKSHOP offers premium custom sportswear across Europe – football,baseball, rugby, basketball kits & more. Design onlin…”.

  • One H1 headline

    Your main headline reads: “KXK-EU”.

  • Canonical URL set

    The canonical URL is https://www.kxkshop.uk/.

  • Structured data in place

    Structured data found: Organization.

  • 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.kxkshop.uk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), 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.

3 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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://www.kxkshop.uk/collections/football-best-seller, https://www.kxkshop.uk/collections/basketball-best-seller, https://www.kxkshop.uk/collections/best-seller-hockey-jersey, https://www.kxkshop.uk/collections/hoodie-best-seller, https://www.kxkshop.uk/collections/softball-best-seller-jersey and https://www.kxkshop.uk/collections/netball-dress-best-sller and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.kxkshop.uk/collections/football-best-seller, https://www.kxkshop.uk/collections/basketball-best-seller, https://www.kxkshop.uk/collections/best-selling-baseball-jerseys, https://www.kxkshop.uk/collections/rugby-best-seller, https://www.kxkshop.uk/collections/best-seller-hockey-jersey and https://www.kxkshop.uk/collections/best-selling-baseball-jackets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 200 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 9684
  • 2 broken images

    2 images failed to load on a phone, for example https://www.kxkshop.uk/.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No analytics detected

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

  • 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.

  • About 771 words of copy

    The homepage carries about 771 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 52 calls to action

    The homepage has 52 calls to action, for example “Shop By Styles”, “Shop By Holiday” and “Shop By Holidays”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 441 testimonial or review blocks, 40 customer or partner logos, a star rating, 4 trust badges and “500,000+ customers”.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 6 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 kxkshop.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on kxkshop.uk, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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