nipro.com website review

10 images could be 8.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.4 s faster on a phone.

Your mobile performance score is 65 (desktop: 70). Pages that score under 90 lose visitors before the first paint.

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

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

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.

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

6 third-party services load with your homepage (Optanon, Google Tag Manager and Matomo and others), adding 452 KiB and 191 ms of main-thread time.

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

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

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

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

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

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

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

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 9.6 MB in 110 requests on a phone: images 8.7 MB (76), scripts 488 KiB (13) and other files 205 KiB (10). Under 2 MB keeps phones on slow connections fast.

4 images weigh 7.9 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example our-purpose_1440-480.jpg at 6,000 px wide, shown at 390 px. Resized copies would save about 6.6 MB.

4 images (7.9 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.

4 images further down the page (6.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

hero-image-top1-1440x960pxl-v1.jpg.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 2.73 g of CO₂e: 327.3 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”.

Contentinfo landmark should not be contained in another landmark: 5 elements on the page fail this check, rated moderate by axe-core.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 31 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 29 characters: “NIPRO Global Homepage | NIPRO”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 16 <h1> headlines (“39000+”, “60+” and “300+”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 166 pages on nipro.com and 8 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://nipro.com/nipro-way and https://nipro.com/news-and-events/news/new-medical-device-manufacturing-facility-greenville-nc-usa have no meta description, so Google writes the search snippet from whatever text it finds.

https://nipro.com/contact-us, https://nipro.com/nipro-way, https://nipro.com/built-create-value, https://nipro.com/about-us/capabilities, https://nipro.com/about-us/built-trust and https://nipro.com/about-us/our-story and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://nipro.com/contact-us, https://nipro.com/nipro-way and https://nipro.com/our-offerings/clinical-essentials took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Service worker registration failed with TypeError: Cannot read properties of undefined (reading 'register')”.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.