nutrabay.com website review

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

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

47 images could be 3.0 MB 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.

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

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

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

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

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

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

8 third-party services load with your homepage (Facebook, moengage.com and Google Tag Manager and others), adding 870 KiB and 442 ms of main-thread time.

About 47 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 35 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.

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

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 “hero_banner”.

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

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

Real visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

21 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-10, real Chrome visitors' tap response (inp) went from 263 ms to 286 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.9 MB in 200 requests on a phone: images 4.3 MB (97), scripts 1.4 MB (78) and fonts 103 KiB (2). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example Mobile-Banner_RageX-1791275319.webp at 2,000 px wide, shown at 354 px. Resized copies would save about 635 KiB.

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

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

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

The homepage links to 156 pages on nutrabay.com and 11 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://nutrabay.com/nutrabay, whose canonical is https://nutrabay.com/brand/nutrabay. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nutrabay.com/sale/nutrabay-sale has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://zuqjug.nutrabay.com/g/uids?pld=PcBNjy2sNs03AOUlyx_WZ21aVPHDpbUKPqIzGoh4bNrelThQDTOSvovxGjXuGdWzxm1PVMp3BLwxN46kmdlT3aTKwxIE3DmZQMgW-mSipPbC3HiTP0uaSzi9NzdrGThE6AJ_gINdJBmEwQIUzxYIJDg55cmWYQsJW.

2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "auto".”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The page uses urgency cues (a countdown or limited-time wording).

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