Programmable

Website review, no card needed

mycloudtopper.com logo

mycloudtopper.com website review

Visit site (opens in a new tab)Reviewed 11 November 202617 issues · 76 checks

This review found 17 issues worth fixing on mycloudtopper.com, 3 of them high impact, across 76 checks. The most urgent: 6 text elements with low contrast. 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

93A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.0 s801 msMay 23Nov 7948 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026829 ms
May 30, 2026861 ms
Jun 6, 2026911 ms
Jun 13, 2026913 ms
Jun 20, 2026924 ms
Jun 27, 2026946 ms
Jul 4, 2026950 ms
Jul 11, 2026973 ms
Jul 18, 2026994 ms
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 2026996 ms
Aug 29, 2026972 ms
Sep 5, 2026941 ms
Sep 12, 2026940 ms
Sep 19, 2026947 ms
Sep 26, 2026948 ms
Oct 3, 2026955 ms
Oct 10, 2026941 ms
Oct 17, 2026942 ms
Oct 24, 2026945 ms
Oct 31, 2026947 ms
Nov 7, 2026948 ms
Real-visitor tap response (INP)75th percentile, phones
236 ms176 msMay 23Nov 7213 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026212 ms
May 30, 2026215 ms
Jun 6, 2026217 ms
Jun 13, 2026211 ms
Jun 20, 2026209 ms
Jun 27, 2026208 ms
Jul 4, 2026205 ms
Jul 11, 2026219 ms
Jul 18, 2026229 ms
Jul 25, 2026221 ms
Aug 1, 2026215 ms
Aug 8, 2026204 ms
Aug 15, 2026195 ms
Aug 22, 2026192 ms
Aug 29, 2026184 ms
Sep 5, 2026184 ms
Sep 12, 2026183 ms
Sep 19, 2026184 ms
Sep 26, 2026186 ms
Oct 3, 2026192 ms
Oct 10, 2026196 ms
Oct 17, 2026204 ms
Oct 24, 2026210 ms
Oct 31, 2026211 ms
Nov 7, 2026213 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.mycloudtopper.com (opens in a new tab)
Full-page screenshot of mycloudtopper.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mycloudtopper.com at 0.4 s0.4 s
  2. mycloudtopper.com at 0.8 s0.8 s
  3. mycloudtopper.com at 1.1 s1.1 s
  4. mycloudtopper.com at 1.5 s1.5 s
  5. mycloudtopper.com at 1.9 s1.9 s
  6. mycloudtopper.com at 2.3 s2.3 s
  7. mycloudtopper.com at 2.6 s2.6 s
  8. mycloudtopper.com at 3.0 s3.0 s

Speed

2 to fix100

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • 1,640 HTML elements

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

  • Reduce unused CSS

    109 KiB

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

  • Improve image delivery

    17 KiB

    3 images could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    15 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cloudfront.net and Klaviyo and others), adding 71 KiB and 3 ms of main-thread time.

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

3 checks passed

  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

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

  • Server response: 40 ms

    40 ms

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

Core Web Vitals

1 to fix100

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

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

    +12%

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

12 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 724 ms

    724 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.19 g

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

4 checks passed

  • Page weight: 677 KiB in 61 requests

    677 KiB

    Your homepage downloads 677 KiB in 61 requests on a phone: scripts 227 KiB (25), images 158 KiB (23) and stylesheets 134 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9697

  • 6 text elements with low contrast

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

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

2 checks passed

  • Every image has alt text

    All 90 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100

  • 152 internal links, 4 external

    The homepage links to 152 pages on mycloudtopper.com and 4 external pages.

8 checks passed

  • Meta description: 158 characters

    Your meta description is 158 characters: “Upgrade sleep with a premium mattress topper. Discover luxury, thick, and orthopaedic mattress topper options for comfo…”.

  • One H1 headline

    Your main headline reads: “Best Selling Products”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Premium Mattress Topper for Better Sleep | CloudTopper”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ItemList, Organization, WebPage 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.mycloudtopper.com/sitemap.xml.

AI search readiness

1 to fix88

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix71

  • 3 pages point its canonical at the homepage

    https://www.mycloudtopper.com/products/silk-pillow-cases, https://www.mycloudtopper.com/products/cloudtopper%E2%84%A2-weighted-blanket and https://www.mycloudtopper.com/products/luxury-blanket declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 6 pages share 2 titles

    /, https://www.mycloudtopper.com/products/silk-pillow-cases, https://www.mycloudtopper.com/products/cloudtopper%E2%84%A2-weighted-blanket and https://www.mycloudtopper.com/products/luxury-blanket all use the title “Premium Mattress Topper for Better Sleep | CloudTopper”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.mycloudtopper.com/pages/best-sellers and https://www.mycloudtopper.com/pages/build-your-better-bed have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.mycloudtopper.com/products/mattress-topper and https://www.mycloudtopper.com/collections/best-sellers/products/mattress-topper use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.mycloudtopper.com/products/mattress-topper, https://www.mycloudtopper.com/products/fitted-sheet, https://www.mycloudtopper.com/products/cloudtopper%E2%84%A2-pillow-set-2-pack, https://www.mycloudtopper.com/pages/cloudtopper-reviews and https://www.mycloudtopper.com/collections/best-sellers/products/mattress-topper 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 30 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.

  • 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 to fixGoogle 9693

  • 3 small tap targets

    3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

  • About 324 words of copy

    The homepage carries about 324 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed

  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop all products”, “Track Order” and “Contact”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 438 testimonial or review blocks, 41 customer or partner logos, a star rating and “75k Happy Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity 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

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 mycloudtopper.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

Intelligems A B Testing · Parkour Tiktok Pixel · Abconvert · Zoorix Sticky Atc · Klaviyo Email Marketing Sms · Gempages Builder · Hive · Simprosys Google Shopping Feed · Reamaze Live Chat Helpdesk · Triplewhale · Awin Affiliate Marketing · Rebuy Personalization Engine · Hive Logistics Services · Zipify Oneclickupsell · loox.io · trustpilot.com · rebuyengine.com · richpanel.com · amazonaws.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on mycloudtopper.com, including 3 speed 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

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