naipo.fr website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and naipo.de and others), adding 2.6 MB and 1.5 s of main-thread time.

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

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

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

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

naipo.de costs a phone 225 ms of main-thread work and 1.2 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.

TikTok costs a phone 253 ms of main-thread work and 161 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,542 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Facebook costs a phone 178 ms of main-thread work and 345 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.

Shopify costs a phone 142 ms of main-thread work and 296 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.

About 45 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.

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

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

16 KiB could be saved by minifying JavaScript.

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

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “La nouvelle génération de relaxation.”. Most of its time is resource load delay (2.6 s).

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

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

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

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

Your homepage downloads 3.4 MB in 309 requests on a phone: scripts 1.9 MB (102), other files 650 KiB (164) and images 316 KiB (17). Under 2 MB keeps phones on slow connections fast.

Mini_Massagepistole.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example Mini_Massagepistole.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 4 KiB.

1 image (35 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.

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

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

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor 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. (2 elements).

Structured data found (BreadcrumbList, MobileApplication, Organization and Store) but with 4 problems, for example “Organization: url points at a different host (https://naipo.de)”.

The homepage links to 294 pages on naipo.fr and 22 external pages.

https://naipo.fr/En-vedette/Ballindamm and https://naipo.fr/En-vedette/salon-de-d%C3%A9tente all use the title “Salon de détente NAIPO | NAIPO”. Search engines can't tell which page to show for a search, so each competes with the others.

https://naipo.fr/En-vedette/Ballindamm and https://naipo.fr/En-vedette/salon-de-d%C3%A9tente use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 119 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=134514980&Ver=2&mid=af8be3df-4e1f-4c9d-8878-3a147d0445f7&bo=1&sid=619c6890d9c711f1974b6b68728636fd&vid=619ca030d9c711f1bec145664a271d87&vids=1&msclkid=N&pi=918639831&l.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://naipo.de/api/collect' from origin 'https://naipo.fr' has been blocked by CORS policy: Respo…”.

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

Requests the notification permission on page load.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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 13 cookies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.