nutridome.pt website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Google CDN and Clarity and others), adding 1.4 MB and 747 ms of main-thread time.

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

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

Shopify costs a phone 402 ms of main-thread work and 306 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 CDN costs a phone 113 ms of main-thread work and 299 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.

conversion.io costs a phone 16 ms of main-thread work and 516 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.

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

70 KiB could be saved by minifying JavaScript.

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

1 image could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 19 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.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK MONTH COMEÇOU”.

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

The layout shifts by 0.284 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.5 MB in 254 requests on a phone: scripts 1.2 MB (90), other files 1.2 MB (101) and images 672 KiB (48). Under 2 MB keeps phones on slow connections fast.

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

19 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (32 elements).

The homepage links to 645 pages on nutridome.pt and 29 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://nutridome.pt/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://nutridome.pt/apps/iwish has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'width')”.

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.

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 1,752 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (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 13 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.