Website review, no card needed
bofrost.fr website review
Visit site (opens in a new tab)Reviewed 31 October 202641 issues · 91 checks
This review found 41 issues worth fixing on bofrost.fr, 20 of them high impact, across 91 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 109 ms |
| May 16, 2026 | 108 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 142 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 137 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
Improve image delivery
2.0 s · 1.3 MB26 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,241 HTML elements
The page has 3,241 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
750 ms · 413 KiBAbout 413 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
500 ms · 172 KiB24 files are served with short cache lifetimes, so returning visitors download them again (172 KiB).
Reduce unused CSS
300 ms · 95 KiBAbout 95 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 789 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 203 ms
203 msGoogle Tag Manager costs a phone 203 ms of main-thread work and 328 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and iTunes and others), adding 668 KiB and 293 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Minify JavaScript
18 KiB18 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: 446 ms
446 msYour server sent the HTML in 446 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.
Real-user CLS: 0.54
0.54For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.784
0.784The layout shifts by 0.784 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “accras de cabillaud bofrost*”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 109 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 653 ms
653 msReal visitors wait 653 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 141 ms
141 msScripts block the page for only 141 ms while loading. Good is under 200 ms.
Images and page weight
8 images far larger than shown
652 KiB8 images are downloaded at several times the size a phone draws them, for example interactive-image.jpg at 1,600 px wide, shown at 370 px. Resized copies would save about 652 KiB.
Page weight: 3.6 MB in 102 requests
3.6 MBYour homepage downloads 3.6 MB in 102 requests on a phone: images 2.2 MB (48), scripts 1.0 MB (34) and fonts 147 KiB (5). Under 2 MB keeps phones on slow connections fast.
19 images below the first screen load straight away
19 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (415 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.
About 1.0 g of CO₂ per visit
1.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (5 elements)
Certain ARIA roles must contain particular children: 5 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”.
Required ARIA attributes must be provided (2 elements)
Required ARIA attributes must be provided: 2 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
Positive tabindex
41 elements have a tabindex above 0, which scrambles the keyboard order.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Orphan list items
Some list items are not inside a list.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail 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.
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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails 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. (12 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
103 internal links, 9 external
The homepage links to 103 pages on bofrost.fr and 9 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Vous aimerez sûrement”.
Title: 35 characters
Your title is a healthy 35 characters: “Vous offre le meilleur | bofrost.fr”.
Canonical URL set
The canonical URL is https://www.bofrost.fr/.
Structured data in place
Structured data found: Organization.
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.bofrost.at/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.bofrost.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.
Text is in the HTML
Your server sends the page's text in the HTML (890 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.bofrost.fr/offre-de-bienvenue.html and https://www.bofrost.fr/nos_recettes_bofrost are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
11 pages without a meta description
https://www.bofrost.fr/offre-de-bienvenue.html, https://www.bofrost.fr/catalogue, https://www.bofrost.fr/contact.html, https://www.bofrost.fr/shop, https://www.bofrost.fr/nos_recettes_bofrost and https://www.bofrost.fr/shop/selection-du-moment_60187 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 links to non-canonical URLs
Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.bofrost.fr/shop, whose canonical is https://www.bofrost.fr/shop?categoryCode=SHOP-ROOT-CATEGORY. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.bofrost.fr/offre-de-bienvenue.html, https://www.bofrost.fr/catalogue, https://www.bofrost.fr/univers-thematiques.html and https://www.bofrost.fr/qualite-service/service/le-fonctionnement-bofrost.html 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 45 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
79 small tap targets
79 of 167 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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 885 words of copy
The homepage carries about 885 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
35 short forms
35 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 9 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 bofrost.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
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Azure
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 bofrost.fr, including 18 speed issues and 2 SEO issues. 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.