Website review, no card needed
naali.fr website review
Visit site (opens in a new tab)Reviewed 19 November 202653 issues · 97 checks
This review found 53 issues worth fixing on naali.fr, 24 of them high impact, across 97 checks. The most urgent: page weight: 61.0 MB in 589 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
60D- #119,106 of 122,447 reviewed websitesbeats 2%
- #68,503 of 69,158 online storesbeats 1%
- #62,549 of 63,002 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 210 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 236 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 269 ms |
| Jul 4, 2026 | 276 ms |
| Jul 11, 2026 | 261 ms |
| Jul 18, 2026 | 247 ms |
| Jul 25, 2026 | 241 ms |
| Aug 1, 2026 | 238 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 254 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 247 ms |
| Sep 5, 2026 | 224 ms |
| Sep 12, 2026 | 215 ms |
| Sep 19, 2026 | 210 ms |
| Sep 26, 2026 | 207 ms |
| Oct 3, 2026 | 209 ms |
| Oct 10, 2026 | 209 ms |
| Oct 17, 2026 | 211 ms |
| Oct 24, 2026 | 207 ms |
| Oct 31, 2026 | 208 ms |
| Nov 7, 2026 | 200 ms |
| Nov 14, 2026 | 201 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
2.0 s · 954 KiBAbout 954 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Main-thread work: 16.5 s
A phone's processor spends 16.5 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 7
7/100Your mobile performance score is 7. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,873 HTML elements
The page has 4,873 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (replocdn.com, alia-prod.com and Clarity and others), adding 57.6 MB and 2.4 s of main-thread time.
Shopify adds 169 ms
169 msShopify costs a phone 169 ms of main-thread work and 55.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.
Use efficient cache lifetimes
250 ms · 861 KiB29 files are served with short cache lifetimes, so returning visitors download them again (861 KiB).
replocdn.com adds 932 ms
932 msreplocdn.com costs a phone 932 ms of main-thread work and 1,018 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 461 ms. During a long task the page ignores taps.
alia-prod.com adds 434 ms
434 msalia-prod.com costs a phone 434 ms of main-thread work and 271 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.
Improve image delivery
434 KiB14 images could be 434 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
300 ms · 105 KiBAbout 105 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.
rebuyengine.com adds 244 ms
244 msrebuyengine.com costs a phone 244 ms of main-thread work and 891 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
250 ms · 127 KiBPolyfills for old browsers add 127 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 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).
Minify JavaScript
42 KiB42 KiB could be saved by minifying JavaScript.
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
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: 25 ms
25 msYour server sent the HTML in 25 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.69
0.69For real visitors the layout shifts by 0.69 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 298.5 s
298.5 sYour largest element takes 298.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 28.0 s
28.0 sVisually, the page fills in at 28.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 298.6 s
298.6 sThe page becomes fully interactive after 298.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.817
0.817The layout shifts by 0.817 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 343 ms
343 msReal visitors wait 343 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
22 images without width and height
22 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-11-14, real Chrome visitors' tap response (inp) went from 210 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 373 ms
373 msReal visitors wait 373 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 61.0 MB in 589 requests
61.0 MBYour homepage downloads 61.0 MB in 589 requests on a phone: media 54.8 MB (7), scripts 3.0 MB (119) and other files 1.7 MB (361). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
93c3e7e8-bd1b-4ee2-9a17-6ed261fc760c 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).
1 image below the first screen load straight away
1 image further down the page (122 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 17.3 g of CO₂ per visit
17.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.30 g of CO₂e: 2076.0 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
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
ARIA commands must have an accessible name (7 elements)
ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
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.
64 images without alt text
64 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
ARIA role should be appropriate for the element (9 elements)
ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 11 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (240 characters)
Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
68 internal links, 5 external
The homepage links to 68 pages on naali.fr and 5 external pages.
6 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “NAALI - L'expert des compléments alimentaires au safran pur”.
Canonical URL set
The canonical URL is https://naali.fr/.
Structured data in place
Structured data found: BreadcrumbList, 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://naali.fr/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.
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 (2,766 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://naali.fr/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://naali.fr/products/dream-gummies-sommeil-sub-otp-29-90 and https://naali.fr/products/dream are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages share 3 titles
https://naali.fr/products/safran-kids-sticks and https://naali.fr/products/zenkids-gommes-tdah all use the title “Safran Kids : complément enfant goût pomme dès 4 ans | Naali”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://naali.fr/collections/meilleures-ventes, https://naali.fr/products/dream-gummies-sommeil-sub-otp-29-90, https://naali.fr/products/magnesium-sub, https://naali.fr/products/magnesium, https://naali.fr/products/dream and https://naali.fr/collections/beaute and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://naali.fr/products/safran-kids-sticks and https://naali.fr/products/zenkids-gommes-tdah use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://naali.fr/products/magnesium, whose canonical is https://naali.fr/products/magnesium-sub. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://naali.fr/collections/meilleures-ventes, https://naali.fr/collections/beaute, https://naali.fr/collections/sante-feminine, https://naali.fr/pages/resultats-gummies-anti-stress, https://naali.fr/pages/notre-safran and https://naali.fr/pages/notre-mission and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://naali.fr/products/dream took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://files.alia-prod.com/11373/c81123d0ffb2b196.webp.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
38 of 45 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 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 3,250 words of copy
The homepage carries about 3,250 words of visible text.
4 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
42 cookies set on arrival
42Opening the homepage sets 42 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.
55 other companies contacted
Loading the homepage contacts 55 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 naali.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Qtrack · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Addingwell · Yotpo Product Reviews · Microsoft Clarity · Rebuy Personalization Engine · Aftersell · Freegifts · storeify.app · goaffpro.com · snapchat.com · gorgias.chat · cloudfront.net · googleapis.com · bogos.io · 9gtb.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on naali.fr, including 25 speed issues, 2 SEO issues and 2 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.