weightworld.es website review

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

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

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

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

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

alia-prod.com costs a phone 316 ms of main-thread work and 256 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.

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

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

About 218 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 22 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

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.

3 KiB could be saved by minifying CSS.

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

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

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

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

Your homepage downloads 4.2 MB in 497 requests on a phone: other files 1.5 MB (258), images 1.3 MB (61) and scripts 1.1 MB (128). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example sunglow-120-tabs-es-front.webp at 390 px wide, shown at 95 px. Resized copies would save about 26 KiB.

3 images (158 KiB) 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.

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

15 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: 3 elements on the page fail this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor 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. (7 elements).

There are 3 <h1> headlines (“”, “Opiniones de los clientes” and “Bienvenido\a a Weightworld”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, ItemList, Organization and WebSite) but with 1 problem, for example “ld+json block 6 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

The homepage links to 307 pages on weightworld.es and 17 external pages.

https://www.weightworld.es/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weightworld.es/collections/all, https://www.weightworld.es/products/aceite-de-pescado-omega-3-2000-mg, https://www.weightworld.es/products/glicinato-de-magnesio-vitamina-b6, https://www.weightworld.es/products/citrato-de-magnesio-1480mg, https://www.weightworld.es/products/colageno-marino-con-acido-hialuronico and https://www.weightworld.es/products/magnesio-complex-1700-mg and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “src.indexOf is not a function https://www.weightworld.es/:233:26”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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 873 words of visible text.

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.

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