leedsunited.com website review

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

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

elfsightcdn.com costs a phone 1.2 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 203 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 45 (desktop: 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.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

31 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

8 third-party services load with your homepage (elfsightcdn.com, Google Tag Manager and Google/Doubleclick Ads and others), adding 2.4 MB and 1.5 s of main-thread time.

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

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

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

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

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

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.

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

Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “James Trafford Sunderland Oct 26 Staring in warm ups”.

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 115 requests on a phone: images 2.7 MB (33), scripts 2.0 MB (39) and stylesheets 314 KiB (16). Under 2 MB keeps phones on slow connections fast.

Brenden_Aaronson_Sunderland_Oct_26_Battling_for_ball.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).

3 images are downloaded at several times the size a phone draws them, for example Newcastle-United-FC-Crest.png at 600 px wide, shown at 36 px. Resized copies would save about 455 KiB.

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

3 images (471 KiB) 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.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 294 pages on leedsunited.com and 63 external pages.

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.

There is no https://www.leedsunited.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.leedsunited.com/en and / all use the title “Leeds United | Official Website - Leeds United”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.leedsunited.com/en/news/category/mens, https://www.leedsunited.com/en/news/category/video, https://www.leedsunited.com/en/news/bijol-says-leeds-will-take-the-positives-from-sunderland-draw, https://www.leedsunited.com/en/news/we-had-to-dig-in-farke-reflects-on-draw-at-stadium-of-light and https://www.leedsunited.com/en/news/category/matchday have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.leedsunited.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.leedsunited.com/en/news/trafford-takes-top-spot-in-hisense-player-of-the-match-poll, https://www.leedsunited.com/en/news/ampadus-duel-with-cairns-farke-consolation-and-off-camera-moments-from-sunderland-v-leeds, https://www.leedsunited.com/en/news/longstaff-almost-produces-silencer-graham-smyths-verdict-on-sunderland-0-0-leeds-united, https://www.leedsunited.com/en/news/stormy-stalemate-watch-highlights-from-leeds-0-0-draw-with-sunderland, https://www.leedsunited.com/en/news/daniel-farke-makes-point-declaration-after-draw-with-sunderland and https://www.leedsunited.com/en/news/bijol-says-leeds-will-take-the-positives-from-sunderland-draw and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

Large scripts ship without source maps.

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.

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

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.

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 3,602 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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