npnutra.com website review

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

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

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

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

6 third-party services load with your homepage (YouTube, Google Tag Manager and Crazy Egg and others), adding 1.6 MB and 1.1 s of main-thread time.

YouTube costs a phone 631 ms of main-thread work and 969 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 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 430 ms faster on a phone.

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

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

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

2 images could be 142 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Desktop scores 70 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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 first text or image appears after 9.0 s on a phone. Good is under 1.8 s.

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Monterey Bay Herb Co. Acquires NP Nutra, Expanding Leadersh…”.

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

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

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

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

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

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

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

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

Your homepage downloads 2.9 MB in 120 requests on a phone: scripts 1.7 MB (34), images 750 KiB (35) and fonts 240 KiB (10). Under 2 MB keeps phones on slow connections fast.

3 images (208 KiB) 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.

3 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

8 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: 27 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Your title is 116 characters, so Google will cut it off around 60: “NP Nutra® - Wholesale Bulk Raw Materials and Nutraceutical Ingredients NP Nutra (Nature's…”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 261 pages on npnutra.com and 3 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles), 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://npnutra.com/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://npnutra.com/quality-assurance and https://npnutra.com/quality all use the title “QUALITY - NP Nutra® - Wholesale Bulk Raw Materials and Nutraceutical …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://npnutra.com/quality-assurance and https://npnutra.com/quality use the same meta description. A description written for each page earns more clicks.

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

https://npnutra.com/product and https://npnutra.com/product-categories have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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