nsm-seating.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Lucky Orange and ringcentral.com and others), adding 1.1 MB and 780 ms of main-thread time.

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

About 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.

About 344 KiB of JavaScript is downloaded but never used on this page.

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

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

ringcentral.com costs a phone 148 ms of main-thread work and 298 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 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.

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

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.

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LET'S GET MOVING, TOGETHER”. Most of its time is element render delay (4.6 s).

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

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

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

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

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

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

6 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 103 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 119 requests on a phone: images 1.5 MB (20), scripts 1.1 MB (34) and fonts 143 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (45 KiB) is 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.

1 image further down the page (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

All page content should be contained by landmarks: 11 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 skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: missing name”.

There is no robots.txt at nsm-seating.com/robots.txt, the first file search crawlers ask for.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 62 pages on nsm-seating.com and 12 external pages.

https://www.nsm-seating.com/getting-your-chair is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.nsm-seating.com/getting-your-chair, https://www.nsm-seating.com/journal, https://www.nsm-seating.com/journal/category/education and https://www.nsm-seating.com/journal/category/hearts-of-nsm-champions have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nsm-seating.com/medical-supplies has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.nsm-seating.com/mobility, https://www.nsm-seating.com/medical-supplies, https://www.nsm-seating.com/service-repair, https://www.nsm-seating.com/getting-your-chair, https://www.nsm-seating.com/financing and https://www.nsm-seating.com/journal and 4 others took over 3 s to send their HTML from our server.

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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 911 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). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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