Website review, no card needed
bodemerauto.com website review
Visit site (opens in a new tab)Reviewed 26 October 202641 issues · 75 checks
This review found 41 issues worth fixing on bodemerauto.com, 16 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 189 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 189 ms |
| Jun 13, 2026 | 198 ms |
| Jun 20, 2026 | 208 ms |
| Jun 27, 2026 | 213 ms |
| Jul 4, 2026 | 219 ms |
| Jul 11, 2026 | 219 ms |
| Jul 18, 2026 | 217 ms |
| Jul 25, 2026 | 211 ms |
| Aug 1, 2026 | 210 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 211 ms |
| Aug 22, 2026 | 212 ms |
| Aug 29, 2026 | 212 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 212 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 212 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 219 ms |
| Oct 24, 2026 | 218 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
How it loaded on a phone
1.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
8.9 s
10.2 s
Speed
Use efficient cache lifetimes
4.3 s · 3.4 MB75 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Reduce unused JavaScript
3.0 s · 499 KiBAbout 499 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Font display
1.8 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.8 s).
Render-blocking requests
1.7 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
300 ms · 2.0 MB22 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, tarteaucitron.io and ovh.net and others), adding 457 KiB and 623 ms of main-thread time.
Google Tag Manager adds 480 ms
480 msGoogle Tag Manager costs a phone 480 ms of main-thread work and 195 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.
Legacy JavaScript
300 ms · 77 KiBPolyfills for old browsers add 77 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 979 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,108 HTML elements
The page has 2,108 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 242 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 33 KiBAbout 33 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 checks passed
Server response: 95 ms
95 msYour server sent the HTML in 95 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 12.5 s
12.5 sYour largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Achetez votre voiture neuve ou occasion au meilleur prix en…”. Most of its time is resource load delay (6.9 s).
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.7 s
12.7 sThe page becomes fully interactive after 12.7 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 565 ms
565 msScripts block taps and scrolling for 565 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.196
0.196The layout shifts by 0.196 while loading, so content jumps under the reader's thumb. Good is under 0.1.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 189 ms to 218 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 3.9 MB in 86 requests
3.9 MBYour homepage downloads 3.9 MB in 86 requests on a phone: images 2.7 MB (55), scripts 806 KiB (15) and fonts 253 KiB (9). Under 2 MB keeps phones on slow connections fast.
16 images in older formats
16 images (2.1 MB) 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.
10 images below the first screen load straight away
10 images further down the page (358 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.5 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
32 tap targets too small
32 tap targets are too small or too close together to hit reliably with a finger.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
ARIA role should be appropriate for the element (18 elements)
ARIA role should be appropriate for the element: 18 elements on the page fail this check, rated minor by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
49 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: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (270 characters)
Your meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
175 internal links, 51 external
The homepage links to 175 pages on bodemerauto.com and 51 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Achetez votre voiture neuve ou occasion au meilleur prix en Bretagne et en Normandie”.
Title: 65 characters
Your title is a healthy 65 characters: “BodemerAuto : Voitures Neuves et Occasion Automobile dans l'Ouest”.
Canonical URL set
The canonical URL is https://www.bodemerauto.com/.
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.bodemerauto.com/sitemaps/lists-vehicles.xml.
AI search readiness
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.bodemerauto.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 (2,079 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 116 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
16 small tap targets
16 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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
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 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 1,758 words of copy
The homepage carries about 1,758 words of visible text.
4 checks passed
1 short form
A short form (2 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
7 other companies contacted
Loading the homepage contacts 7 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 bodemerauto.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on bodemerauto.com, including 21 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.