Website review, no card needed
despetitshauts.com website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 84 checks
This review found 38 issues worth fixing on despetitshauts.com, 15 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
77C- #66,230 of 118,374 reviewed websitesbeats 39%
- #43,148 of 67,255 online storesbeats 31%
- #41,088 of 61,325 Shopify storesbeats 28%
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.6 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 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.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 159 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 182 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 188 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 197 ms |
| Jul 18, 2026 | 200 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 199 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 192 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 169 ms |
| Oct 31, 2026 | 173 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
0.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Use efficient cache lifetimes
1.8 s · 530 KiB18 files are served with short cache lifetimes, so returning visitors download them again (530 KiB).
Reduce unused JavaScript
1.2 s · 711 KiBAbout 711 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.5 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
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
600 ms · 202 KiB4 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Klarna and others), adding 1.1 MB and 659 ms of main-thread time.
Reduce unused CSS
450 ms · 69 KiBAbout 69 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.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 235 ms
235 msGoogle Tag Manager costs a phone 235 ms of main-thread work and 462 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.
1,867 HTML elements
The page has 1,867 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Duplicated JavaScript
12 KiB12 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 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.
Largest Contentful Paint: 12.2 s
12.2 sYour largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 291 ms
291 msScripts block taps and scrolling for 291 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 159 ms to 173 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-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).
5 checks passed
Real-user INP: 155 ms
155 msReal visitors wait 155 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: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 599 ms
599 msReal visitors wait 599 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 362 requests
4.2 MBYour homepage downloads 4.2 MB in 362 requests on a phone: scripts 1.8 MB (101), other files 1.2 MB (212) and images 869 KiB (26). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 144.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
48 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: 48 passed and 8 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.
Meta description is long (194 characters)
Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.
139 internal links, 9 external
The homepage links to 139 pages on despetitshauts.com and 9 external pages.
6 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “Des Petits Hauts | Vêtements Femme | Automne-Hiver 2026”.
Canonical URL set
The canonical URL is https://despetitshauts.com/.
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://despetitshauts.com/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 (781 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://despetitshauts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://despetitshauts.com/pages/wishlist, https://despetitshauts.com/pages/aide, https://despetitshauts.com/collections/coups-de-coeur and https://despetitshauts.com/collections/dernieres-nouveautes have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://despetitshauts.com/collections/bloom, https://despetitshauts.com/collections/pret-a-porter and https://despetitshauts.com/collections/jeans 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 77 found) and read each the way a search engine does.
5 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.
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
11 small tap targets
11 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'currentVisitorConsent')”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 246 words
The homepage has only about 246 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
2 calls to action
The homepage has 2 calls to action, for example “Shop” and “Shop now”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
33 cookies set on arrival
33Opening the homepage sets 33 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.
32 other companies contacted
Loading the homepage contacts 32 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 despetitshauts.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Sortd Merchandiser · Wisepops Popup Builder Cro · Microsoft Clarity · Orbe Geolocation · Simple Social Login
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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 95
- Founded
- 1998
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on despetitshauts.com, including 17 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.