locinox.com website review

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

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

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

About 156 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and ZenDesk and others), adding 3.3 MB and 1.4 s of main-thread time.

9 images could be 334 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

YouTube costs a phone 326 ms of main-thread work and 987 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.

78 KiB could be saved by minifying JavaScript.

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

ZenDesk costs a phone 260 ms of main-thread work and 473 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.

Google Maps costs a phone 107 ms of main-thread work and 395 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.

Google CDN costs a phone 70 ms of main-thread work and 348 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.

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

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

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

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

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

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

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

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

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

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

14 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-17, real Chrome visitors' tap response (inp) went from 120 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 116 requests on a phone: scripts 3.6 MB (40), images 560 KiB (27) and fonts 270 KiB (7). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 286fa55f-0c6b-4c07-8ec5-2e55dd79d533.png at 640 px wide, shown at 81 px. Resized copies would save about 189 KiB.

4 images (282 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

7 images have no alt text, which hurts accessibility and image search.

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

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

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

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 134 pages on locinox.com and 5 external pages.

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.

There is no https://www.locinox.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.locinox.com/en-gb, https://www.locinox.com/de-de, https://www.locinox.com/fr-fr, https://www.locinox.com/nl-be, https://www.locinox.com/pl-pl and https://www.locinox.com/ru-ru all use the title “Locinox - Gate & Fence Hardware”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.locinox.com/en-gb/contact, https://www.locinox.com/en-gb/gate-closers, https://www.locinox.com/en-gb/gate-closers/new-fit, https://www.locinox.com/en-gb/gate-closers/retro-fit, https://www.locinox.com/en-gb/gate-closers/accessories and https://www.locinox.com/en-gb/gate-closers/accessories/adapters and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.locinox.com/de-de, https://www.locinox.com/fr-fr, https://www.locinox.com/nl-be, https://www.locinox.com/pl-pl and https://www.locinox.com/ru-ru use the same meta description. A description written for each page earns more clicks.

https://www.locinox.com/de-de, https://www.locinox.com/es-es, https://www.locinox.com/fr-fr, https://www.locinox.com/nl-be, https://www.locinox.com/pl-pl and https://www.locinox.com/ru-ru and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.locinox.com/ru-ru has 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.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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