fairzerowaste.com website review

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

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

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

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

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

Shopify costs a phone 441 ms of main-thread work and 984 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 501 KiB of JavaScript is downloaded but never used on this page.

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

Google CDN costs a phone 168 ms of main-thread work and 329 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 1,941 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

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

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

15 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 312 ms to 312 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 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 415 requests on a phone: scripts 1.4 MB (134), images 1.3 MB (31) and other files 1.2 MB (198). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example fervone-cat-tumbler.png at 800 px wide, shown at 257 px. Resized copies would save about 14 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Your title is 68 characters, so Google will cut it off around 60: “Fair Zero Waste | Tienda Online de Productos Ecoamigables en Ecuador”.

Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 52 pages on fairzerowaste.com and 5 external pages.

https://www.fairzerowaste.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.fairzerowaste.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.fairzerowaste.com/customer_authentication/redirect, https://www.fairzerowaste.com/collections/botellas, https://www.fairzerowaste.com/collections/fair-zero-waste-sale, https://www.fairzerowaste.com/pages/preguntas-frecuentes-1, https://www.fairzerowaste.com/collections/all and https://www.fairzerowaste.com/products/fair-botella-tumbler-termica-bildin-1200ml and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.fairzerowaste.com/products/tumbler-calef-900ml and https://www.fairzerowaste.com/products/tumbler-calef-750ml use the same meta description. A description written for each page earns more clicks.

https://www.fairzerowaste.com/customer_authentication/redirect and https://www.fairzerowaste.com/pages/preguntas-frecuentes-1 have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 24 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: the server responded with a status of 404 ()”.

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.

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

Social proof on the homepage: 124 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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 14 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.