Website review, no card needed
bernard.fr website review
Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 88 checks
This review found 39 issues worth fixing on bernard.fr, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 317 ms |
| May 9, 2026 | 314 ms |
| May 16, 2026 | 314 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 312 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 315 ms |
| Jun 20, 2026 | 316 ms |
| Jun 27, 2026 | 319 ms |
| Jul 4, 2026 | 320 ms |
| Jul 11, 2026 | 318 ms |
| Jul 18, 2026 | 317 ms |
| Jul 25, 2026 | 317 ms |
| Aug 1, 2026 | 324 ms |
| Aug 8, 2026 | 328 ms |
| Aug 15, 2026 | 330 ms |
| Aug 22, 2026 | 337 ms |
| Aug 29, 2026 | 336 ms |
| Sep 5, 2026 | 337 ms |
| Sep 12, 2026 | 341 ms |
| Sep 19, 2026 | 338 ms |
| Sep 26, 2026 | 336 ms |
| Oct 3, 2026 | 335 ms |
| Oct 10, 2026 | 331 ms |
| Oct 17, 2026 | 331 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
Speed
Render-blocking requests
1.2 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Improve image delivery
2.0 MB43 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 71
71/100Your mobile performance score is 71 (desktop: 52). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
979 KiBAbout 979 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 613 KiB127 files are served with short cache lifetimes, so returning visitors download them again (613 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Optanon and Other Google APIs/SDKs and others), adding 1.5 MB and 489 ms of main-thread time.
Reduce unused CSS
450 ms · 133 KiBAbout 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 358 ms
358 msGoogle CDN costs a phone 358 ms of main-thread work and 1.1 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,788 HTML elements
The page has 1,788 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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: 182 ms
182 msYour server sent the HTML in 182 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.
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.275
0.275The layout shifts by 0.275 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 351 ms
351 msReal visitors wait 351 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 925 ms
925 msReal visitors wait 925 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Chez Bernard nous utilisons des cookies avec nos partenaire…”. Most of its time is element render delay (1.4 s).
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 317 ms to 331 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-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (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.
Total Blocking Time: 106 ms
106 msScripts block the page for only 106 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.0 MB in 158 requests
6.0 MBYour homepage downloads 6.0 MB in 158 requests on a phone: images 3.1 MB (89), scripts 1.9 MB (35) and other files 452 KiB (16). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (108 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 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.1 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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
23 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 3 problems
Structured data found (LocalBusiness, Organization and Website) but with 3 problems, for example “Organization: logo is not an absolute URL ("https://www.bernard.fr/INTERSHOP/static/WFS/RAJA-BERNARDFR-Site/-/RAJA-BERNAR…”.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
255 internal links, 7 external
The homepage links to 255 pages on bernard.fr and 7 external pages.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Bernard, fournisseur professionnel hygiène, entretien et sécurité au service des entreprises. 18000 références professi…”.
Title: 61 characters
Your title is a healthy 61 characters: “Bernard, votre fournisseur professionnel hygiène et entretien”.
Canonical URL set
The canonical URL is https://www.bernard.fr/.
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.bernard.fr/sitemap/Sitemap_HTTPS.
AI search readiness
No llms.txt
There is no https://www.bernard.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.
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, description and contact details; sameAs (social profiles) would complete it.
Other pages
4 pages share a title
https://www.bernard.fr/produits-responsables_cms_000945.html, https://www.bernard.fr/produits-d-hygiene_C10.html, https://www.bernard.fr/produits-d-entretien_C09.html and https://www.bernard.fr/materiel-d-entretien_C07.html all use the title “Radware Bot Manager Captcha”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.bernard.fr/produits-responsables_cms_000945.html, https://www.bernard.fr/produits-d-hygiene_C10.html, https://www.bernard.fr/produits-d-entretien_C09.html and https://www.bernard.fr/materiel-d-entretien_C07.html have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages with very little text
https://www.bernard.fr/produits-responsables_cms_000945.html, https://www.bernard.fr/produits-d-hygiene_C10.html, https://www.bernard.fr/produits-d-entretien_C09.html and https://www.bernard.fr/materiel-d-entretien_C07.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://captcha.perfdrive.com/captcha-public/css/shieldsquare_styles.min.css' from origin …”.
Missing source maps
Large scripts ship without source maps.
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.
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.
Only about 83 words
The homepage has only about 83 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
7 checks passed
4 short forms
4 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks, 4 customer or partner logos, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 7 of them by other companies (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.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 bernard.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
Hiring
- Hiring
- 7 open roles
- Teams
- Product & Engineering (5), Growth (1), Operations (1)
- Job board
- ashby
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bernard.fr, including 20 speed issues, 4 SEO issues and 3 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.