Website review, no card needed
glaciersleep.com website review
Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 92 checks
This review found 41 issues worth fixing on glaciersleep.com, 14 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
80B- #48,322 of 124,051 reviewed websitesbeats 55%
- #31,935 of 69,761 online storesbeats 48%
- #30,684 of 63,450 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 189 ms |
| Jun 13, 2026 | 188 ms |
| Jun 20, 2026 | 188 ms |
| Jun 27, 2026 | 181 ms |
| Jul 4, 2026 | 182 ms |
| Jul 11, 2026 | 189 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 186 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 167 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 201 ms |
| Oct 31, 2026 | 206 ms |
| Nov 7, 2026 | 201 ms |
| Nov 14, 2026 | 193 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.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Improve image delivery
3.9 s · 1.7 MB17 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.
Reduce unused JavaScript
2.4 s · 911 KiBAbout 911 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.7 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.6 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 (neurograph.io, rebuyengine.com and Shopify and others), adding 2.2 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
750 ms · 296 KiB22 files are served with short cache lifetimes, so returning visitors download them again (296 KiB).
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
neurograph.io adds 754 ms
754 msneurograph.io costs a phone 754 ms of main-thread work and 130 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.
rebuyengine.com adds 201 ms
201 msrebuyengine.com costs a phone 201 ms of main-thread work and 445 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.
2,367 HTML elements
The page has 2,367 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 188 ms
188 msShopify costs a phone 188 ms of main-thread work and 359 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 118 ms
118 msKlaviyo costs a phone 118 ms of main-thread work and 311 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.
tidio.co adds 91 ms
91 mstidio.co costs a phone 91 ms of main-thread work and 518 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.
Duplicated JavaScript
200 ms · 28 KiB28 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
150 ms · 65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 169 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
30 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Reduce unused CSS
18 KiBAbout 18 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.7 s
30.7 sYour largest element takes 30.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man relaxing on a Glacier mattress”.
Time to Interactive: 31.2 s
31.2 sThe page becomes fully interactive after 31.2 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 278 ms
278 msScripts block taps and scrolling for 278 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 187 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 418 ms
418 msReal visitors wait 418 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 7.9 MB in 478 requests
7.9 MBYour homepage downloads 7.9 MB in 478 requests on a phone: images 3.0 MB (45), scripts 2.5 MB (134) and other files 1.3 MB (227). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
1.2 MB8 images are downloaded at several times the size a phone draws them, for example Comparison_Original_web_1200_x_1200-01.jpg at 2,000 px wide, shown at 354 px. Resized copies would save about 1.2 MB.
4 images below the first screen load straight away
4 images further down the page (666 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 268.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (1 element).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Glacier Sleep - Premium Cooling Mattress For A Deep & Restful Sleep”.
2 H1 headlines
There are 2 <h1> headlines (“” and “Cooler Nights. Better Mornings.”). One clear main headline is easier for people and search engines.
Meta description is long (243 characters)
Your meta description is 243 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.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 17 external
The homepage links to 100 pages on glaciersleep.com and 17 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://glaciersleep.com/.
Structured data in place
Structured data found: Organization 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://glaciersleep.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 (1,599 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://glaciersleep.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://glaciersleep.com/pages/mattress-comparison, https://glaciersleep.com/collections/mattresses, https://glaciersleep.com/collections/mattress-toppers, https://glaciersleep.com/collections/bases and https://glaciersleep.com/collections/bedding-1 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://glaciersleep.com/products/carbonice%E2%84%A2-topper, whose canonical is https://glaciersleep.com/products/carbonice%e2%84%a2-topper. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://glaciersleep.com/pages/mattress-comparison, https://glaciersleep.com/products/carbonice%E2%84%A2-topper, https://glaciersleep.com/products/2-modern-cooling-foam-topper, https://glaciersleep.com/products/glacier-adjustable-bed-frame, https://glaciersleep.com/products/blue-foam-cooling-pillow and https://glaciersleep.com/products/cooling-sheet-set and 2 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 31 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://cdn.shopify.com/s/files/1/0611/8912/8246/files/Group_2227.png?v=1741368245.
12 small tap targets
12 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) AbortError: The play() request was interrupted by a new load request. https://goo.gl/LdLk22”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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 759 words of copy
The homepage carries about 759 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop the sale” and “Shop Mattresses”.
33 calls to action
The homepage has 33 calls to action, for example “Shop All”, “Shop Original°” and “Shop Summit°”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks, 2 customer or partner logos, a star rating and 7 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 1 of them by other companies (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.
57 other companies contacted
Loading the homepage contacts 57 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 glaciersleep.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Ta Mappy Store Locator Maps · Yotpo Product Reviews · Userway Website Accessibility · Triplewhale · Instafeed · Gempages Builder · Comparable Products · Gsc Countdown Timer · Wyllo Formerly Nofraud · Gorgias Live Chat Helpdesk · Avada Cookie Bar · Loop Returns · Affirm · Upcharge Fees · rebuyengine.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on glaciersleep.com, including 19 speed issues and 5 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.