Website review, no card needed

sloom.co.za logo

sloom.co.za website review

Visit site (opens in a new tab)Reviewed 10 November 202640 issues · 83 checks

This review found 40 issues worth fixing on sloom.co.za, 14 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.7 sMay 23Nov 72.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.2 s
Nov 7, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
255 ms150 msMay 23Nov 7243 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026162 ms
May 30, 2026165 ms
Jun 6, 2026171 ms
Jun 13, 2026173 ms
Jun 20, 2026180 ms
Jun 27, 2026182 ms
Jul 4, 2026185 ms
Jul 11, 2026195 ms
Jul 18, 2026198 ms
Jul 25, 2026200 ms
Aug 1, 2026200 ms
Aug 8, 2026192 ms
Aug 15, 2026190 ms
Aug 22, 2026194 ms
Aug 29, 2026201 ms
Sep 5, 2026206 ms
Sep 12, 2026212 ms
Sep 19, 2026221 ms
Sep 26, 2026224 ms
Oct 3, 2026228 ms
Oct 10, 2026229 ms
Oct 17, 2026228 ms
Oct 24, 2026221 ms
Oct 31, 2026219 ms
Nov 7, 2026243 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

Full-page screenshot of sloom.co.za (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sloom.co.za at 0.5 s0.5 s
  2. sloom.co.za at 1.1 s1.1 s
  3. sloom.co.za at 1.6 s1.6 s
  4. sloom.co.za at 2.2 s2.2 s
  5. sloom.co.za at 2.7 s2.7 s
  6. sloom.co.za at 3.3 s3.3 s
  7. sloom.co.za at 3.8 s3.8 s
  8. sloom.co.za at 4.3 s4.3 s

Speed

10 to fix49
  • Reduce unused JavaScript

    3.1 s · 596 KiB

    About 596 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Improve image delivery

    1.1 s · 556 KiB

    10 images could be 556 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vercel.app and Clarity and others), adding 1.8 MB and 1.2 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 112 KiB

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

  • Render-blocking requests

    800 ms

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

  • Google Tag Manager adds 413 ms

    413 ms

    Google Tag Manager costs a phone 413 ms of main-thread work and 538 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.

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • vercel.app adds 271 ms

    271 ms

    vercel.app costs a phone 271 ms of main-thread work and 538 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 41 ms

    41 ms

    Shopify costs a phone 41 ms of main-thread work and 317 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

    150 ms · 47 KiB

    47 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    120 ms · 44 KiB

    About 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 24.5 s

    24.5 s

    Your largest element takes 24.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman smiling on a Sloom mattress, up to 35% off selected p…”.

  • Time to Interactive: 24.8 s

    24.8 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 203 ms

    203 ms

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

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

    +41%

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

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

    +20%

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 847 ms

    847 ms

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

  • Total Blocking Time: 365 ms

    365 ms

    Scripts block taps and scrolling for 365 ms in total while the page loads. Good is under 200 ms.

  • 22 images without width and height

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

2 checks passed
  • Real-user CLS: 0.09

    0.09

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix60
  • Page weight: 4.6 MB in 341 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 341 requests on a phone: scripts 1.7 MB (89), images 1.6 MB (46) and other files 938 KiB (155). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    157 KiB

    2 images are downloaded at several times the size a phone draws them, for example Bedframe_Shop1_d5f4e834-925b-48c1-8db7-0d2a75a3d76a.webp at 600 px wide, shown at 60 px. Resized copies would save about 157 KiB.

  • 1 image in older formats

    1 image (119 KiB) is 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 1.3 g of CO₂ per visit

    1.29 g

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

1 checks passed
  • Images load when needed

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

Accessibility

8 to fixGoogle 8189
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 19 tap targets too small

    19 tap targets are too small or too close together to hit reliably with a finger.

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

  • ARIA commands must have an accessible name (4 elements)

    ARIA commands must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • 40 images without alt text

    40 images have no alt text, which hurts accessibility and image search.

  • 1 form field without a label

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “WELCOME TO YOUR”). One clear main headline is easier for people and search engines.

  • Meta description is long (172 characters)

    Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 84 internal links, 14 external

    The homepage links to 84 pages on sloom.co.za and 14 external pages.

6 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Sloom | South Africa's First & Only Modular Mattress”.

  • Canonical URL set

    The canonical URL is https://sloom.co.za/.

  • 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://sloom.co.za/sitemap.xml.

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: 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,490 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://sloom.co.za/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://sloom.co.za/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://sloom.co.za/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 5 distorted images

    5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    19 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 1,220 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE MATTRESS”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP THE MATTRESS”, “Shop bundles” and “SHOP OUR MATTRESS”.

  • 5 short forms

    5 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: 107 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • 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
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 19 cookies set on arrival

    19

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

  • 41 other companies contacted

    Loading the homepage contacts 41 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 sloom.co.za, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Form Builder · Judge Me Reviews · Smart Seo · Klaviyo Email Marketing Sms · Glo Color Swatch · nice-team.net · cloudfront.net

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 | 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 40 issues on sloom.co.za, including 23 speed issues and 2 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

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