Website review, no card needed

racing-sport.com logo

racing-sport.com website review

Visit site (opens in a new tab)Reviewed 13 November 202620 issues · 66 checks

This review found 20 issues worth fixing on racing-sport.com, 8 of them high impact, across 66 checks. The most urgent: use efficient cache lifetimes. 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 racing-sport.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. racing-sport.com at 0.4 s0.4 s
  2. racing-sport.com at 0.9 s0.9 s
  3. racing-sport.com at 1.3 s1.3 s
  4. racing-sport.com at 1.7 s1.7 s
  5. racing-sport.com at 2.1 s2.1 s
  6. racing-sport.com at 2.6 s2.6 s
  7. racing-sport.com at 3.0 s3.0 s
  8. racing-sport.com at 3.4 s3.4 s

Speed

6 to fix70
  • Use efficient cache lifetimes

    51.3 s · 24.9 MB

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

  • Improve image delivery

    36.0 s · 16.8 MB

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

  • Mobile performance score: 70

    70/100

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

  • Font display

    700 ms

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

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • Reduce unused CSS

    300 ms · 61 KiB

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

  • Reduce unused JavaScript

    150 ms · 29 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • 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: 0.6 s

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

  • Server response: 119 ms

    119 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 75.2 s

    75.2 s

    Your largest element takes 75.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Racing Teamwear · Lifestyle · Fan Wear Motorsport-Bekleidun…”.

  • Time to Interactive: 77.4 s

    77.4 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • 20 images without width and height

    20 images 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.

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix70
  • Page weight: 24.9 MB in 62 requests

    24.9 MB

    Your homepage downloads 24.9 MB in 62 requests on a phone: images 24.6 MB (29), scripts 156 KiB (28) and fonts 71 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (38 KiB) is 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.

  • About 7.1 g of CO₂ per visit

    7.06 g

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

2 checks passed
  • 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

5 to fixGoogle 9293
  • Certain ARIA roles must contain particular children (1 element)

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

  • 1 form field without a label

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 69 internal links, 0 external

    The homepage links to 69 pages on racing-sport.com and 0 external pages.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Entdecke offizielle Motorsport-Bekleidung, F1-Fanartikel, Kappen, Taschen und Racewear im Racing-Sport-Shop. Schnelle L…”.

  • One H1 headline

    Your main headline reads: “Motorsport-Bekleidung & F1-Fanartikel”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Motorsport-Bekleidung & F1-Fanartikel | Racing Sport”.

  • Canonical URL set

    The canonical URL is https://www.racing-sport.com/.

  • 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://www.racing-sport.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.racing-sport.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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 12 pages without a meta description

    https://www.racing-sport.com/bekleidung/t-shirts, https://www.racing-sport.com/bekleidung/poloshirts, https://www.racing-sport.com/bekleidung/sweater, https://www.racing-sport.com/bekleidung/jacken, https://www.racing-sport.com/bekleidung/hosen and https://www.racing-sport.com/bekleidung/shorts and 6 others 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 46 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.

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 356 words of copy

    The homepage carries about 356 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Start”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 6 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 racing-sport.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics
Hosting
IONOS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on racing-sport.com, including 10 speed issues, 1 SEO issue and 1 conversion gap. 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