Programmable

Website review, no card needed

mysleepwell.com logo

mysleepwell.com website review

Visit site (opens in a new tab)Reviewed 1 November 202629 issues · 78 checks

This review found 29 issues worth fixing on mysleepwell.com, 5 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.5 s2.7 sAug 15Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20262.8 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
340 ms236 msAug 15Oct 24326 ms
Show as table
DateReal-visitor tap response (INP)
Aug 15, 2026248 ms
Aug 22, 2026263 ms
Aug 29, 2026270 ms
Sep 5, 2026278 ms
Sep 12, 2026294 ms
Sep 19, 2026301 ms
Sep 26, 2026309 ms
Oct 3, 2026326 ms
Oct 10, 2026328 ms
Oct 17, 2026327 ms
Oct 24, 2026326 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

www.mysleepwell.com (opens in a new tab)
Full-page screenshot of mysleepwell.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mysleepwell.com at 1.7 s1.7 s
  2. mysleepwell.com at 3.3 s3.3 s
  3. mysleepwell.com at 5.0 s5.0 s
  4. mysleepwell.com at 6.7 s6.7 s
  5. mysleepwell.com at 8.3 s8.3 s
  6. mysleepwell.com at 10.0 s10.0 s
  7. mysleepwell.com at 11.7 s11.7 s
  8. mysleepwell.com at 13.3 s13.3 s

Speed

3 to fix74

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    400 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • 2,981 HTML elements

    The page has 2,981 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    150 ms · 12 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).

  • Improve image delivery

    100 ms · 37 KiB

    3 images could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

  • 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, Google Fonts and JSDelivr CDN and others), adding 46 KiB and 0 ms of main-thread time.

2 checks passed

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 89 ms of it running JavaScript. That is comfortably low.

  • Server response: 20 ms

    20 ms

    Your server sent the HTML in 20 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33

  • 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.

  • Speed Index: 16.1 s

    16.1 s

    Visually, the page fills in at 16.1 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (10.0 s).

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 278 ms

    278 ms

    Real visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 28% slower for real visitors

    +28%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 248 ms to 326 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 4.3 s

    4.3 s

    The page becomes fully interactive after 4.3 s. Good is under 3.8 s.

  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 17% slower for real visitors

    +17%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix69

  • Page weight: 2.6 MB in 113 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 113 requests on a phone: media 1.4 MB (1), images 642 KiB (38) and HTML 204 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Nexa_new.webp 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).

  • 4 images in older formats

    4 images (568 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9596

  • 21 text elements with low contrast

    21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 498 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086

  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Buy Sleepwell Mattress Online | Best Mattress Brand in India – mysleepwell”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://mysleepwell.com/sitemap.xml, so Google discovers your pages only by following links.

  • 128 internal links, 10 external

    The homepage links to 128 pages on mysleepwell.com and 10 external pages.

5 checks passed

  • Meta description: 143 characters

    Your meta description is 143 characters: “Buy premium mattresses online from Sleepwell – India’s most trusted mattress brand. Explore bed and latex mattresses, p…”.

  • One H1 headline

    Your main headline reads: “Sleepwell Mattresses: Engineered for the Way India Sleeps”.

  • Canonical URL set

    The canonical URL is https://www.mysleepwell.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,434 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.mysleepwell.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68

  • 1 page without a title

    https://www.mysleepwell.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.mysleepwell.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.mysleepwell.com/pages/find-store, https://www.mysleepwell.com/customer_authentication/redirect, https://www.mysleepwell.com/pages/compare-mattress, https://www.mysleepwell.com/pages/furniture-cushioning, https://www.mysleepwell.com/pages/sofa-refurbishment and https://www.mysleepwell.com/pages/sleep-advice have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.mysleepwell.com/pages/find-store, https://www.mysleepwell.com/customer_authentication/redirect, https://www.mysleepwell.com/collections/mattress, https://www.mysleepwell.com/pages/compare-mattress, https://www.mysleepwell.com/pages/mattress-selector and https://www.mysleepwell.com/pages/build-my-mattress and 7 others 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 67 found) and read each the way a search engine does.

3 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.

Best practices

1 to fixGoogle 9693

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

    27 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94

  • 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.

  • 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.

  • 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 1,784 words of copy

    The homepage carries about 1,784 words of visible text.

7 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “Contact options”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Bulk Order”, “View/Track Order” and “Return Request”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 452 testimonial or review blocks and 3 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • 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.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mysleepwell.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mysleepwell.com, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25