nutraj.com website review

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

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

19 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (codepen.io, Amazon Web Services and breezesdk.store and others), adding 1.2 MB and 140 ms of main-thread time.

breezesdk.store costs a phone 32 ms of main-thread work and 606 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 8 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.

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.

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

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

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

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

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

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 5.9 MB in 191 requests on a phone: images 3.7 MB (55), scripts 1.7 MB (87) and stylesheets 182 KiB (36). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example Pay_on_delivery.gif at 512 px wide, shown at 34 px. Resized copies would save about 1.9 MB.

Pay_on_delivery.gif weighs 525 KiB. On a phone connection a single image that size takes seconds.

4 images (1.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Some list items are not inside a list.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

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

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

11 links have no real href, so search engines can't follow them.

The homepage links to 451 pages on nutraj.com and 33 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://www.nutraj.com/collections/walnut-inshell, https://www.nutraj.com/collections/almond-kernels, https://www.nutraj.com/collections/pista-inshell and https://www.nutraj.com/collections/pista-kernels have no <h1> headline, so visitors and search engines get no clear main topic.

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

11 of 55 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

The homepage carries about 1,246 words of visible text.

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

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