tessi.fr website review

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

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

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

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, axept.io and Google Fonts and others), adding 203 KiB and 112 ms of main-thread time.

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

10 KiB could be saved by minifying JavaScript.

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 see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

The first text or image appears after 2.3 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 110 ms to 111 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 2.7 s to 3.0 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.37 g of CO₂e: 44.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 buttons have no accessible name, so screen readers announce just “button”.

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 3 problems, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

The homepage links to 186 pages on tessi.fr and 2 external pages.

There is no https://www.tessi.eu/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.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/facture-et-paiement/facturation-electronique-processus-procure-to-pay and https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/facture-et-paiement/factures-clients-procure-to-pay-order-to-cash all use the title “Facture électronique : Plateforme Agréée DIGITAL INVOICE by Tessi”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tessi.eu/fr/decouvrir-tessi and https://www.tessi.eu/fr/decouvrir-tessi/decouvrez-lespace-presse have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/facture-et-paiement/facturation-electronique-processus-procure-to-pay and https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/facture-et-paiement/factures-clients-procure-to-pay-order-to-cash use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/document/editique-flux-sortants-marketing-direct, whose canonical is https://www.tessi.eu/fr/digital-experience-by-tessi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/document/editique-flux-sortants-marketing-direct and https://www.tessi.eu/fr/solution/services/digitalisation-des-processus-documentaires/facture-et-paiement/facturation-electronique-processus-procure-to-pay took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “wp is not defined”.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 475 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 4 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.