tereva.fr website review

About 882 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.

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

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

6 third-party services load with your homepage (Google Tag Manager, Cookiebot and Clarity and others), adding 962 KiB and 751 ms of main-thread time.

Google Tag Manager costs a phone 538 ms of main-thread work and 525 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 3.1 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

4 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Notre site utilise des cookies pour vous garantir la meille…”.

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

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

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

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

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

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

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

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

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

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

Links must have discernible text: 7 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

31 form fields have no label, so screen readers announce an empty box and autofill guesses.

21 links have no real href, so search engines can't follow them.

Your meta description is 191 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.

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

The homepage links to 86 pages on tereva.fr and 4 external pages.

https://www.tereva.fr/C-427705-destockage, https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire, https://www.tereva.fr/C-595069-la-promo-de-l-electricite and https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire/NW-50-domusa-teknik are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire and https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire/NW-50-domusa-teknik all use the title “Achat de Focus - Une offre qui donne le sourire | Téréva”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire and https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire/NW-50-domusa-teknik use the same meta description. A description written for each page earns more clicks.

https://www.tereva.fr/C-427705-destockage, https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire, https://www.tereva.fr/C-595069-la-promo-de-l-electricite and https://www.tereva.fr/C-685169-focus-une-offre-qui-donne-le-sourire/NW-50-domusa-teknik have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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.

Social proof on the homepage: 32 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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 13 cookies (measured from a US location before any click).

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