Website review, no card needed
facom.fr website review
Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 81 checks
This review found 32 issues worth fixing on facom.fr, 11 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
81B- #37,300 of 109,987 reviewed websitesbeats 60%
- #24,920 of 62,419 online storesbeats 54%
- #24,047 of 56,942 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 126 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 128 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
Reduce unused JavaScript
1.9 s · 383 KiBAbout 383 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 397 KiB20 files are served with short cache lifetimes, so returning visitors download them again (397 KiB).
3,752 HTML elements
The page has 3,752 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
862 KiB17 images could be 862 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Google Tag Manager and Optanon and others), adding 1.1 MB and 535 ms of main-thread time.
Render-blocking requests
300 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Yotpo adds 204 ms
204 msYotpo costs a phone 204 ms of main-thread work and 483 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 51 KiBAbout 51 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.8 s
13.8 sYour largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.2 s
14.2 sThe page becomes fully interactive after 14.2 s. Good is under 3.8 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 221 ms
221 msScripts block taps and scrolling for 221 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 396 ms
396 msReal visitors wait 396 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 272 requests
3.3 MBYour homepage downloads 3.3 MB in 272 requests on a phone: images 1.3 MB (59), scripts 934 KiB (54) and other files 721 KiB (116). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Banniere_FACOM_2.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.9 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
21 images without alt text
21 images have no alt text, which hurts accessibility and image search.
95 links without text
95 visible links have no text or label, so screen readers cannot say where they go.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “FACOM, expert en outillage et rangement professionnel en France depuis – FACOM FRANCE”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
262 internal links, 16 external
The homepage links to 262 pages on facom.fr and 16 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “FACOM, tout l'univers des outils à main et des équipements professionnels pour les métiers de l'industrie, de l'automob…”.
One H1 headline
Your main headline reads: “FACOM : Un outillage d'excellence, au service des professionnels!”.
Canonical URL set
The canonical URL is https://www.facom.fr/.
Structured data in place
Structured data found: 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://www.facom.fr/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,704 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.facom.fr/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without an H1
https://www.facom.fr/collections/outillage-general, https://www.facom.fr/collections/serrage, https://www.facom.fr/collections/cles-a-ouverture-fixe-et-variable, https://www.facom.fr/collections/cles-dynamometriques, https://www.facom.fr/collections/cliquets-douilles and https://www.facom.fr/collections/vissage and 6 others 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 146 found) and read each the way a search engine does.
6 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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-widget-assets.yotpo.com/ReviewsCarousel/SyUZq1WNMzhzTaG7iCBDEyc53aL9bvqAr6KF7h…”.
2 checks passed
Tap targets are thumb-sized
132 of 145 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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,919 words of copy
The homepage carries about 1,919 words of visible text.
2 checks passed
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 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 facom.fr, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
C Hub Customer Accounts · Helium Customer Fields · Sortd Merchandiser · Iwish · yotpo.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on facom.fr, including 15 speed issues, 2 SEO issues and 4 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.