ecobioboutique.pt website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, loox.io and Cookiebot and others), adding 1.0 MB and 840 ms of main-thread time.

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

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

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

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

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

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

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

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

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 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Scripts block taps and scrolling for 423 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' largest content (lcp) went from 2.2 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 199 requests on a phone: scripts 1.5 MB (52), other files 801 KiB (95) and images 632 KiB (36). Under 2 MB keeps phones on slow connections fast.

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

6 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Your title is 75 characters, so Google will cut it off around 60: “Eco Bio Boutique | Uma nova geração de beleza – Eco Bio Boutique - Portugal”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 296 pages on ecobioboutique.pt and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

https://ecobioboutique.pt/collections/rosto, https://ecobioboutique.pt/collections/rosto/limpeza, https://ecobioboutique.pt/collections/rosto/t%C3%B3nicos, https://ecobioboutique.pt/collections/rosto/esfoliantes, https://ecobioboutique.pt/collections/rosto/s%C3%A9runs and https://ecobioboutique.pt/collections/rosto/contornodeolhos and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://ecobioboutique.pt/collections/rosto/t%C3%B3nicos, whose canonical is https://ecobioboutique.pt/collections/rosto/t%c3%b3nicos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ecobioboutique.pt/collections/cuidados-intimos took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=52004098&Ver=2&mid=3940e109-6254-42c1-917c-4170f28058bc&bo=1&sid=bf7cd870dda611f181e917ab819f9e5f&vid=bf7cfb20dda611f1823b2f9c84bd3c65&vids=1&msclkid=N&pi=918639831&lg.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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

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