nanz.com website review

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

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

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

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

About 27 KiB of CSS is downloaded but never applied on this page.

26 KiB could be saved by minifying JavaScript.

3 third-party services load with your homepage (Cloudflare CDN, Google Fonts and MyFonts), adding 83 KiB and 4 ms of main-thread time.

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

8 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 5.2 MB in 158 requests on a phone: images 4.4 MB (39), scripts 319 KiB (49) and stylesheets 294 KiB (59). Under 2 MB keeps phones on slow connections fast.

chisel-1.jpg weighs 555 KiB. On a phone connection a single image that size takes seconds.

31 images (4.3 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.

chisel-1.jpg 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 1.47 g of CO₂e: 176.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

Your title is only 21 characters: “Home - NANZ & Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“”, “Home” and “Add to Portfolio”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 641 pages on nanz.com and 4 external pages.

There is no https://www.nanz.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.nanz.com/catalogue, https://www.nanz.com/collections, https://www.nanz.com/hardware/hinges, https://www.nanz.com/hardware/hinges/butt-hinges, https://www.nanz.com/hardware/hinges/olive-knuckle and https://www.nanz.com/hardware/hinges/paumelles and 7 others use the same meta description. A description written for each page earns more clicks.

https://www.nanz.com/hardware/hinges/concealed took over 3 s to send its HTML from our server.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 96 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 10 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.