nord.com website review

45 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.3 s.

About 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Facebook, Cookiebot and Hubspot and others), adding 457 KiB and 290 ms of main-thread time.

10 long tasks block the main thread while loading, the longest for 177 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 24 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 JavaScript.

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 11.6 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 20.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.

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

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

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

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

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

Your homepage downloads 3.2 MB in 91 requests on a phone: scripts 1.4 MB (31), images 1.2 MB (25) and fonts 333 KiB (8). Under 2 MB keeps phones on slow connections fast.

4 images (739 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 are downloaded at several times the size a phone draws them, for example mynord_homeslider_highresolution1920x1152.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 369 KiB.

2 images further down the page (182 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.91 g of CO₂e: 108.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 206 pages on nord.com and 39 external pages.

There is no https://www.nord.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://www.nord.com/oauth2/authorization/keycloak is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.nord.com/us/home-us.jsp and https://www.nord.com/us/index-homepage.jsp all use the title “NORD: Speed Reducers, Gear Motors, AC Vector Drives | NORD”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.nord.com/oauth2/authorization/keycloak, https://www.nord.com/us/products/usp/mynord-dashboard/portal-dashboard.jsp, https://www.nord.com/us/products/usp/product-search/product-search.jsp and https://www.nord.com/us/products/usp/drawings/configurator.jsp have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://www.nord.com/us/products/usp/mynord-dashboard/portal-dashboard.jsp, https://www.nord.com/us/products/usp/product-search/product-search.jsp and https://www.nord.com/us/products/usp/drawings/configurator.jsp have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://e1-0850197d5e074be58352ddc860645af6.ecs.us-east-1.on.aws/events?cee=no' violates the following C…”.

Chrome logged issues while loading the page (“Content security policy”).

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.

Social proof on the homepage: 1 customer or partner logo. 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.

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

The homepage carries about 819 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, HubSpot, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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