Website review, no card needed
dreamcloudsleep.co.uk website review
Visit site (opens in a new tab)Reviewed 19 November 202652 issues · 100 checks
This review found 52 issues worth fixing on dreamcloudsleep.co.uk, 19 of them high impact, across 100 checks. The most urgent: main-thread work: 18.8 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
74C- #87,407 of 125,277 reviewed websitesbeats 26%
- #54,749 of 70,152 online storesbeats 18%
- #51,406 of 63,745 Shopify storesbeats 16%
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.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 168 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 178 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 180 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 209 ms |
| Oct 10, 2026 | 219 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 229 ms |
| Nov 7, 2026 | 229 ms |
| Nov 14, 2026 | 228 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
0.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Main-thread work: 18.8 s
A phone's processor spends 18.8 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 20
20/100Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
950 ms · 1.4 MB7 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Yotpo and others), adding 2.8 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.3 MBAbout 1.3 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 980 ms
980 msGoogle Tag Manager costs a phone 980 ms of main-thread work and 863 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.
Use efficient cache lifetimes
821 KiB49 files are served with short cache lifetimes, so returning visitors download them again (821 KiB).
Reduce unused CSS
600 ms · 182 KiBAbout 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Yotpo adds 198 ms
198 msYotpo costs a phone 198 ms of main-thread work and 552 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,514 HTML elements
The page has 2,514 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 171 ms
171 msKlaviyo costs a phone 171 ms of main-thread work and 344 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 93 ms
93 msShopify costs a phone 93 ms of main-thread work and 589 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 242 ms. During a long task the page ignores taps.
Legacy JavaScript
90 KiBPolyfills for old browsers add 90 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.2 s
40.2 sThe page becomes fully interactive after 40.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.492
0.492The layout shifts by 0.492 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 781 ms
781 msScripts block taps and scrolling for 781 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 168 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 215 ms
215 msReal visitors wait 215 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 8.3 MB in 591 requests
8.3 MBYour homepage downloads 8.3 MB in 591 requests on a phone: scripts 3.1 MB (157), images 2.8 MB (63) and other files 1.6 MB (298). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
DC_Bamboo_Bed_Frame_Bundle___Natural.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).
6 images in older formats
6 images (850 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.
1 image far larger than shown
96 KiB1 image is downloaded at several times the size a phone draws it, for example dc_bf_mob3.jpg at 1,500 px wide, shown at 390 px. Resized copies would save about 96 KiB.
About 2.3 g of CO₂ per visit
2.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 281.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
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 (h1 → h4, h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 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 short (10 characters)
Your title is only 10 characters: “DreamCloud”. Between 30 and 65 characters leaves room to say what you do and for whom.
12 H1 headlines
There are 12 <h1> headlines (“”, “” and “Save Up To 40% On Mattresses* *Savings compared t…”). One clear main headline is easier for people and search engines.
Meta description is long (232 characters)
Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
151 internal links, 2 external
The homepage links to 151 pages on dreamcloudsleep.co.uk and 2 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.dreamcloudsleep.co.uk/.
Structured data in place
Structured data found: Organization.
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.dreamcloudsleep.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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,325 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dreamcloudsleep.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.dreamcloudsleep.co.uk/products/bamboo-platform-bed, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.dreamcloudsleep.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.dreamcloudsleep.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.dreamcloudsleep.co.uk/pages/aboutus, https://www.dreamcloudsleep.co.uk/pages/support, https://www.dreamcloudsleep.co.uk/customer_authentication/redirect and https://www.dreamcloudsleep.co.uk/pages/mattresses have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.dreamcloudsleep.co.uk/pages/similar-brands-avg-price, https://www.dreamcloudsleep.co.uk/customer_authentication/redirect and https://www.dreamcloudsleep.co.uk/products/divan-bed have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.dreamcloudsleep.co.uk/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
2 checks passed
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
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=16004273&Ver=2&mid=3487fd33-0413-4812-b11a-80effe41cbd4&bo=1&sid=8bf48150e46311f1af8001e4ab5e04f0&vid=8bf48a20e46311f1b9b04f01755eb6e9&vids=1&msclkid=N&pi=918639831&lg.
11 small tap targets
11 of 30 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.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
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
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,627 words of copy
The homepage carries about 1,627 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MATTRESS” and “SHOP BUNDLES”.
35 calls to action
The homepage has 35 calls to action, for example “Call Us”, “Shop Mattress” and “Shop All Mattresses”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 90 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 6 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
13 trackers load before any consent
13Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Heap and Hotjar and 8 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.
38 cookies set on arrival
38Opening the homepage sets 38 cookies, 2 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.
75 other companies contacted
Loading the homepage contacts 75 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 dreamcloudsleep.co.uk, 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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Seowill Redirects · Elevar Conversion Tracking · Impact Com · Loxa · Bespoke Shipping · Gdpr Backpack · Checkout Rules · nice-team.net · b-cdn.net · usecorner.io · digitaloceanspaces.com · zigpoll.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on dreamcloudsleep.co.uk, including 21 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.