Website review, no card needed

speedway.fr logo

speedway.fr website review

Visit site (opens in a new tab)Reviewed 25 October 202650 issues · 100 checks

This review found 50 issues worth fixing on speedway.fr, 22 of them high impact, across 100 checks. The most urgent: render-blocking requests. 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
2.0 s1.8 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
172 ms153 msMay 2Oct 17157 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026155 ms
May 9, 2026155 ms
May 16, 2026156 ms
May 23, 2026158 ms
May 30, 2026160 ms
Jun 6, 2026161 ms
Jun 13, 2026161 ms
Jun 20, 2026162 ms
Jun 27, 2026163 ms
Jul 4, 2026166 ms
Jul 11, 2026169 ms
Jul 18, 2026169 ms
Jul 25, 2026168 ms
Aug 1, 2026168 ms
Aug 8, 2026168 ms
Aug 15, 2026170 ms
Aug 22, 2026170 ms
Aug 29, 2026169 ms
Sep 5, 2026167 ms
Sep 12, 2026165 ms
Sep 19, 2026163 ms
Sep 26, 2026163 ms
Oct 3, 2026161 ms
Oct 10, 2026158 ms
Oct 17, 2026157 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 speedway.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. speedway.fr at 1.1 s1.1 s
  2. speedway.fr at 2.2 s2.2 s
  3. speedway.fr at 3.3 s3.3 s
  4. speedway.fr at 4.4 s4.4 s
  5. speedway.fr at 5.5 s5.5 s
  6. speedway.fr at 6.6 s6.6 s
  7. speedway.fr at 7.7 s7.7 s
  8. speedway.fr at 8.8 s8.8 s

Speed

12 to fix31
  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 31

    31/100

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

  • 5,377 HTML elements

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, beyable.com and iAdvize SAS and others), adding 858 KiB and 1.5 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 320 KiB

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

  • Google Tag Manager adds 605 ms

    605 ms

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

  • beyable.com adds 431 ms

    431 ms

    beyable.com costs a phone 431 ms of main-thread work and 108 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.

  • Improve image delivery

    428 KiB

    18 images could be 428 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    300 ms · 77 KiB

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

  • iAdvize SAS adds 323 ms

    323 ms

    iAdvize SAS costs a phone 323 ms of main-thread work and 222 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.

  • 17 long tasks on the main thread

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

  • Use efficient cache lifetimes

    230 KiB

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

  • Legacy JavaScript

    150 ms · 7 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 71 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    6 KiB

    6 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: 329 ms

    329 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Time to Interactive: 16.2 s

    16.2 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mois anniversaire : Des remises sur les accessoires moto”.

  • Total Blocking Time: 870 ms

    870 ms

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Real-user CLS: 0.23

    0.23

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

  • Cumulative Layout Shift: 0.225

    0.225

    The layout shifts by 0.225 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

4 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 123 ms

    123 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 693 ms

    693 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.6 MB in 173 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 173 requests on a phone: images 1.6 MB (74), scripts 964 KiB (56) and other files 593 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (169 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.

  • 2 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.01 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

17 to fixGoogle 5680
  • Images must have alternative text (6 elements)

    Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.

  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 20 tap targets too small

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

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA input fields must have an accessible name (2 elements)

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

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (40 elements)

    All page content should be contained by landmarks: 40 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Zoom is disabled

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

  • Hidden but focusable

    7 elements hidden from screen readers can still receive keyboard focus.

  • 6 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.speedway.fr/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 410 internal links, 7 external

    The homepage links to 410 pages on speedway.fr and 7 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “L'Equipement Moto, Scooter, Enduro et Cross à Prix Imbattable ! Livraison & Retour GRATUIT. Un choix immense parmi les …”.

  • One H1 headline

    Your main headline reads: “Équipez votre passion : L'accessoire moto qu'il vous faut est chez Speedway”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Accessoire et équipement Moto, Scooter et Cross - Speedway.fr”.

  • Canonical URL set

    The canonical URL is https://www.speedway.fr/.

  • Structured data in place

    Structured data found: Corporation and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

3 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,147 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix80
  • 5 linked pages hidden from search

    https://www.speedway.fr/mois-anniversaire, https://www.speedway.fr/mois-anniversaire-cadeau, https://www.speedway.fr/mois-anniversaire-cross, https://www.speedway.fr/mois-anniversaire-motard and https://www.speedway.fr/mois-anniversaire-technique are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    https://www.speedway.fr/mois-anniversaire, https://www.speedway.fr/mois-anniversaire-cross, https://www.speedway.fr/mois-anniversaire-motard and https://www.speedway.fr/mois-anniversaire-technique all use the title “Le Mois Anniversaire Speedway - Speedway”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.speedway.fr/mois-anniversaire, https://www.speedway.fr/mois-anniversaire-cadeau, https://www.speedway.fr/mois-anniversaire-cross, https://www.speedway.fr/mois-anniversaire-motard and https://www.speedway.fr/mois-anniversaire-technique have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://www.speedway.fr/mois-anniversaire took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 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 an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6974
  • 1 broken image

    1 image failed to load on a phone, for example https://dyzmpx.speedway.fr/g/uids?pld=JGcaTsfDLVYvfgRYVprLbyN1RANwM-f16PbEyPTTzN1VL_pHBV513cvzQQaqH4FcbQHlHk5jEVlcja31FKxsOj6RQmmIxfj3xhj7vscplnTHZv2mtLaIM-n0ffs1_iWSqa-NsdcsUhKDgJ3UxYbGAtR1CVrf6ya3rH.

  • 20 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 2,287 words of copy

    The homepage carries about 2,287 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Aide & Contact”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Criteo 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.

  • 10 cookies set on arrival

    10

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 speedway.fr, 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 Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on speedway.fr, including 20 speed issues, 2 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