nutridome.bg website review

Shopify costs a phone 1.2 s of main-thread work and 297 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

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

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

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

Facebook costs a phone 321 ms of main-thread work and 309 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.

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

35 KiB could be saved by minifying JavaScript.

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

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 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK MONTH СТАРТИРА”.

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

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

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

Real visitors wait 211 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 157 ms to 220 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Visually, the page fills in at 4.9 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.

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

Your homepage downloads 3.6 MB in 253 requests on a phone: scripts 1.9 MB (79), other files 808 KiB (108) and images 628 KiB (54). Under 2 MB keeps phones on slow connections fast.

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

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

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. (33 elements).

The homepage links to 651 pages on nutridome.bg 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.

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

https://nutridome.bg/collections/grizha-za-liceto, https://nutridome.bg/apps/iwish, https://nutridome.bg/collections/lice, https://nutridome.bg/collections/dnevni-kremove, https://nutridome.bg/collections/noshchni-kremove and https://nutridome.bg/collections/kremove-za-lice-protiv-brchki and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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.

The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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