vuse.fr website review

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

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

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

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

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

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

8 third-party services load with your homepage (Optanon, Adobe Tag Manager and Facebook and others), adding 936 KiB and 367 ms of main-thread time.

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

About 85 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 26 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.

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

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

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

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

Real visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BAT France collecte et stocke des informations sur votre te…”. Most of its time is element render delay (4.3 s).

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

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

Your homepage downloads 4.1 MB in 284 requests on a phone: scripts 1.4 MB (45), images 1.2 MB (43) and other files 1.1 MB (181). Under 2 MB keeps phones on slow connections fast.

Ultra_Black_PLP_7c1813ff-9ec8-4d31-8ca7-264298a6a470.png 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).

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 196 pages on vuse.fr and 1 external page.

There is no https://www.vuse.fr/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.

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

3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "auto".”.

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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