Website review, no card needed

foxracing.ch logo

foxracing.ch website review

Visit site (opens in a new tab)Reviewed 9 November 202623 issues · 70 checks

This review found 23 issues worth fixing on foxracing.ch, 6 of them high impact, across 70 checks. The most urgent: no call to action on the first screen. 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 s904 msMay 23Nov 7931 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 2026988 ms
Jun 13, 2026948 ms
Jun 20, 2026926 ms
Jun 27, 2026927 ms
Jul 4, 2026937 ms
Jul 11, 2026956 ms
Jul 18, 2026962 ms
Jul 25, 2026948 ms
Aug 1, 2026957 ms
Aug 8, 2026987 ms
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.0 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 2026960 ms
Oct 17, 2026927 ms
Oct 24, 2026930 ms
Oct 31, 2026934 ms
Nov 7, 2026931 ms
Real-visitor tap response (INP)75th percentile, phones
111 ms94 msMay 23Nov 7102 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202699 ms
May 30, 2026101 ms
Jun 6, 202699 ms
Jun 13, 202697 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 2026101 ms
Jul 11, 2026103 ms
Jul 18, 2026103 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026106 ms
Sep 19, 2026109 ms
Sep 26, 2026106 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 2026102 ms
Oct 24, 2026101 ms
Oct 31, 2026104 ms
Nov 7, 2026102 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 foxracing.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. foxracing.ch at 0.7 s0.7 s
  2. foxracing.ch at 1.5 s1.5 s
  3. foxracing.ch at 2.2 s2.2 s
  4. foxracing.ch at 3.0 s3.0 s
  5. foxracing.ch at 3.7 s3.7 s
  6. foxracing.ch at 4.4 s4.4 s
  7. foxracing.ch at 5.2 s5.2 s
  8. foxracing.ch at 5.9 s5.9 s

Speed

6 to fix77
  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    800 ms

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

  • Improve image delivery

    500 ms · 212 KiB

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

  • Reduce unused JavaScript

    300 ms · 309 KiB

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

  • ZenDesk adds 162 ms

    162 ms

    ZenDesk costs a phone 162 ms of main-thread work and 431 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.

  • 1,556 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (ZenDesk, Shopify and JSDelivr CDN and others), adding 548 KiB and 201 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    13 KiB

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

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 468 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (3.9 s).

  • Time to Interactive: 5.1 s

    5.1 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 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: 0.8 s

    0.8 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 42 ms

    42 ms

    Scripts block the page for only 42 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 148 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 148 requests on a phone: other files 736 KiB (82), scripts 699 KiB (46) and images 565 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10096
  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

  • 13 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

Google 100100
  • 248 internal links, 4 external

    The homepage links to 248 pages on foxracing.ch and 4 external pages.

8 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “FOX Racing ist die bekannteste und meistverkaufte Marke im MX- und MTB-Bereich und die Bekleidungswahl der Actionsportl…”.

  • One H1 headline

    Your main headline reads: “Autumn Essentials”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “FOX Racing® Schweiz | MX, MTB & Sportkleidung”.

  • Canonical URL set

    The canonical URL is https://foxracing.ch/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://foxracing.ch/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

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

  • No llms.txt

    There is no https://foxracing.ch/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.

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

Other pages

1 to fix95
  • 2 pages without an H1

    https://foxracing.ch/pages/mountainbike and https://foxracing.ch/pages/mtb-bekleidungsets have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 calls to action

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

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 84 words

    The homepage has only about 84 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 4 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Klaviyo, Meta Pixel and Microsoft Ads (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.

  • 8 cookies set on arrival

    8

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

  • 10 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews

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

E-commerce
Shopify
Hosting
Shopify

Company

Founded
1974
Headquarters
Morgan Hill

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on foxracing.ch, including 9 speed issues and 5 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