Website review, no card needed
cocorico.store website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 82 checks
This review found 38 issues worth fixing on cocorico.store, 10 of them high impact, across 82 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
74C- #86,826 of 124,317 reviewed websitesbeats 26%
- #54,546 of 69,848 online storesbeats 18%
- #51,238 of 63,521 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 147 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 173 ms |
| Oct 24, 2026 | 178 ms |
| Oct 31, 2026 | 183 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.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.1 s
5.9 s
Speed
Reduce unused JavaScript
1.4 s · 316 KiBAbout 316 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
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
300 ms · 685 KiB22 images could be 685 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, TikTok and Klaviyo and others), adding 1.5 MB and 643 ms of main-thread time.
Use efficient cache lifetimes
500 ms · 116 KiB19 files are served with short cache lifetimes, so returning visitors download them again (116 KiB).
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,960 HTML elements
The page has 1,960 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 129 ms
129 msKlaviyo costs a phone 129 ms of main-thread work and 317 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 35 ms
35 msShopify costs a phone 35 ms of main-thread work and 716 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 · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 28 KiBAbout 28 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.
Duplicated JavaScript
11 KiB11 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: 9 ms
9 msYour server sent the HTML in 9 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: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “vêtements made in france”.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 147 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 351 ms
351 msScripts block taps and scrolling for 351 ms in total while the page loads. Good is under 200 ms.
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.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (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: 656 ms
656 msReal visitors wait 656 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.6 MB in 271 requests
4.6 MBYour homepage downloads 4.6 MB in 271 requests on a phone: images 2.3 MB (47), scripts 1.1 MB (108) and other files 795 KiB (95). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
jean-1000x1400.jpg 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 1.3 g of CO₂ per visit
1.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.30 g of CO₂e: 155.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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 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.
42 links without text
42 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (15 elements)
Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.
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.
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
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
209 internal links, 14 external
The homepage links to 209 pages on cocorico.store and 14 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Découvrez nos Vêtements 100% Made in France et Accessibles pour Homme, Femme et Enfants ✔️ Fabrication Française ✔️ Ret…”.
One H1 headline
Your main headline reads: “Cocorico, des Vêtements 100% Made in France à petits prix”.
Title: 57 characters
Your title is a healthy 57 characters: “Cocorico : Vêtement 100% Made in France à prix abordables”.
Canonical URL set
The canonical URL is https://www.cocorico.store/.
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.cocorico.store/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.cocorico.store/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: 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,945 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.cocorico.store/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.cocorico.store/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.cocorico.store/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.cocorico.store/collections/promotions-du-moment, https://www.cocorico.store/customer_authentication/redirect, https://www.cocorico.store/collections/idees-cadeaux, https://www.cocorico.store/collections/nouvelle-collection and https://www.cocorico.store/collections/114-polo-homme-made-in-france 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 100 found) and read each the way a search engine does.
3 checks passed
Linked pages load
5 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.
Titles are unique
Every page we checked has its own title.
Best practices
33 small tap targets
33 of 76 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “An error has been thrown while configuring your widget AbortError: signal is aborted without reason AbortError: signal …”.
1 checks passed
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.
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 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 664 words of copy
The homepage carries about 664 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Presse”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
46 other companies contacted
Loading the homepage contacts 46 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 cocorico.store, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- 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 38 issues on cocorico.store, including 19 speed 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.