Website review, no card needed
sleepeezee.com website review
Visit site (opens in a new tab)Reviewed 25 October 202651 issues · 92 checks
This review found 51 issues worth fixing on sleepeezee.com, 23 of them high impact, across 92 checks. The most urgent: improve image delivery. 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
67D- #110,069 of 122,751 reviewed websitesbeats 9%
- #65,509 of 69,277 online storesbeats 4%
- #2,497 of 2,858 WooCommerce storesbeats 10%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 130 ms |
| May 9, 2026 | 136 ms |
| May 16, 2026 | 137 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 159 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 166 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 162 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
Improve image delivery
11.4 s · 6.1 MB24 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.4 s faster on a phone.
Render-blocking requests
4.8 s56 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Use efficient cache lifetimes
2.1 s · 1.1 MB171 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Hotjar and others), adding 17.5 MB and 1.8 s of main-thread time.
Vimeo adds 147 ms
147 msVimeo costs a phone 147 ms of main-thread work and 16.0 MB 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.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 679 ms
679 msGoogle Tag Manager costs a phone 679 ms of main-thread work and 864 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.
Reduce unused CSS
450 ms · 214 KiBAbout 214 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.
FontAwesome CDN adds 370 ms
370 msFontAwesome CDN costs a phone 370 ms of main-thread work and 102 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 289 ms. During a long task the page ignores taps.
2,165 HTML elements
The page has 2,165 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 6 KiB6 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 66 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 204 ms
204 msYour server sent the HTML in 204 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 LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 20.6 s
20.6 sYour largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With over a century of experience, we’re committed to suppo…”.
Speed Index: 18.2 s
18.2 sVisually, the page fills in at 18.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 38.8 s
38.8 sThe page becomes fully interactive after 38.8 s. Good is under 3.8 s.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 130 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 70% slower for real visitors
+70%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 122 ms
122 msReal visitors wait 122 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 26.5 MB in 277 requests
26.5 MBYour homepage downloads 26.5 MB in 277 requests on a phone: other files 15.6 MB (60), images 7.5 MB (30) and scripts 2.9 MB (114). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.
16 images far larger than shown
2.5 MB16 images are downloaded at several times the size a phone draws them, for example logo-white.png at 3,587 px wide, shown at 180 px. Resized copies would save about 2.5 MB.
20 images in older formats
20 images (7.3 MB) are 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 (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.5 g of CO₂ per visit
7.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.52 g of CO₂e: 902.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (6 elements)
Elements must only use permitted ARIA attributes: 6 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.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (14 elements)
Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Home | Sleepeezee”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
160 internal links, 9 external
The homepage links to 160 pages on sleepeezee.com and 9 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Perfecting sleep for over 100 years”.
Canonical URL set
The canonical URL is https://sleepeezee.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://sleepeezee.com/sitemap_index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://sleepeezee.com/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.
2 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 (684 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://sleepeezee.com/care-guides is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://sleepeezee.com/contact-us, https://sleepeezee.com/mattresses, https://sleepeezee.com/beds, https://sleepeezee.com/find-a-retailer, https://sleepeezee.com/hospitality and https://sleepeezee.com/the-comfort-guide and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://sleepeezee.com/blog, https://sleepeezee.com/find-a-retailer and https://sleepeezee.com/mattress-comparison have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages slow to respond
https://sleepeezee.com/contact-us, https://sleepeezee.com/blog, https://sleepeezee.com/mattresses, https://sleepeezee.com/beds, https://sleepeezee.com/find-a-retailer and https://sleepeezee.com/hospitality and 9 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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.
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.
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=11044172&tm=gtm002&Ver=2&mid=a10f1063-a4dc-45b1-a1e0-a2ec676cbae2&bo=1&sid=afab4410d06311f1b85f37321f1ba880&vid=afab7510d06311f1aaac6745be3e85dc&vids=1&msclkid=N>m_t.
17 small tap targets
17 of 46 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.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “elementorFrontendConfig is not defined”.
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 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 594 words of copy
The homepage carries about 594 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact us”, “Register your guarantee” and “Contact Us”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 2 of them by other companies (measured from a US location before any click).
37 other companies contacted
Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 sleepeezee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on sleepeezee.com, including 25 speed issues, 3 SEO 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.