naturalform.com website review

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

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

8 third-party services load with your homepage (Shopify, Facebook and Google Tag Manager and others), adding 1.2 MB and 902 ms of main-thread time.

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

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

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

Shopify costs a phone 274 ms of main-thread work and 393 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.

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

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

1 image could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

6 KiB could be saved by minifying CSS.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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.

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider image 1621243260e1af0c20-0”.

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

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

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 263 requests on a phone: scripts 1.3 MB (93), other files 779 KiB (105) and images 210 KiB (23). Under 2 MB keeps phones on slow connections fast.

1b58300a4c5406e4026e6ecd41bb36703788976ebf7db6eff6149ceabb5f 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).

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

31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 element hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 12 characters: “Natural Form”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 127 pages on naturalform.com and 5 external pages.

https://naturalform.com/collections/all, https://naturalform.com/pages/mattress-quiz and https://naturalform.com/collections/bed-frames have no meta description, so Google writes the search snippet from whatever text it finds.

https://naturalform.com/pages/compare-mattresses, https://naturalform.com/pages/mattress-quiz, https://naturalform.com/pages/about-us and https://naturalform.com/pages/sustainability have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,305 words of visible text.

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

Opening the homepage sets 18 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.