Introduction : why the performance web is a enjeu strategic
En 2026, 53 % visitors mobiles abandonnent a site that met more of 3 secondes à charger. Each seconde of chargement additional réduit the conversions of 7 %, augmente the bounce rate of 11 % and does chuter the satisfaction user of 16 %. The performance web is not a détail technical : it is a factor déterminant of your revenue online.
Google the a compris and a does Core Web Vitals a signal of classement officiel since 2021. En 2026, with the arrivée of the INP (Interaction to Next Paint) en remplacement of the FID, the exigences itself are still renforcées. The sites that offer a experience fast and fluide are récompensés in the search results, while the sites lents are gradually relégués.
Ce guide technical complete, élaboré par the développeurs web of Pirabel Labs, you gives all the key for understand, measure and optimize your Core Web Vitals. Des optimisations d'images to the choix of the CDN, of the minification CSS to the cache serveur, each technical is détaillée with actions concrètes that you can mettre en oeuvre immediately.
The performance web is the fondement invisible of the user experience. A site beau but slow is a site that personne ne visitera deux fois.
The Core Web Vitals mesurent the trois dimensions fondamentales of the user experience : chargement, interactivity and stabilité visuelle.
Comprendre the trois Core Web Vitals
The Core Web Vitals are a together of trois metrics that mesurent the aspects the most critiques of the user experience on a page web. Each metric évalue a dimension specific of the interaction between the user and the page.
LCP (Largest Contentful Paint) : the vitesse of chargement perçue
The LCP mesure the time necessary for that the most large element visible of the page (une image hero, a bloc of text principal, a video) soit entirely rendu à the screen. It is the metric that correspond the most directly à the perception of vitesse par the user. The objective is a LCP lower à 2,5 secondes. Beyond 4 secondes, Google considère the experience like « médiocre ».
The causes the most fréquentes d'un bad LCP are the images non optimisées (format, taille, compression), the polices web that bloquent the rendu, the fichiers CSS and JavaScript volumineux that retardent the first affichage and the time of response serveur too longs (TTFB high).
INP (Interaction to Next Paint) : the réactivity to the interactions
The INP a remplacé the FID (First Input Delay) en mars 2024 like metric officielle d'interactivity. Contrairement to the FID that ne mesurait that the first interaction, the INP évalue the réactivity of the page on the together of the visite. Il mesure the time between a interaction user (clic, tap, appui clavier) and the update visuelle correspondante à the screen. The objective is a INP lower à 200 millisecondes.
A bad INP is generally causé par of the JavaScript that bloque the thread main of the navigateur. The scripts tiers (analytics, advertisings, widgets sociaux), the gestionnaires d'events lourds and the calculs complexes côté client are the coupables habituels. The enjeu is of s'assurer that the navigateur remains réactif à all moment, same during the exécution of scripts.
CLS (Cumulative Layout Shift) : the stabilité visuelle
The CLS mesure the quantité of déplacements inattendus of the content visible during the chargement of the page. You connaissez this frustration : you are on the point of cliquer on a lien and soudain, a image itself charge au-dessus, all the content itself décale and you cliquez on the bad chose. It is exactement this that the CLS quantifie. The objective is a CLS lower à 0,1.
The causes main d'un bad CLS are the images and videos without dimensions explicites (width/height), the advertisings and embeds that s'insèrent dynamiquement, the polices web that provoquent a flash of text invisible (FOIT) or of text non stylisé (FOUT) and the content injecté dynamiquement au-dessus of the content existant.
Mesurer your Core Web Vitals
Avant d'optimize, you need to measure. Google met à disposition several tools for évaluer your Core Web Vitals, each with ses spécificités.
The tools of mesure essentials
- Google PageSpeed Insights : the tool of reference. Il combine data of laboratoire (Lighthouse) and data of terrain (Chrome UX Report) for donner a vue completee of your performance. Test each page key of your site, not only the homepage.
- Google Search Console : the rapport « Signaux Web essentials » you montre the état of your Core Web Vitals for the together of your site, basé on the data réelles users Chrome. It is the source the most fiable car it reflète the experience réelle of your visitors.
- Lighthouse (Chrome DevTools) : intégré in the tools of development of Chrome, Lighthouse effectue a audit complete of performance in a approximatelynement contrôlé. Idéal for the débogage and the identification problems specific.
- Web Vitals Extension : a extension Chrome that affiche in real time the Core Web Vitals during your navigation. Utile for tester quickly the pages after a modification.
The tools of mesure permettent d'identify precisely the goulots d'étranglement of performance of your site.
Optimiser the LCP : accélérer the chargement visible
The optimisation of the LCP is often the chantier the most impactant car it is the metric that the users perçoivent the most directly. Voici the technicals the most effectives, classées par ordre d'impact.
Optimiser the images : the levier numéro un
The images represent en average 50 % of the poids d'une page web. Leur optimisation is the levier the most puissant for improve the LCP.
- Adopter the formats modernes : WebP offers a compression 25 à 35 % highere to the JPEG à quality visuelle équivalente. AVIF, the format of new generation, pousse the compression still more loin with gains of 40 à 50 %. Use the balise <picture> with sources multiples for servir the format optimal according to the navigateur.
- Dimensionner correctly : ne servez never a image of 3 000 pixels of large for a espace d'affichage of 800 pixels. Use the attribut srcset for fournir images adaptées à each taille d'screen.
- Compression intelligente : a compression à 80 % of quality is visuellement indiscernable of the original for the large majority images. Des tools like Squoosh, TinyPNG or ImageOptim automatisent this compression without perte visible.
- Preload of the image LCP : add a <link rel="preload"> in the <head> for the image main of each page. Cela indique to the navigateur of commencer à télécharger the image before same d'avoir analysé the CSS and the HTML.
Optimiser the time of response serveur (TTFB)
The Time to First Byte (TTFB) is the time between the query of the navigateur and the réception of the first octet of response of the serveur. A TTFB high retarde all the chaîne of chargement. The objective is a TTFB lower à 800 ms.
- Utiliser a CDN (Content Delivery Network) : a CDN like Cloudflare, Fastly or AWS CloudFront distribue your content since serveurs situés to the more près of your visitors. A user à Paris accède à a serveur parisien, not à a serveur américain.
- Activer the cache serveur : the cache côté serveur (Varnish, Redis, Memcached) évite of recalculer the same page à each query. For the sites à content statique or semi-statique, the cache can reduce the TTFB of 90 %.
- Choisir a hosting performant : a hosting mutualisé à 3 euros par mois ne supportera never the performance d'un VPS or d'un serveur dédié. The hosting is a investissement, not a dépense.
Éliminer the resources that bloquent the rendu
The fichiers CSS and JavaScript in the <head> bloquent the rendu of the page so much that they are not entirely téléchargés and analysés. Each fichier bloquant ajoute centaines of millisecondes to the LCP.
- CSS critique online : identify the CSS necessary for rendre the content visible au-dessus of the line of flottaison and integrate-le directly in the HTML with a balise <style>. The remains of the CSS can être chargé of way asynchrone.
- Différer the JavaScript non critique : add the attribut defer or async à all the scripts that are not indispensables to the first rendu. The defer is generally préférable car he guarantees the ordre d'exécution.
- Minifier CSS and JavaScript : the minification supprime the espaces, the howaires and the caractères inutiles. Elle réduit typiquement the taille fichiers of 20 à 40 % without no changement fonctionnel.
Optimiser the INP : rendre your site réactif
The INP is the metric the most technical à optimize car it implique a compréhension fine of the fonctionnement of the thread main of the navigateur and of the boucle d'events JavaScript.
Diviser the tasks longues (Long Tasks)
The navigateur utilise a only thread main for exécuter the JavaScript, calculer the styles, effectuer the mise en page and peindre the pixels. Lorsqu'une task JavaScript takes more of 50 ms, it bloque the thread main and empêche the navigateur of répondre to the interactions of the user. It is the cause numéro a bad scores INP.
The solution is of diviser the tasks longues en sous-tasks more courtes en utilisant technicals like requestAnimationFrame, setTimeout(fn, 0) or the API scheduler.yield() disponible in the navigateurs modernes. The idée is of rendre the contrôle to the navigateur between each sous-task for that he puisse traiter the interactions en attente.
Réduire the impact scripts tiers
The scripts tiers (Google Analytics, pixels publicitaires, widgets of chat, intégrations sociales) are often the most gros consommateurs of time on the thread principal. Each script tiers that you add à your site is a cost of performance.
- Auditer regularly your scripts tiers : supprimez ceux that ne are more utilisés or whose the value ne justifie not the cost en performance.
- Charger the scripts tiers en différé : no script tiers n'a need d'être chargé immediately. Use defer, async or the chargement conditionnel (charger the widget of chat uniquement when the user scrolle or clique).
- Utiliser façades (facades) : for the embeds lourds like the videos YouTube or the cartes Google Maps, affichez a image statique and ne chargez the embed réel that to the clic. This technical can économiser centaines of kilooctets of JavaScript.
A site réactif and performant offers a user experience that fidélise the visitors and booste the conversions.
Optimiser the CLS : stabiliser the affichage
The CLS is often the metric the most simple à corriger car the causes are well identifiées and the solutions are mainly good pratiques HTML/CSS.
Toujours define the dimensions médias
The cause numéro a of the CLS is the images and videos without attributs width and height. Lorsque the navigateur rencontre a image without dimensions, he lui alloue a espace of 0 pixel then redimensionne the mise en page lorsque the image is chargée, provoquant a décalage visible. The solution is triviale : add always the attributs width and height à your balises <img> and <video>. The navigateur usea the ratio of these dimensions for réserver the espace correct before the chargement.
Réserver the espace for the contents dynamiques
The advertisings, the embeds tiers and the contents chargés dynamiquement are sources fréquentes of CLS. The solution is of réserver a espace fixe for these elements with of the CSS, same before their chargement. Use min-height, aspect-ratio or conteneurs of taille fixe for garantir that the insertion of the content ne déplace not the remains of the page.
Gérer the polices web correctly
The polices web can provoquer a CLS si the text change of taille or d'espacement lorsque the police personalized remplace the police system of substitution. The propriété CSS font-display: swap is recommandée for afficher immediately the text with a police system, then basculer toward the police personalized a fois chargée. For minimiser the décalage visuel, choose polices system of substitution whose the metrics are proches of your police personalized.
The lazy loading : charger intelligemment
The lazy loading consiste à ne charger the resources (images, videos, iframes) that lorsqu'elles are on the point d'entrer in the zone visible of the screen. This technical réduit drastically the time of chargement initial and économise the bande passante for the contents that the user ne verra peut-être never.
The lazy loading natif of the navigateur
The attribut loading="lazy" is now supporté par all the navigateurs modernes. Il suffit of the ajouter to the balises <img> and <iframe> for activer the lazy loading natif, without JavaScript additional. It is the method recommandée for sa simplicité and sa performance.
Attention critique : ne mettez never loading="lazy" on the images visibles au-dessus of the line of flottaison, and notably on the image LCP. The lazy loading retarderait their chargement and dégraderait your score LCP. Réservez the lazy loading to the images situées en dessous of the first screen visible.
The strategy of cache : servir instantanément
A cache well configuré allows you to servir pages en a few millisecondes to the lieu of centaines of millisecondes. It is the optimisation with the best ratio effort/impact for the visitors récurrents.
The cache navigateur (headers HTTP)
Configurez headers Cache-Control appropriés for each type of resource. The resources statiques that ne changent never (images, polices, CSS/JS versionnés) must avoir a cache d'un an (max-age=31536000) with a hash in the nom of fichier for the invalidation. The pages HTML must avoir a cache court (max-age=0, must-revalidate) for garantir that the visitors voient always the content à jour.
The cache CDN
The CDN ajoute a couche of cache additional between your serveur and the visitors. Lorsqu'un visitor à Lyon demande your page, the CDN the sert since son point of presence lyonnais without never contacter your serveur d'origine. Configurez règles of cache CDN distinctes for the resources statiques (cache long) and the pages dynamiques (cache court with invalidation automatique lors updates).
Checklist of performance : the actions prioritaires
Voici a checklist synthétique optimisations à mettre en oeuvre, classées par impact and facilité d'implémentation.
- Compresser and redimensionner all the images en WebP or AVIF with dimensions adaptées to the conteneurs d'affichage.
- Ajouter width and height à all the balises <img> and <video> for éliminer the CLS.
- Mettre en place a CDN (Cloudflare propose a plan gratuit performant) for reduce the TTFB mondial.
- Minifier the fichiers CSS and JavaScript with tools like Terser, cssnano or esbuild.
- Différer all the scripts non critiques with the attribut defer or async.
- Activer the lazy loading on all the images under the line of flottaison.
- Preload the image LCP and the polices web critiques.
- Configurer the headers of cache with durées appropriées for each type of resource.
- Auditer and reduce the scripts tiers en supprimant ceux that are inutiles and en différant the autres.
- Activer the compression Gzip or Brotli côté serveur for reduce the taille transferts of 60 à 80 %.
Conclusion : the performance like culture, not like projet
The optimisation Core Web Vitals is not a projet ponctuel à cocher on a liste. It is a culture of the performance that must imprégner each decision technical and éditoriale. Each new image ajoutée, each new script intégré, each new feature déployée impacte the performance of your site. The enjeu is of maintain a level d'excellence constant in the time.
The benefits d'un site performant dépassent largement the SEO. A site fast améliore the conversion rate, réduit the costs d'hosting (moins of bande passante consommée), améliore the accessibility for the users en connexion lente and renforce the perception of professionnalisme of your brand. Each milliseconde gagnée itself traduit par a best experience for your visitors and a best return on investment for your business.
The team technical of Pirabel Labs réalise audits of performance completes and accompagne the businesses in the optimisation of their Core Web Vitals. Contactez-nous for a audit of performance gratuit and discover how a site ultra-rapide can transform your results online.