Website review, no card needed
nectarsleep.co.uk website review
Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 90 checks
This review found 40 issues worth fixing on nectarsleep.co.uk, 11 of them high impact, across 90 checks. The most urgent: page weight: 6.9 MB in 360 requests. 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
84B- #22,145 of 124,300 reviewed websitesbeats 77%
- #14,252 of 69,848 online storesbeats 74%
- #13,821 of 63,521 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 328 ms |
| May 23, 2026 | 303 ms |
| May 30, 2026 | 287 ms |
| Jun 6, 2026 | 269 ms |
| Jun 13, 2026 | 277 ms |
| Jun 20, 2026 | 279 ms |
| Jun 27, 2026 | 290 ms |
| Jul 4, 2026 | 308 ms |
| Jul 11, 2026 | 318 ms |
| Jul 18, 2026 | 312 ms |
| Jul 25, 2026 | 286 ms |
| Aug 1, 2026 | 259 ms |
| Aug 8, 2026 | 234 ms |
| Aug 15, 2026 | 230 ms |
| Aug 22, 2026 | 234 ms |
| Aug 29, 2026 | 233 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 227 ms |
| Oct 10, 2026 | 232 ms |
| Oct 17, 2026 | 234 ms |
| Oct 24, 2026 | 236 ms |
| Oct 31, 2026 | 239 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.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
3.0 MB10 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
300 ms · 831 KiBAbout 831 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms17 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Yotpo and Klaviyo and others), adding 1.4 MB and 752 ms of main-thread time.
Reduce unused CSS
450 ms · 132 KiBAbout 132 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.
Use efficient cache lifetimes
50 ms · 408 KiB27 files are served with short cache lifetimes, so returning visitors download them again (408 KiB).
Google Tag Manager adds 267 ms
267 msGoogle Tag Manager costs a phone 267 ms of main-thread work and 347 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 301 ms. During a long task the page ignores taps.
2,347 HTML elements
The page has 2,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 104 ms
104 msKlaviyo costs a phone 104 ms of main-thread work and 333 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.
Minify JavaScript
53 KiB53 KiB could be saved by minifying JavaScript.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.8 s
23.8 sThe page becomes fully interactive after 23.8 s. Good is under 3.8 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 383 ms
383 msScripts block taps and scrolling for 383 ms in total while the page loads. Good is under 200 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
10 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 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: 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: 208 ms
208 msReal visitors wait 208 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 328 ms to 239 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 360 requests
6.9 MBYour homepage downloads 6.9 MB in 360 requests on a phone: images 3.6 MB (38), scripts 1.9 MB (134) and other files 829 KiB (129). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
new_awards_home_26.webp weighs 1,004 KiB. On a phone connection a single image that size takes seconds.
8 images in older formats
8 images (1.6 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 far larger than shown
101 KiB2 images are downloaded at several times the size a phone draws them, for example GHI_APPROVED_2026_1_1000x.png at 1,000 px wide, shown at 165 px. Resized copies would save about 101 KiB.
4 images below the first screen load straight away
4 images further down the page (192 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.94 g of CO₂e: 233.2 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”.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
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 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“”, “Hear From Happy Nectar Sleepers” and “The World’s Most Awarded Mattress!”). One clear main headline is easier for people and search engines.
Meta description is long (228 characters)
Your meta description is 228 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
213 internal links, 15 external
The homepage links to 213 pages on nectarsleep.co.uk and 15 external pages.
6 checks passed
Title: 40 characters
Your title is a healthy 40 characters: “Most Comfortable Mattress | Nectar Sleep”.
Canonical URL set
The canonical URL is https://www.nectarsleep.co.uk/.
Structured data in place
Structured data found: Organization 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.nectarsleep.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 (2,783 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.nectarsleep.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.nectarsleep.co.uk/pages/track-my-order and https://www.nectarsleep.co.uk/pages/mattresses have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.nectarsleep.co.uk/pages/similar-brands-avg-price, https://www.nectarsleep.co.uk/pages/track-my-order, https://www.nectarsleep.co.uk/products/kids-mattress and https://www.nectarsleep.co.uk/products/starter-bundle-king-size 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 63 found) and read each the way a search engine does.
5 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.
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
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=16001745&tm=gtm002&Ver=2&mid=151395d9-28dd-4362-8738-8fba86678e2a&bo=1&sid=94766150d8ef11f1a6ec0f4759ea54ef&vid=9476ab10d8ef11f193f191539249c7b3&vids=1&msclkid=N&pi=91.
9 small tap targets
9 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,338 words of copy
The homepage carries about 1,338 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Mattress” and “Shop Bamboo Bundle”.
34 calls to action
The homepage has 34 calls to action, for example “Shop Mattresses”, “Shop Bundles” and “Call 0203 807 1096”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 92 testimonial or review blocks and 2 trust badges.
Direct contact links
Visitors can reach you directly: 4 phone links and 3 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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
49 other companies contacted
Loading the homepage contacts 49 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 nectarsleep.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Yotpo Product Reviews · Lucky Orange · Elevar Conversion Tracking · Loxa · Bespoke Shipping · nice-team.net · cloudfront.net · dynamic-yield.com · plerdy.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
- Hosting
- Shopify
Hiring
- Hiring
- 4 open roles
- Teams
- Food Service (2), Maintenance (1), Warehouse (1)
- Job board
- bamboohr
- Careers page
- nectar.bamboohr.com/careers (opens in a new tab)
Company
- Headquarters
- Milton Keynes
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on nectarsleep.co.uk, including 17 speed issues, 3 SEO issues and 2 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.