nellaspec.com website review

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

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

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

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

8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Osano CMP and others), adding 2.5 MB and 1.2 s of main-thread time.

14 images could be 553 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

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

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

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

Shopify costs a phone 78 ms of main-thread work and 1.4 MB 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.

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

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

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

9 KiB could be saved by minifying CSS.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 84 ms to 112 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 1.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 5.7 MB in 319 requests on a phone: images 1.6 MB (32), scripts 1.5 MB (109) and media 1.0 MB (1). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (384 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 1.62 g of CO₂e: 194.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 58 pages on nellaspec.com and 16 external pages.

https://www.nellaspec.com/products/the-nella-comfort-kit-classic, https://www.nellaspec.com/products/the-nella-comfort-kit-first and https://www.nellaspec.com/products/the-nella-comfort-kit-menopause all use the title “Modern & Comfortable Speculum | Pap Smear Tool | Stirrup Socks – Nell…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.nellaspec.com/collections/all, https://www.nellaspec.com/policies/shipping-policy, https://www.nellaspec.com/collections/all-kits, https://www.nellaspec.com/pages/how-it-works, https://www.nellaspec.com/pages/medical-advisory and https://www.nellaspec.com/pages/clinical-backed and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nellaspec.com/products/the-nella-comfort-kit-classic, https://www.nellaspec.com/products/the-nella-comfort-kit-first and https://www.nellaspec.com/products/the-nella-comfort-kit-menopause use the same meta description. A description written for each page earns more clicks.

https://www.nellaspec.com/pages/how-it-works, https://www.nellaspec.com/pages/why-nella, https://www.nellaspec.com/pages/medical-advisory, https://www.nellaspec.com/pages/clinical-backed, https://www.nellaspec.com/pages/about-us and https://www.nellaspec.com/pages/payment-options and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 28 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”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Reddit Pixel (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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