Website review, no card needed
atome3d.com website review
Visit site (opens in a new tab)Reviewed 4 November 202661 issues · 96 checks
This review found 61 issues worth fixing on atome3d.com, 25 of them high impact, across 96 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
60D- #114,228 of 117,360 reviewed websitesbeats 2%
- #66,269 of 66,896 online storesbeats 1%
- #60,570 of 61,004 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 137 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 182 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 184 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 185 ms |
| Oct 24, 2026 | 184 ms |
| Oct 31, 2026 | 184 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.9 s
3.7 s
5.6 s
7.5 s
9.4 s
11.2 s
13.1 s
15.0 s
Speed
Improve image delivery
3.6 s · 1.3 MB17 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 3.6 s faster on a phone.
Reduce unused JavaScript
2.3 s · 647 KiBAbout 647 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
1.9 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
19,028 HTML elements
The page has 19,028 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
1.5 s · 341 KiB26 files are served with short cache lifetimes, so returning visitors download them again (341 KiB).
Main-thread work: 10.4 s
A phone's processor spends 10.4 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (chatra.io, Facebook and Shopify and others), adding 1.7 MB and 761 ms of main-thread time.
Reduce unused CSS
450 ms · 64 KiBAbout 64 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 389 ms. During a long task the page ignores taps.
chatra.io adds 350 ms
350 mschatra.io costs a phone 350 ms of main-thread work and 339 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.
Shopify adds 97 ms
97 msShopify costs a phone 97 ms of main-thread work and 842 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
150 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 20 ms
20 msYour server sent the HTML in 20 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 LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 19.1 s
19.1 sYour largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 294 ms
294 msReal visitors wait 294 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.204
0.204The layout shifts by 0.204 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 390 ms
390 msScripts block taps and scrolling for 390 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 460 ms
460 msReal visitors wait 460 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.6 MB in 589 requests
6.6 MBYour homepage downloads 6.6 MB in 589 requests on a phone: images 2.8 MB (89), scripts 1.8 MB (150) and other files 1.4 MB (306). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
header-anim-v2-2550x164.gif weighs 1.5 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.2 MB1 image is downloaded at several times the size a phone draws it, for example header-anim-v2-2550x164.gif at 2,550 px wide, shown at 360 px. Resized copies would save about 1.2 MB.
3 images in older formats
3 images (2.0 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.
1 image below the first screen load straight away
1 image further down the page (312 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.86 g of CO₂e: 223.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
187 buttons without a name
187 buttons have no accessible name, so screen readers announce just “button”.
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
24 tap targets too small
24 tap targets are too small or too close together to hit reliably with a finger.
<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.
27 images without alt text
27 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1,348 elements)
All page content should be contained by landmarks: 1,348 elements on the page fail this check, rated moderate by axe-core.
245 form fields without a label
245 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
43 links without text
43 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 failed. 3 mores 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.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Atome3D Le Leader de la Distribution d’Imprimantes 3D en France Europe”.
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 (313 characters)
Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
1,525 internal links, 30 external
The homepage links to 1,525 pages on atome3d.com and 30 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.atome3d.com/.
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.atome3d.com/sitemap.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.
3 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 (17,319 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.atome3d.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.atome3d.com/blogs/news, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
https://www.atome3d.com/pages/nos-franchises-partout-en-france-europe-et-dom and https://www.atome3d.com/pages/localisation-nos-magasins-et-agences-partout-en-france-europe-et-dompour-acheter-une-imprimante-3d-et-filament all use the title “Atome3D.com - Trouver Nos Agences et Magasins Atome3D à Travers la Fr…”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.atome3d.com/collections/tout-les-laser, https://www.atome3d.com/collections/nos-imprimantes-uv and https://www.atome3d.com/collections/fraiseuses-cnc have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.atome3d.com/pages/nos-franchises-partout-en-france-europe-et-dom and https://www.atome3d.com/pages/localisation-nos-magasins-et-agences-partout-en-france-europe-et-dompour-acheter-une-imprimante-3d-et-filament use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.atome3d.com/pages/nos-franchises-partout-en-france-europe-et-dom, whose canonical is https://www.atome3d.com/pages/localisation-nos-magasins-et-agences-partout-en-france-europe-et-dompour-acheter-une-imprimante-3d-et-filament. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://www.atome3d.com/collections/black-friday-2026, https://www.atome3d.com/pages/demande-devis-atome3d, https://www.atome3d.com/pages/quote-request, https://www.atome3d.com/pages/nos-franchises-partout-en-france-europe-et-dom, https://www.atome3d.com/pages/localisation-nos-magasins-et-agences-partout-en-france-europe-et-dompour-acheter-une-imprimante-3d-et-filament and https://www.atome3d.com/collections/achat-imprimante-3d-france-au-meilleur-prix and 8 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 197 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://fraats.atome3d.com/g/uids?pld=-PmXxE7iX5LWGhZKijflR6HenHwgVsCsym44zgHv07Z_ReSvAgtU-ohjsGOzDCXuzak1FBUp7i4FOk6WXRNjxM8EeHhRzFGFmaZVNIq5UHZRkbvLpPRSDFEGlFVVxyFlJZpZma95NqrR2ypkmJawJQHuWYCWnJLtQN.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
172 of 202 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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
About 4,229 words of copy
The homepage carries about 4,229 words of visible text.
7 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Ask for a quote”, “FEP Shop FEP Shop” and “Demande de devis Ask for a quote”.
122 short forms
122 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 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.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 2 mores (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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (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.
45 other companies contacted
Loading the homepage contacts 45 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 atome3d.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Url Shortener Snipit · Forms · goaffpro.com · chatra.io · cloudfront.net · doofinder.com · conversionbear.com · klaviyo.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 | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 61 issues on atome3d.com, including 25 speed issues, 5 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.