protectionunit.com website review

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

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

21 images could be 22.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

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

About 605 KiB of JavaScript is downloaded but never used on this page.

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

Cookiebot costs a phone 378 ms of main-thread work and 32 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 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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.

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

For real visitors the layout shifts by 2.00 (75th percentile). Good is under 0.1.

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

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

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

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROTECTION UNIT, VOTRE SOCIÉTÉ DE GARDIENNAGE EN BELGIQUE”. Most of its time is element render delay (5.6 s).

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

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

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

Your homepage downloads 30.8 MB in 149 requests on a phone: images 24.8 MB (32), media 3.1 MB (1) and scripts 2.2 MB (71). Under 2 MB keeps phones on slow connections fast.

3 images (658 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 8.74 g of CO₂e: 1049.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

[aria-*] attributes do not have valid values (1 element).

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Entreprise de sécurité et gardiennage en Belgique | Protection Unit”.

The homepage links to 102 pages on protectionunit.com and 19 external pages.

There is no https://www.protectionunit.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.protectionunit.com/espace-securise is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.protectionunit.com/espace-securise and https://www.protectionunit.com/fr/actualite/united-post have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.protectionunit.com/fr/qui-sommes-nous/secteurs-dactivites and https://www.protectionunit.com/fr/qui-sommes-nous/qualite use the same meta description. A description written for each page earns more clicks.

https://www.protectionunit.com/contact has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.protectionunit.com/fr/qui-sommes-nous/vision-mission-valeurs took over 3 s to send its HTML from our server.

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

3 of 14 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 “Failed to load resource: net::ERR_FAILED”.

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

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

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