normet.com website review

The HTML itself could arrive about 1.4 s sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 1.4 s on a phone.

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

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

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

7 third-party services load with your homepage (Google CDN, Google Tag Manager and Cookiebot and others), adding 2.4 MB and 569 ms of main-thread time.

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

Google CDN costs a phone 324 ms of main-thread work and 741 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 3.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your server takes 1.5 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

ctfassets.net costs a phone 0 ms of main-thread work and 1.3 MB 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.

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

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

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

Normet-xrock-www.png weighs 657 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 62 requests on a phone: scripts 1.4 MB (23), images 1.3 MB (19) and other files 588 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image (657 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 is downloaded at several times the size a phone draws it, for example Normet-xrock-www.png at 1,360 px wide, shown at 402 px. Resized copies would save about 140 KiB.

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

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

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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (5 elements).

There are 6 <h1> headlines (“HX-Bolt - Hollow Hybrid Dynamic Bolt”, “Designed for the future underground” and “Discover Normet”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 47 pages on normet.com and 5 external pages.

Your Organization JSON-LD is missing 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://www.normet.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.normet.com/en and https://www.normet.com/en/discover-normet all use the title “Normet – Underground Mining, Tunnelling & Construction Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.normet.com/en/discover-normet and https://www.normet.com/en/news/normet-honoured-with-finlands-national-entrepreneur-of-the-year-award use the same meta description. A description written for each page earns more clicks.

https://www.normet.com/en/discover-normet/innovations/smartdrive, https://www.normet.com/en/normet-xrock and https://www.normet.com/en/normet-xrock/customer-case/tommi-makinen have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.normet.com/en/discover-normet, https://www.normet.com/en/success-stories/future-ready-fleet-management, https://www.normet.com/en/tunnelling/sprayed-concrete-tunnelling, https://www.normet.com/en/normet-xrock, https://www.normet.com/en/news/normet-honoured-with-finlands-national-entrepreneur-of-the-year-award and https://www.normet.com/en/news/codelco-and-normet-partner-to-accelerate-autonomous-underground-mining-technologies and 2 others took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 4 cookies (measured from a US location before any click).

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