Website review, no card needed
deuxpardeux.com website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 91 checks
This review found 40 issues worth fixing on deuxpardeux.com, 16 of them high impact, across 91 checks. The most urgent: main-thread work: 12.7 s. 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
75C- #76,371 of 115,529 reviewed websitesbeats 30%
- #49,371 of 66,525 online storesbeats 22%
- #46,738 of 60,790 Shopify storesbeats 19%
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.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 318 ms |
| May 23, 2026 | 322 ms |
| May 30, 2026 | 332 ms |
| Jun 6, 2026 | 337 ms |
| Jun 13, 2026 | 338 ms |
| Jun 20, 2026 | 329 ms |
| Jun 27, 2026 | 321 ms |
| Jul 4, 2026 | 298 ms |
| Jul 11, 2026 | 281 ms |
| Jul 18, 2026 | 279 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 267 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 240 ms |
| Sep 12, 2026 | 236 ms |
| Sep 19, 2026 | 229 ms |
| Sep 26, 2026 | 228 ms |
| Oct 3, 2026 | 225 ms |
| Oct 10, 2026 | 224 ms |
| Oct 17, 2026 | 228 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 230 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.9 s
5.8 s
7.8 s
9.7 s
11.6 s
13.6 s
15.5 s
Speed
Main-thread work: 12.7 s
A phone's processor spends 12.7 s on main-thread work while loading, 3.5 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.
6,390 HTML elements
The page has 6,390 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 (heatmap.com, Shopify and Klaviyo and others), adding 1.7 MB and 1.1 s of main-thread time.
Improve image delivery
150 ms · 765 KiB22 images could be 765 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.
Use efficient cache lifetimes
678 KiB20 files are served with short cache lifetimes, so returning visitors download them again (678 KiB).
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 510 ms. During a long task the page ignores taps.
Reduce unused JavaScript
464 KiBAbout 464 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 57 KiBAbout 57 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.
Shopify adds 256 ms
256 msShopify costs a phone 256 ms of main-thread work and 894 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.
heatmap.com adds 304 ms
304 msheatmap.com costs a phone 304 ms of main-thread work and 94 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.
Klaviyo adds 239 ms
239 msKlaviyo costs a phone 239 ms of main-thread work and 390 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
59 KiBPolyfills for old browsers add 59 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Speed Index: 20.4 s
20.4 sVisually, the page fills in at 20.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 25.0 s
25.0 sThe page becomes fully interactive after 25.0 s. Good is under 3.8 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “up to 40% off”.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 935 ms
935 msReal visitors wait 935 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 156 ms
156 msReal visitors wait 156 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.
Tap response (INP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 318 ms to 230 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 607 requests
5.9 MBYour homepage downloads 5.9 MB in 607 requests on a phone: scripts 1.8 MB (207), images 1.7 MB (37) and other files 1.5 MB (317). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.67 g of CO₂e: 200.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).
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 (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (8 elements)
ARIA role should be appropriate for the element: 8 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
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 2 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
1,084 internal links, 25 external
The homepage links to 1,084 pages on deuxpardeux.com and 25 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “The best baby and children's clothing store in Canada! Designed in Montreal. High quality clothing; shop online today! …”.
Title: 65 characters
Your title is a healthy 65 characters: “Online clothing store for babies and children | Deux par Deux USA”.
Canonical URL set
The canonical URL is https://deuxpardeux.com/en-us.
Structured data in place
Structured data found: OnlineStore.
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://deuxpardeux.com/sitemap.xml.
AI search readiness
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.
llms.txt published
The site publishes https://deuxpardeux.com/llms.txt (14 KiB, 95 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a title
https://deuxpardeux.com/en-us/collections/the-snow-shop, https://deuxpardeux.com/en-us/collections/snow-shop-girls-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-boys-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-baby-girls-winter-clothing and https://deuxpardeux.com/en-us/collections/snow-shop-baby-boys-winter-clothing all use the title “Snow shop - Kids' winter suit | Deux par Deux USA”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://deuxpardeux.com/en-us/collections/the-snow-shop, https://deuxpardeux.com/en-us/collections/snow-shop-girls-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-boys-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-baby-girls-winter-clothing and https://deuxpardeux.com/en-us/collections/snow-shop-baby-boys-winter-clothing use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://deuxpardeux.com/en-us/collections/girl, https://deuxpardeux.com/en-us/collections/boy, https://deuxpardeux.com/en-us/collections/baby-girl, https://deuxpardeux.com/en-us/collections/baby-boy, https://deuxpardeux.com/en-us/collections/the-snow-shop and https://deuxpardeux.com/en-us/collections/black-friday-deals and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://deuxpardeux.com/en-us/collections/snow-shop-girls-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-boys-winter-clothing, https://deuxpardeux.com/en-us/collections/snow-shop-baby-boys-winter-clothing and https://deuxpardeux.com/en-us/collections/base-layers have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 185 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Missing source maps
Large scripts ship without source maps.
Requests the notification permission on page load
Requests the notification permission on page load.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
24 of 25 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 street address 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.
Only about 54 words
The homepage has only about 54 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
38 calls to action
The homepage has 38 calls to action, for example “Snow Shop”, “The Snow Shop” and “Shop by gender”.
62 short forms
62 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and PostHog.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Microsoft Ads, Pinterest Tag and TikTok Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 24 of them by other companies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 deuxpardeux.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Intelligems A B Testing · Triplewhale · Addingwell · Black Crow Ai That Delivers · Klaviyo Email Marketing Sms · Tapcart Mobile App · Postscript Sms Marketing · Region Restrictions · Pushowl · Test Sms · 56071677a62720b5cde4241477474f626e61c35a · Pixiehog · Lhg Badges Deux Par Deux · rise-ai.com · oxiapps.com · glopal.com · socialsnowball.io · influencer-hero.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | PostHog
- Hosting
- Shopify
Company
- Headquarters
- Montreal
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on deuxpardeux.com, including 21 speed issues, 2 SEO 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.