Website review, no card needed

uspoloassn.co.uk logo

uspoloassn.co.uk website review

Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 86 checks

This review found 38 issues worth fixing on uspoloassn.co.uk, 13 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
1.1 s907 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026980 ms
May 23, 2026965 ms
May 30, 2026955 ms
Jun 6, 2026955 ms
Jun 13, 2026946 ms
Jun 20, 2026933 ms
Jun 27, 2026937 ms
Jul 4, 2026937 ms
Jul 11, 2026931 ms
Jul 18, 2026942 ms
Jul 25, 2026953 ms
Aug 1, 2026967 ms
Aug 8, 2026980 ms
Aug 15, 20261.0 s
Aug 22, 2026993 ms
Aug 29, 2026987 ms
Sep 5, 2026988 ms
Sep 12, 2026994 ms
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
157 ms133 msMay 16Oct 31149 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026136 ms
May 23, 2026137 ms
May 30, 2026140 ms
Jun 6, 2026145 ms
Jun 13, 2026144 ms
Jun 20, 2026141 ms
Jun 27, 2026140 ms
Jul 4, 2026138 ms
Jul 11, 2026137 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026144 ms
Aug 8, 2026149 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026153 ms
Sep 12, 2026151 ms
Sep 19, 2026152 ms
Sep 26, 2026150 ms
Oct 3, 2026150 ms
Oct 10, 2026146 ms
Oct 17, 2026146 ms
Oct 24, 2026146 ms
Oct 31, 2026149 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 uspoloassn.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uspoloassn.co.uk at 2.7 s2.7 s
  2. uspoloassn.co.uk at 5.5 s5.5 s
  3. uspoloassn.co.uk at 8.2 s8.2 s
  4. uspoloassn.co.uk at 11.0 s11.0 s
  5. uspoloassn.co.uk at 13.7 s13.7 s
  6. uspoloassn.co.uk at 16.4 s16.4 s
  7. uspoloassn.co.uk at 19.2 s19.2 s
  8. uspoloassn.co.uk at 21.9 s21.9 s

Speed

11 to fix47
  • Reduce unused JavaScript

    1.1 s · 349 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.2 s

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

  • Improve image delivery

    950 ms · 548 KiB

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    650 ms · 181 KiB

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

  • 15 long tasks on the main thread

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

  • Google Tag Manager adds 306 ms

    306 ms

    Google Tag Manager costs a phone 306 ms of main-thread work and 162 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 248 ms

    248 ms

    Klaviyo costs a phone 248 ms of main-thread work and 324 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,616 HTML elements

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

  • Clarity adds 253 ms

    253 ms

    Clarity costs a phone 253 ms of main-thread work and 30 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 CSS

    40 ms · 34 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Duplicated JavaScript

    11 KiB

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

  • Forced reflow

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.7 s

    15.7 s

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

  • Time to Interactive: 16.0 s

    16.0 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Total Blocking Time: 646 ms

    646 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 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.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: 169 ms

    169 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 420 ms

    420 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.3 MB in 444 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 444 requests on a phone: images 1.5 MB (41), other files 1.4 MB (263) and scripts 1.2 MB (99). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    33 KiB

    4 images are downloaded at several times the size a phone draws them, for example 69950_20260501_FW26_NY_S09_1140.jpg at 600 px wide, shown at 191 px. Resized copies would save about 33 KiB.

  • 3 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.4 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

8 to fixGoogle 8389
  • 12 tap targets too small

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

  • ARIA commands must have an accessible name (6 elements)

    ARIA commands must have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

  • 5 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 123 links without text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 7 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 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: 46 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7777
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “U.S. Polo Assn. Official UK Store - USPA Official UK – U.S. Polo Assn. UK”.

  • Meta description is long (315 characters)

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

  • No social preview image

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

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

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

  • 330 internal links, 20 external

    The homepage links to 330 pages on uspoloassn.co.uk and 20 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.uspoloassn.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.uspoloassn.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,387 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://www.uspoloassn.co.uk/collections/all, https://www.uspoloassn.co.uk/policies/shipping-policy, https://www.uspoloassn.co.uk/collections/kids-new-arrival, https://www.uspoloassn.co.uk/collections/mens-knitwear and https://www.uspoloassn.co.uk/collections/mens-sweatshirts-hoodies have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “initializeCardSwatches is not defined”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

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

    The homepage carries about 500 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP FOR 25% OFF”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “SIGN UP FOR 25% OFF”, “LAST CHANCE TO BUY” and “Learn More”.

  • 9 short forms

    9 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and Hotjar.

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, Hotjar and Klaviyo 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.

  • 18 cookies set on arrival

    18

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 uspoloassn.co.uk, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Bundler Bundles App · Lipscore Reviews · nice-team.net · gorgias.chat · 9gtb.com · amazonaws.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 Analytics | Hotjar | Microsoft Clarity
Hosting
Shopify Hosted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on uspoloassn.co.uk, including 17 speed issues, 6 SEO issues and 2 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