snsm.org website review

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

27 files are served with short cache lifetimes, so returning visitors download them again (23.0 MB).

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.6 MB and 1.0 s of main-thread time.

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

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

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

Facebook costs a phone 208 ms of main-thread work and 307 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,105 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

webotit.ai costs a phone 24 ms of main-thread work and 391 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.

5 images could be 206 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 200 ms).

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

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

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

4 KiB could be saved by minifying JavaScript.

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 22.1 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

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

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

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

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

The layout shifts by 0.135 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

5 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-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 30.5 MB in 210 requests on a phone: media 22.6 MB (3), images 5.7 MB (46) and scripts 1.7 MB (66). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example snsm-cohesion-groupe-leo-joachim.webp at 1,024 px wide, shown at 32 px. Resized copies would save about 139 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 8.65 g of CO₂e: 1038.1 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: 11 elements on the page fail this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 135 pages on snsm.org and 40 external pages.

There is no https://www.snsm.org/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.snsm.org/notre-association/notre-organisation and https://www.snsm.org/notre-association/nos-bateaux-de-sauvetage all use the title “Fonctionnement - Les Sauveteurs en Mer”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.snsm.org/newsletter, https://www.snsm.org/espace-presse, https://www.snsm.org/nous-contacter, https://www.snsm.org/notre-association, https://www.snsm.org/notre-association/nos-missions and https://www.snsm.org/notre-association/histoire and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.snsm.org/notre-association/notre-organisation and https://www.snsm.org/notre-association/nos-bateaux-de-sauvetage use the same meta description. A description written for each page earns more clicks.

https://www.snsm.org/nous-soutenir took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 48 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=56097864&tm=gtm002&Ver=2&mid=be6544c1-4f7e-4916-a69a-0b9781592b7e&bo=3&sid=17033480d67d11f1947c11552c97eac1&vid=17034cf0d67d11f180abef1ebdce4aef&vids=0&msclkid=N&pi=91.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 testimonial or review block. 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 1,004 words of visible text.

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