sesa-systems.com website review

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

vurbismarketplace.com costs a phone 1.3 s of main-thread work and 58 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (vurbismarketplace.com, Google Tag Manager and Cookiebot and others), adding 1.6 MB and 2.4 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

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

Google Tag Manager costs a phone 513 ms of main-thread work and 530 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 246 ms of main-thread work and 453 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 166 ms of main-thread work and 569 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 52 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.

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

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

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

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

18 KiB could be saved by minifying JavaScript.

8 KiB JavaScript is shipped twice across bundles.

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.

2 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 582 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 170 ms to 599 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 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.9 MB in 187 requests on a phone: media 6.6 MB (1), scripts 1.8 MB (58) and other files 590 KiB (69). Under 2 MB keeps phones on slow connections fast.

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

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

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

Your meta description is 206 characters; Google truncates after about 160, so the end of your pitch is cut.

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

Your <h1> is empty.

The homepage links to 271 pages on sesa-systems.com and 6 external pages.

Your homepage links to https://www.sesa-systems.com/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.sesa-systems.com/pages/contact, https://www.sesa-systems.com/pages/consultez-nos-catalogues, https://www.sesa-systems.com/pages/prendre-rendez-vous-avec-un-charge-daffaires and https://www.sesa-systems.com/pages/creation-de-compte have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sesa-systems.com/pages/creation-de-compte has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sesa-systems.com/collections/les-fondamentaux-5s, https://www.sesa-systems.com/collections/protege-document and https://www.sesa-systems.com/collections/pictogramme-adhesif-au-sol took over 3 s to send their HTML from our server.

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 2,008 words of visible text.

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

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