balooliving.com website review

Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (heatmap.com, alia-prod.com and Clarity and others), adding 1.4 MB and 850 ms of main-thread time.

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

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

About 667 KiB of JavaScript is downloaded but never used on this page.

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

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

Klaviyo costs a phone 113 ms of main-thread work and 312 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.

6 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 77 KiB JavaScript that modern phones do not need.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A smiling woman peeks out from underneath a sheet, sitting …”.

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 310 requests on a phone: scripts 1.9 MB (123), other files 869 KiB (159) and images 225 KiB (9). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (147 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Weighted Blankets by Baloo Living I Natural materials for deep sleep”.

There are 3 <h1> headlines (“Naturally cool. Deeply calming.”, “Naturally cool. Deeply calming.” and “Curl up & stay awhile”). One clear main headline is easier for people and search engines.

The homepage links to 124 pages on balooliving.com and 10 external pages.

/pages/sleep-quiz has no <h1> headline, so visitors and search engines get no clear main topic.

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

4 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 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://facebook.com/balooliving.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

balooliving.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

balooliving.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

balooliving.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your longest form asks for 15 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 898 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 52 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 72 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.