nitrex.com website review

About 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.4 s faster on a phone.

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

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

Google CDN costs a phone 1.3 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Hubspot and Google Tag Manager and others), adding 4.7 MB and 2.7 s of main-thread time.

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

Hubspot costs a phone 709 ms of main-thread work and 1.1 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.

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

22 KiB could be saved by minifying JavaScript.

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 CSS.

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 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website stores cookies on your computer. These cookies…”.

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

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

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

The layout shifts by 0.295 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 9.1 MB in 281 requests on a phone: scripts 5.0 MB (98), images 2.0 MB (55) and other files 1.1 MB (43). Under 2 MB keeps phones on slow connections fast.

3 images (861 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.

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

Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

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

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails 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.

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

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

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

Your title is 73 characters, so Google will cut it off around 60: “Nitrex provides fully integrated heat-treating services and technologies.”.

There are 2 <h1> headlines (“- NITREX -” and “Nitrex is redefining heat treatment with the most…”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 328 pages on nitrex.com and 73 external pages.

There is no /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.

/en and / all use the title “Nitrex provides fully integrated heat-treating services and technolog…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en/furnaces-technologies/nitriding-nitrocarburizing and /furnaces-technologies/nitriding-nitrocarburizing use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is /en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en/solutions/furnaces-technologies/nitriding-nitrocarburizing/turnkey-installations/nxh-horizontal-series and /en/solutions/furnaces-technologies/nitriding-nitrocarburizing/turnkey-installations/nxl-continuous-series took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343122911&tm=gtm002&Ver=2&mid=5cb89f5e-d029-4e15-9de0-ceff56672d52&bo=1&sid=d94cb440d5e611f19f008b133af7254e&vid=d94cd470d5e611f185a395a192971361&vids=1&msclkid=N&pi=9.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute')”.

8 images are served at too low a resolution for sharp phone screens.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://nitrex.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block, 1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

nitrex.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

nitrex.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

nitrex.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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