thesoccerarchive.com website review

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

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

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

8 third-party services load with your homepage (ContentSquare, Google Tag Manager and Shopify and others), adding 977 KiB and 636 ms of main-thread time.

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

ContentSquare costs a phone 360 ms of main-thread work and 185 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.

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

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

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

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

3 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 251 requests on a phone: other files 1.2 MB (131), scripts 904 KiB (64) and fonts 519 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Structured data found (ClothingStore, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

A phone browser shows 875 words, but the HTML your server sends has only 17. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing logo, 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.

https://thesoccerarchive.com/collections/new-in has no <h1> headline, so visitors and search engines get no clear main topic.

https://thesoccerarchive.com/collections/new-in has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 1 page linked from your homepage and read each the way a search engine does.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 875 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Pinterest Tag and TikTok 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 16 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.