Website review, no card needed

fxrracing.uk logo

fxrracing.uk website review

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

This review found 38 issues worth fixing on fxrracing.uk, 16 of them high impact, across 79 checks. The most urgent: improve image delivery. 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

Full-page screenshot of fxrracing.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fxrracing.uk at 1.3 s1.3 s
  2. fxrracing.uk at 2.6 s2.6 s
  3. fxrracing.uk at 4.0 s4.0 s
  4. fxrracing.uk at 5.3 s5.3 s
  5. fxrracing.uk at 6.6 s6.6 s
  6. fxrracing.uk at 7.9 s7.9 s
  7. fxrracing.uk at 9.3 s9.3 s
  8. fxrracing.uk at 10.6 s10.6 s

Speed

15 to fix32
  • Improve image delivery

    3.9 s · 1.8 MB

    22 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

  • Signyfyd adds 2.5 s

    2.5 s

    Signyfyd costs a phone 2.5 s of main-thread work and 538 KiB 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.

  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 10.3 s

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

  • Mobile performance score: 32

    32/100

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

  • 3,853 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, negate.io and Google Tag Manager and others), adding 2.3 MB and 3.8 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 929 KiB

    About 929 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 309 ms

    309 ms

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

  • negate.io adds 313 ms

    313 ms

    negate.io costs a phone 313 ms of main-thread work and 40 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.

  • Use efficient cache lifetimes

    305 KiB

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

  • Font display

    300 ms

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

  • Klaviyo adds 197 ms

    197 ms

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

  • Shopify adds 105 ms

    105 ms

    Shopify costs a phone 105 ms of main-thread work and 574 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

    150 ms · 85 KiB

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

  • Legacy JavaScript

    90 KiB

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

    76 ms

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

Core Web Vitals

6 to fix36
  • Largest Contentful Paint: 11.3 s

    11.3 s

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

  • Time to Interactive: 26.9 s

    26.9 s

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

  • Speed Index: 12.7 s

    12.7 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 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.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix42
  • Page weight: 7.2 MB in 350 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 350 requests on a phone: images 3.3 MB (72), scripts 2.6 MB (128) and other files 724 KiB (113). Under 2 MB keeps phones on slow connections fast.

  • 17 images far larger than shown

    920 KiB

    17 images are downloaded at several times the size a phone draws them, for example activity_panel_apparel_mob.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 920 KiB.

  • An image on the first screen is lazy-loaded

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

  • About 2.0 g of CO₂ per visit

    2.05 g

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

4 to fixGoogle 9495
  • Hidden but focusable

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 101 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “FXR Racing - Snow, Motocross, Outdoor, Lifestyle, Race Div., Apparel – FXR Racing Europe”.

  • Meta description is long (302 characters)

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

  • 1,034 internal links, 35 external

    The homepage links to 1,034 pages on fxrracing.uk and 35 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “FXR Racing UK — Snowmobile, Motocross, Pro Fish & Outdoor Gear”.

  • Canonical URL set

    The canonical URL is https://fxrracing.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://fxrracing.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without an H1

    https://fxrracing.uk/collections/shop-by-riding-style, https://fxrracing.uk/collections/snow-27, https://fxrracing.uk/collections/backcountry, https://fxrracing.uk/collections/backcountry-crossover-gear, https://fxrracing.uk/collections/performance-crossover and https://fxrracing.uk/collections/performance-trail and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://fxrracing.uk/pages/snow-buyers-guide and https://fxrracing.uk/collections/mens-monosuits took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 200 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9679
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 7 small tap targets

    7 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'confidence')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 316 words of visible text.

3 checks passed
  • 84 calls to action

    The homepage has 84 calls to action, for example “Shop by Riding Style”, “Shop All” and “Shop by Season”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 21 cookies set on arrival

    21

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

  • 46 other companies contacted

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

Apps your storefront loads

Consentmo Gdpr · Microsoft Clarity · Eg Auto Add To Cart · Judge Me Reviews · Pushowl · Gdpr Backpack · shopiapps.in · signifyd.com · klaviyo.com · kiwisizing.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 38 issues on fxrracing.uk, including 21 speed issues, 2 SEO issues and 3 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