Website review, no card needed
supplend-store.com website review
Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 77 checks
This review found 28 issues worth fixing on supplend-store.com, 7 of them high impact, across 77 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
78C- #58,382 of 114,810 reviewed websitesbeats 44%
- #38,866 of 66,305 online storesbeats 36%
- #37,220 of 60,658 Shopify storesbeats 33%
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 |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 150 ms |
| May 23, 2026 | 146 ms |
| Jun 20, 2026 | 169 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 163 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 161 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 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (GitHub, OptiMonk and Shopify and others), adding 1.4 MB and 812 ms of main-thread time.
Reduce unused JavaScript
300 ms · 579 KiBAbout 579 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
477 KiB15 files are served with short cache lifetimes, so returning visitors download them again (477 KiB).
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 77 KiB3 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
19 KiB19 KiB JavaScript is shipped twice across bundles.
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: 36 ms
36 msYour server sent the HTML in 36 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.214
0.214The layout shifts by 0.214 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 279 ms
279 msScripts block taps and scrolling for 279 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 150 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 3.2 MB in 319 requests
3.2 MBYour homepage downloads 3.2 MB in 319 requests on a phone: scripts 1.5 MB (83), other files 1.1 MB (168) and images 288 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
86 KiB1 image is downloaded at several times the size a phone draws it, for example English.webp at 1,500 px wide, shown at 25 px. Resized copies would save about 86 KiB.
1 image in older formats
1 image (86 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.
2 images below the first screen load straight away
2 images further down the page (113 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail 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.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
57 internal links, 20 external
The homepage links to 57 pages on supplend-store.com and 20 external pages.
8 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Traitez les ongles mycosés avec le stylo Supplend. Formule 100% naturelle pour des ongles sains. Commandez dès maintena…”.
One H1 headline
Your main headline reads: “Stylo de soin des ongles Supplend: éliminez facilement les champignons des ongles”.
Title: 61 characters
Your title is a healthy 61 characters: “Supplend | N°1 Traitement Mycose des Ongles de Pied en France”.
Canonical URL set
The canonical URL is https://supplend.fr/.
Structured data in place
Structured data found: BreadcrumbList, Organization, Store 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://supplend.fr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://supplend.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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (763 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
7 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 6 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.
2 checks passed
Tap targets are thumb-sized
17 of 18 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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 556 words of copy
The homepage carries about 556 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
6 short forms
6 short forms (6 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 1 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.
36 other companies contacted
Loading the homepage contacts 36 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 supplend-store.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Optimonk Popup Cro A B Test · Tinyseo Ai Seo Speed · Kaching Bundles · Hreflang Manager · Pagefly Ai Page Builder · Triplewhale · Sitemap Noindex Pro Seo · Gdpr Cookie Consent · Revoq Eu Withdrawal Button · goaffpro.com · jsdelivr.net · wetracked.io
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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on supplend-store.com, including 14 speed 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.