Website review, no card needed
nord-lock.com website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 84 checks
This review found 42 issues worth fixing on nord-lock.com, 17 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 266 ms |
| May 23, 2026 | 254 ms |
| May 30, 2026 | 239 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 185 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 189 ms |
| Sep 12, 2026 | 193 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 208 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 211 ms |
| Oct 31, 2026 | 203 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.8 s
4.8 s
5.7 s
6.7 s
7.6 s
Speed
Reduce unused JavaScript
1.9 s · 555 KiBAbout 555 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Google Tag Manager adds 2.1 s
2.1 sGoogle Tag Manager costs a phone 2.1 s of main-thread work and 520 KiB 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.
Render-blocking requests
1.9 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and azure.com and others), adding 822 KiB and 2.6 s of main-thread time.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Improve image delivery
528 KiB7 images could be 528 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Cookiebot adds 290 ms
290 msCookiebot costs a phone 290 ms of main-thread work and 158 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.
1,612 HTML elements
The page has 1,612 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 108 KiBAbout 108 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 14 KiB14 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
154 KiB9 files are served with short cache lifetimes, so returning visitors download them again (154 KiB).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Safe bolted connections”.
Total Blocking Time: 4.0 s
4.0 sScripts block taps and scrolling for 4.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 147 ms
147 msReal visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 266 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Images and page weight
Page weight: 16.1 MB in 53 requests
16.1 MBYour homepage downloads 16.1 MB in 53 requests on a phone: media 13.1 MB (1), scripts 1.4 MB (13) and images 1.3 MB (16). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (700 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
335 KiB3 images are downloaded at several times the size a phone draws them, for example 001-image.png at 3,840 px wide, shown at 326 px. Resized copies would save about 335 KiB.
About 4.6 g of CO₂ per visit
4.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.57 g of CO₂e: 548.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
20 internal links, 1 external
The homepage links to 20 pages on nord-lock.com and 1 external page.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Whatever your bolting challenges, Nord-Lock Group has the solution. Explore our four brand technologies and their criti…”.
Title: 52 characters
Your title is a healthy 52 characters: “Solutions for secure bolted joints - Nord-Lock Group”.
Canonical URL set
The canonical URL is https://www.nord-lock.com/.
Structured data in place
Structured data found: WebPage.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.nord-lock.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
8%A phone browser shows 659 words, but the HTML your server sends has only 54. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.nord-lock.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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
13 pages share 2 titles
/, https://www.nord-lock.com/en-au, https://www.nord-lock.com/de-de, https://www.nord-lock.com/en-in, https://www.nord-lock.com/it-it and https://www.nord-lock.com/ja-jp and 5 others all use the title “Solutions for secure bolted joints - Nord-Lock Group”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages share a meta description
https://www.nord-lock.com/en-au, https://www.nord-lock.com/de-de, https://www.nord-lock.com/en-in, https://www.nord-lock.com/it-it, https://www.nord-lock.com/ja-jp and https://www.nord-lock.com/de-ch and 4 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.nord-lock.com/latam, https://www.nord-lock.com/en-au, https://www.nord-lock.com/pt-br, https://www.nord-lock.com/fr-fr, https://www.nord-lock.com/de-de and https://www.nord-lock.com/en-in and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.nord-lock.com/latam, https://www.nord-lock.com/en-au, https://www.nord-lock.com/pt-br, https://www.nord-lock.com/fr-fr, https://www.nord-lock.com/de-de and https://www.nord-lock.com/en-in and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
21 small tap targets
21 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 659 words of copy
The homepage carries about 659 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before 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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at nord-lock.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Episerver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on nord-lock.com, including 20 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.