Website review, no card needed

allopneus.com logo

allopneus.com website review

Visit site (opens in a new tab)Reviewed 19 October 202636 issues · 88 checks

This review found 36 issues worth fixing on allopneus.com, 13 of them high impact, across 88 checks. The most urgent: mobile performance score: 41. 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.3 sApr 25Oct 101.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.9 s
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
148 ms125 msApr 25Oct 10129 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026145 ms
May 2, 2026128 ms
May 9, 2026128 ms
May 16, 2026128 ms
May 23, 2026128 ms
May 30, 2026129 ms
Jun 6, 2026130 ms
Jun 13, 2026130 ms
Jun 20, 2026130 ms
Jun 27, 2026130 ms
Jul 4, 2026129 ms
Jul 11, 2026130 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026129 ms
Sep 26, 2026129 ms
Oct 3, 2026129 ms
Oct 10, 2026129 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 allopneus.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allopneus.com at 0.5 s0.5 s
  2. allopneus.com at 1.0 s1.0 s
  3. allopneus.com at 1.5 s1.5 s
  4. allopneus.com at 2.1 s2.1 s
  5. allopneus.com at 2.6 s2.6 s
  6. allopneus.com at 3.1 s3.1 s
  7. allopneus.com at 3.6 s3.6 s
  8. allopneus.com at 4.1 s4.1 s

Speed

8 to fix41
  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 4.2 s

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

  • Use efficient cache lifetimes

    100 ms · 822 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (captcha-delivery.com, Optanon and Kameleoon and others), adding 790 KiB and 599 ms of main-thread time.

  • captcha-delivery.com adds 439 ms

    439 ms

    captcha-delivery.com costs a phone 439 ms of main-thread work and 399 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

    371 KiB

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

  • Reduce unused JavaScript

    365 KiB

    About 365 KiB of JavaScript is downloaded but never used on this page.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 184 KiB

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

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

    216 ms

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

Core Web Vitals

9 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: 14.1 s

    14.1 s

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

  • Largest Contentful Paint: 5.5 s

    5.5 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Real-user CLS: 0.12

    0.12

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

  • 35 images without width and height

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

  • Cumulative Layout Shift: 0.175

    0.175

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

5 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 135 ms

    135 ms

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

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

    410 ms

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

  • Largest content (LCP) got 26% faster for real visitors

    -26%

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 167 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 167 requests on a phone: scripts 1.5 MB (67), images 827 KiB (51) and other files 147 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.75 g

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

8 to fixGoogle 8890
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

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

  • Malformed lists

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

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

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

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate 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.

  • 2 form fields without a label

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

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

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 85 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • 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 X (Twitter) card tag

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

  • 214 internal links, 9 external

    The homepage links to 214 pages on allopneus.com and 9 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Trouvez tous vos pneus pas chers chez Allopneus | Jusqu'à -50% sur 27000 pneus ! Livraison 0€ dès 2 pneus ! Livraison e…”.

  • One H1 headline

    Your main headline reads: “Si simple de fairechanger ses pneus.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Pneu pas cher ALLOPNEUS - Achat Pneus en Ligne - Allopneus.com”.

  • Canonical URL set

    The canonical URL is https://www.allopneus.com/.

  • Structured data in place

    Structured data found: FAQPage, 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.allopneus.com/sitemapindex.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.allopneus.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
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7385
  • 7 small tap targets

    7 of 24 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.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks, 4 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Company

Founded
2004
Headquarters
Aix-en-Provence

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on allopneus.com, including 17 speed issues, 1 SEO issue 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