Website review, no card needed
emilyspillow.com website review
Visit site (opens in a new tab)Reviewed 6 November 202640 issues · 83 checks
This review found 40 issues worth fixing on emilyspillow.com, 21 of them high impact, across 83 checks. The most urgent: main-thread work: 17.4 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
66D- #113,149 of 123,924 reviewed websitesbeats 7%
- #66,651 of 69,719 online storesbeats 4%
- #61,108 of 63,424 Shopify storesbeats 3%
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.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 133 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 143 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 157 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 170 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.8 s
3.6 s
5.4 s
7.2 s
9.0 s
10.8 s
12.6 s
14.4 s
Speed
Main-thread work: 17.4 s
A phone's processor spends 17.4 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
1.1 s · 463 KiBAbout 463 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
1.0 s · 443 KiB10 images could be 443 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 24
24/100Your mobile performance score is 24. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,646 HTML elements
The page has 5,646 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 (Hotjar, Shopify and Clarity and others), adding 1.1 MB and 1.8 s of main-thread time.
Use efficient cache lifetimes
650 ms · 388 KiB31 files are served with short cache lifetimes, so returning visitors download them again (388 KiB).
Hotjar adds 701 ms
701 msHotjar costs a phone 701 ms of main-thread work and 65 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 334 ms
334 msShopify costs a phone 334 ms of main-thread work and 522 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 347 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 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: 17.6 s
17.6 sYour largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.333
0.333The layout shifts by 0.333 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 201 ms
201 msReal visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 133 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.8 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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 519 ms
519 msReal visitors wait 519 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.5 MB in 362 requests
4.5 MBYour homepage downloads 4.5 MB in 362 requests on a phone: scripts 1.9 MB (129), images 963 KiB (30) and other files 927 KiB (138). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (116 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.4 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
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
19 tap targets too small
19 tap targets are too small or too close together to hit reliably with a finger.
[role="img"] and [role="image"] elements must have alternative text (3 elements)
[role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious 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.
Orphan list items
Some list items are not inside a list.
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 10 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Emily's Pillow - Taie d'oreiller en soie 100% naturelle et biologique”.
Meta description is long (298 characters)
Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.
236 internal links, 10 external
The homepage links to 236 pages on emilyspillow.com and 10 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Emily's Pillow - Taie d'oreiller en soie 100% naturelle et biologique”.
Canonical URL set
The canonical URL is https://emilyspillow.com/.
Structured data in place
Structured data found: FAQPage, 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://emilyspillow.com/sitemap.xml.
AI search readiness
4 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 (2,415 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://emilyspillow.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://emilyspillow.com/pages/tarifs-et-expedition, https://emilyspillow.com/pages/vos-cheveux-vous-diront-merci, https://emilyspillow.com/pages/votre-peau-vous-dira-merci, https://emilyspillow.com/pages/fidelite-parrainage and https://emilyspillow.com/products/taie-doreiller-100-pure-soie-de-murier-vert-sauge-joie have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://emilyspillow.com/collections/collection-madeleine-%F0%9F%8E%84, whose canonical is https://emilyspillow.com/collections/collection-madeleine-%f0%9f%8e%84. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://emilyspillow.com/pages/tarifs-et-expedition and https://emilyspillow.com/pages/fidelite-parrainage 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 98 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97108235&tm=shpfy_ui&Ver=2&mid=5c3bf3c6-8642-4296-9944-433862d003c2&bo=1&sid=6543c110da3611f1b2cad9aa9fa87468&vid=6543f310da3611f1a3d9693e059dc296&vids=1&msclkid=N&pi=.
25 small tap targets
25 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 788 words of copy
The homepage carries about 788 words of visible text.
6 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 “Contact” and “Shop now”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks, 1 customer or partner logo and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 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.
35 cookies set on arrival
35Opening the homepage sets 35 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.
68 other companies contacted
Loading the homepage contacts 68 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 emilyspillow.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Wisepops Popup Builder Cro · Qtrack · Judge Me Reviews · Gorgias Live Chat Helpdesk · Instafeed · Userway Website Accessibility · Depict Search Merchandising · Scalapay On Site Messaging · Loyoly · Iadvize Ai Shopping Assistant · Cartbot · Orbe Geolocation · Dialog E Commerce Ai Agent · Scalapay Widget Installer Prod · Swishlist · Free Gift · Axeptio · richpanel.com · nfcube.com · web.app · discounthuntapp.com · webyn.ai
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 | Hotjar
- Hosting
- Shopify
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 emilyspillow.com, including 20 speed issues and 2 SEO issues. 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.