Website review, no card needed

sportstradingcardsuk.com logo

sportstradingcardsuk.com website review

Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 86 checks

This review found 36 issues worth fixing on sportstradingcardsuk.com, 9 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
973 ms885 msMay 23Nov 7963 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026920 ms
May 30, 2026907 ms
Jun 6, 2026910 ms
Jun 13, 2026925 ms
Jun 20, 2026935 ms
Jun 27, 2026952 ms
Jul 4, 2026949 ms
Jul 11, 2026927 ms
Jul 18, 2026927 ms
Jul 25, 2026911 ms
Aug 1, 2026901 ms
Aug 8, 2026900 ms
Aug 15, 2026895 ms
Aug 22, 2026908 ms
Aug 29, 2026919 ms
Sep 5, 2026929 ms
Sep 12, 2026945 ms
Sep 19, 2026948 ms
Sep 26, 2026956 ms
Oct 3, 2026938 ms
Oct 10, 2026918 ms
Oct 17, 2026920 ms
Oct 24, 2026926 ms
Oct 31, 2026942 ms
Nov 7, 2026963 ms
Real-visitor tap response (INP)75th percentile, phones
141 ms109 msMay 23Nov 7137 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026113 ms
May 30, 2026116 ms
Jun 6, 2026123 ms
Jun 13, 2026128 ms
Jun 20, 2026129 ms
Jun 27, 2026130 ms
Jul 4, 2026129 ms
Jul 11, 2026126 ms
Jul 18, 2026125 ms
Jul 25, 2026122 ms
Aug 1, 2026123 ms
Aug 8, 2026124 ms
Aug 15, 2026125 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026133 ms
Sep 12, 2026136 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026136 ms
Oct 17, 2026135 ms
Oct 24, 2026135 ms
Oct 31, 2026135 ms
Nov 7, 2026137 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 sportstradingcardsuk.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sportstradingcardsuk.com at 0.8 s0.8 s
  2. sportstradingcardsuk.com at 1.6 s1.6 s
  3. sportstradingcardsuk.com at 2.4 s2.4 s
  4. sportstradingcardsuk.com at 3.2 s3.2 s
  5. sportstradingcardsuk.com at 4.0 s4.0 s
  6. sportstradingcardsuk.com at 4.7 s4.7 s
  7. sportstradingcardsuk.com at 5.5 s5.5 s
  8. sportstradingcardsuk.com at 6.3 s6.3 s

Speed

13 to fix51
  • Reduce unused JavaScript

    3.5 s · 632 KiB

    About 632 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 241 KiB

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

  • Improve image delivery

    800 ms · 1.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 3.8 MB and 1.2 s of main-thread time.

  • Mobile performance score: 51

    51/100

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

  • Shopify adds 371 ms

    371 ms

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

  • Render-blocking requests

    600 ms

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

  • Main-thread work: 3.9 s

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

  • Reduce unused CSS

    300 ms · 39 KiB

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

  • Google Tag Manager adds 244 ms

    244 ms

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

  • Klaviyo adds 208 ms

    208 ms

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

  • 2,054 HTML elements

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

  • Google CDN adds 123 ms

    123 ms

    Google CDN costs a phone 123 ms of main-thread work and 298 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.

  • Legacy JavaScript

    200 ms · 60 KiB

    Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 11 long tasks on the main thread

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

  • 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: 30 ms

    30 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 20.3 s

    20.3 s

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

  • Time to Interactive: 20.6 s

    20.6 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 405 ms

    405 ms

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

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

    +19%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 160 ms

    160 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 448 ms

    448 ms

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

  • Cumulative Layout Shift: 0.067

    0.067

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

Images and page weight

5 to fix43
  • Page weight: 5.7 MB in 356 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 356 requests on a phone: images 2.6 MB (46), scripts 1.9 MB (127) and other files 891 KiB (140). Under 2 MB keeps phones on slow connections fast.

  • 33 images in older formats

    33 images (2.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 24 images below the first screen load straight away

    24 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    New_Website_750x.png 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).

  • 1 image far larger than shown

    1 KiB

    1 image is downloaded at several times the size a phone draws it, for example STCUK_Trading_Cards_UK_Web_GraphicsArtboard_1_550x.png at 359 px wide, shown at 119 px. Resized copies would save about 1 KiB.

  • About 1.6 g of CO₂ per visit

    1.62 g

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

Accessibility

4 to fixGoogle 9495
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (4 elements)

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

  • 14 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3 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.

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • Meta description is long (267 characters)

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

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

  • One H1 headline

    Your <h1> is empty.

  • 117 internal links, 11 external

    The homepage links to 117 pages on sportstradingcardsuk.com and 11 external pages.

5 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Sports Trading Cards UK - Huge range of US sports cards and more”.

  • Canonical URL set

    The canonical URL is https://sportstradingcardsuk.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://sportstradingcardsuk.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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 (686 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without a meta description

    https://sportstradingcardsuk.com/collections/new-in-store, https://sportstradingcardsuk.com/collections/soccer-boxes, https://sportstradingcardsuk.com/collections/soccer-boxes-1, https://sportstradingcardsuk.com/collections/soccer-blasters-and-packs, https://sportstradingcardsuk.com/collections/nfl and https://sportstradingcardsuk.com/collections/boxes and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://sportstradingcardsuk.com/collections/basketball-boxes took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR”.

2 checks passed
  • Tap targets are thumb-sized

    74 of 89 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 direct contact details

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

  • 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 658 words of copy

    The homepage carries about 658 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 ALL COLLECTIONS”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “Contact us” and “Shop All Collections”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: a star rating and “over 1,000 reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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.

  • 44 other companies contacted

    Loading the homepage contacts 44 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 sportstradingcardsuk.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Wiser Upsell Cross Sell · Klaviyo Email Marketing Sms · Collection Cart · optimonk.com · crucialcommerceapps.com · trustpilot.com · chimpstatic.com · elfsight.com

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on sportstradingcardsuk.com, including 18 speed issues, 4 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