alan.com website review

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

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

About 1,012 KiB of JavaScript is downloaded but never used on this page.

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

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

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

twic.pics costs a phone 48 ms of main-thread work and 682 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.

4 third-party services load with your homepage (piwik.pro, twic.pics and Cloudflare and others), adding 845 KiB and 109 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 128 requests on a phone: scripts 1.9 MB (43), images 1.3 MB (76) and media 132 KiB (2). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example MzE4JsQDorsfeEZS_Mo-Chat-FR-fr.png at 750 px wide, shown at 160 px. Resized copies would save about 65 KiB.

2 images further down the page (40 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 76 characters, so Google will cut it off around 60: “Alan | Le nouveau standard de l’Assurance Prévention : la santé n’attend pas”.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 119 pages on alan.com and 8 external pages.

/fr-fr/privacy, /fr-fr/assurance-sante/pourquoi-alan/couvrir-premiers-salaries, /fr-fr/assurance-sante/pourquoi-alan/preserver-pouvoir-achat, /fr-fr/assurance-sante/pourquoi-alan/sante-au-travail, /fr-fr/assurance-sante/pourquoi-alan and /fr-fr/assurance-sante/pourquoi-alan/app-sante and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/fr-fr/assurance-sante/pourquoi-alan/couvrir-premiers-salaries took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 64 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”.

Large scripts ship without source maps.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.