natulim.com website review

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

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

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

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

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

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

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

Google Tag Manager costs a phone 379 ms of main-thread work and 773 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 costs a phone 298 ms of main-thread work and 1.1 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.

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

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

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

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

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

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

About 48 KiB of CSS is downloaded but never applied on this page.

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

2 KiB could be saved by minifying JavaScript.

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 31.0 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

Your homepage downloads 6.5 MB in 625 requests on a phone: scripts 3.0 MB (250), other files 1.4 MB (230) and images 1.1 MB (67). Under 2 MB keeps phones on slow connections fast.

hero-home-limpia-wc-mobile.webp weighs 738 KiB. On a phone connection a single image that size takes seconds.

15 images (2.1 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.

1 image is downloaded at several times the size a phone draws it, for example Categoria_Recargas.webp at 300 px wide, shown at 80 px. Resized copies would save about 40 KiB.

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

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 130 pages on natulim.com and 6 external pages.

https://natulim.com/pages/suscribete is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://natulim.com/collections/green-friday and https://natulim.com/collections/crea-tu-plan all use the title “Crea tu plan – Natulim”. Search engines can't tell which page to show for a search, so each competes with the others.

https://natulim.com/collections/green-friday and https://natulim.com/collections/crea-tu-plan have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://natulim.com/collections/green-friday, whose canonical is https://natulim.com/collections/crea-tu-plan. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://natulim.com/products/lavavajillas, https://natulim.com/products/tiras-de-detergente-para-lavadora-ecologicas-fragancia-natural, https://natulim.com/products/perlas-perfumadas-natulim, https://natulim.com/products/friega-suelos-en-eco-tiras, https://natulim.com/products/pack-ahorro-detergente-360-lavados and https://natulim.com/products/oxi-white and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

14 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 576 words of visible text.

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

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