Website review, no card needed
breizh-modelisme.com website review
Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 78 checks
This review found 35 issues worth fixing on breizh-modelisme.com, 11 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
77C- #69,578 of 125,559 reviewed websitesbeats 39%
- #44,804 of 70,209 online storesbeats 31%
- #42,581 of 63,780 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 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.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 131 ms |
| May 23, 2026 | 131 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 155 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 165 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 193 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.3 s · 1.1 MB34 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,682 HTML elements
The page has 4,682 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, Shopify and Cookiebot and others), adding 3.5 MB and 1.3 s of main-thread time.
Use efficient cache lifetimes
600 ms · 942 KiB39 files are served with short cache lifetimes, so returning visitors download them again (942 KiB).
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
hcaptcha.com adds 667 ms
667 mshcaptcha.com costs a phone 667 ms of main-thread work and 1.2 MB 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.
Shopify adds 318 ms
318 msShopify costs a phone 318 ms of main-thread work and 1.5 MB 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.
Render-blocking requests
450 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
300 ms · 122 KiBAbout 122 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 382 ms. During a long task the page ignores taps.
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
Minify JavaScript
27 KiB27 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: 17 ms
17 msYour server sent the HTML in 17 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: 19.0 s
19.0 sYour largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 38.4 s
38.4 sThe page becomes fully interactive after 38.4 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 804 ms
804 msReal visitors wait 804 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 361 ms
361 msScripts block taps and scrolling for 361 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 200 ms
200 msReal visitors wait 200 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.7 MB in 627 requests
9.7 MBYour homepage downloads 9.7 MB in 627 requests on a phone: images 4.6 MB (101), scripts 2.8 MB (202) and other files 1.4 MB (284). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.75 g of CO₂e: 329.8 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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 checks passed
16 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 19 WCAG 2.2 A/AA and best-practice rules on the phone render: 16 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,239 internal links, 19 external
The homepage links to 1,239 pages on breizh-modelisme.com and 19 external pages.
8 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Retrouvez tout l'univers RC : Voiture, Avions, Engins de chantier, bateau télécommandés chez Breizh Modélisme. Livraiso…”.
One H1 headline
Your main headline reads: “Breizh Modélisme”.
Title: 60 characters
Your title is a healthy 60 characters: “Breizh Modélisme : Voiture RC, Bateaux, Avion télécommandés.”.
Canonical URL set
The canonical URL is https://breizh-modelisme.com/.
Structured data in place
Structured data found: BreadcrumbList, ItemList, 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://breizh-modelisme.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://breizh-modelisme.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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Other pages
1 page without a title
https://breizh-modelisme.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://breizh-modelisme.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://breizh-modelisme.com/blogs/videos and https://breizh-modelisme.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://breizh-modelisme.com/pages/faq-du-modelisme-rc and https://breizh-modelisme.com/customer_authentication/redirect 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 197 found) and read each the way a search engine does.
3 checks passed
Linked pages load
8 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.
Titles are unique
Every page we checked has its own title.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'cloneNode')”.
1 checks passed
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 26 words
The homepage has only about 26 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Démarreurs Roto Start”, “Contact” and “Contact et services”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 31 testimonial or review blocks, a star rating and 1 trust badge.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
48 other companies contacted
Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 breizh-modelisme.com, 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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Searchpie Seo Speed · Instafeed · Fbp Fast Bundle · Sensefuel Personalized Search · Region Restrictions · Forms · Now In Stock · Convi · Loyalty Program · Swishlist · cloudfront.net · trustpilot.com
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
- CMS
- WordPress
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on breizh-modelisme.com, including 20 speed issues and 6 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.