PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 11, 2025, 8:00:48 AM
Showing results for URL: https://www.homair.com/
Run with original URL
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)90%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)3%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
512 ms
Page LoadsGood (≤ 200 ms)39%Needs Improvement (200 ms - 500 ms)36%Poor (> 500 ms)26%75th Percentile - 512 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)100%Needs Improvement (0.1 - 0.25)0%Poor (> 0.25)0%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.6 s
Page LoadsGood (≤ 1.8 s)79%Needs Improvement (1.8 s - 3 s)14%Poor (> 3 s)7%75th Percentile - 1.6 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)74%Needs Improvement (0.8 s - 1.8 s)20%Poor (> 1.8 s)5%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)89%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)4%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
413 ms
Page LoadsGood (≤ 200 ms)52%Needs Improvement (200 ms - 500 ms)27%Poor (> 500 ms)20%75th Percentile - 413 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)98%Needs Improvement (0.1 - 0.25)1%Poor (> 0.25)2%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)82%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)7%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)77%Needs Improvement (0.8 s - 1.8 s)16%Poor (> 1.8 s)7%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
60 FCP+7LCP+13TBT+12CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
760 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.039
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
7.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 11, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 440 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
homair.com
1st party
1,684 ms
856 ms
49 ms
623 ms
9 ms
8 ms
548 ms
520 ms
1 ms
305 ms
157 ms
2 ms
147 ms
119 ms
28 ms
/2.24.0/hv-vendors.js
(cdn.homair.com)
61 ms
51 ms
9 ms
Noibu
utility
601 ms
168 ms
6 ms
/collect.js
(cdn.noibu.com)
601 ms
168 ms
6 ms
Google Tag Manager
tag-manager
516 ms
466 ms
46 ms
/gtag/js?id=…
(www.googletagmanager.com)
169 ms
159 ms
9 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
113 ms
100 ms
12 ms
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
85 ms
73 ms
11 ms
/gtag/js?id=…
(www.googletagmanager.com)
78 ms
70 ms
7 ms
/gtag/destination?id=…
(www.googletagmanager.com)
71 ms
63 ms
6 ms
mcangelus.com
437 ms
362 ms
3 ms
…i/78a2d9a….js
(eudevil.mcangelus.com)
437 ms
362 ms
3 ms
Unattributable
237 ms
43 ms
0 ms
Unattributable
237 ms
43 ms
0 ms
AB Tasty
analytics
114 ms
104 ms
9 ms
114 ms
104 ms
9 ms
Minimize main-thread work 3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
2,150 ms
Style & Layout
592 ms
Other
574 ms
Rendering
213 ms
Script Parsing & Compilation
130 ms
Parse HTML & CSS
87 ms
Garbage Collection
50 ms
Largest Contentful Paint element 3,870 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
section#hp-carousel > div#hp-carousel-block > div#carousel-home > div.carousel-cell
<div class="carousel-cell cell-0" style="background-image: url(&quot;https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2…&quot;);">
Phase
% of LCP
Timing
TTFB
23%
870 ms
Load Delay
7%
280 ms
Load Time
29%
1,110 ms
Render Delay
41%
1,600 ms
Eliminate render-blocking resources Potential savings of 1,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
homair.com
1st party
60.7 KiB
3,600 ms
/2.24.0/hv-home.css
(cdn.homair.com)
4.2 KiB
750 ms
/2.24.0/hv-main.css
(cdn.homair.com)
46.8 KiB
1,350 ms
4.4 KiB
750 ms
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
5.2 KiB
750 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 270 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
736 KiB
160 ms
/gtag/js?id=…
(www.googletagmanager.com)
141 KiB
114 ms
/gtag/js?id=…
(www.googletagmanager.com)
106 KiB
27 ms
/gtag/destination?id=…
(www.googletagmanager.com)
93 KiB
19 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
127 KiB
0 ms
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
159 KiB
0 ms
/gtag/js?id=AW-103…
(www.googletagmanager.com)
107 KiB
0 ms
2 KiB
0 ms
Noibu
utility
79 KiB
54 ms
/collect.js
(cdn.noibu.com)
73 KiB
54 ms
/collect-worker.js
(cdn.noibu.com)
6 KiB
0 ms
mcangelus.com
42 KiB
29 ms
…i/78a2d9a….js
(eudevil.mcangelus.com)
40 KiB
29 ms
/ct?id=…
(potter.mcangelus.com)
1 KiB
0 ms
/mon
(potter.mcangelus.com)
1 KiB
0 ms
/tracker/tc_imp.gif?e=37dfbd8…
(potter.mcangelus.com)
0 KiB
0 ms
AB Tasty
analytics
100 KiB
28 ms
74 KiB
25 ms
/84cc8d9….js
(try.abtasty.com)
2 KiB
3 ms
7 KiB
0 ms
/shared/me.0c0baf9….js
(try.abtasty.com)
4 KiB
0 ms
/84cc8d9…/initiator.js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
/84cc8d9…/manifest.json
(try.abtasty.com)
1 KiB
0 ms
1 KiB
0 ms
/v1/geoip?weather=false
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
/v1/ua-parser
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
0 KiB
0 ms
Tealium
tag-manager
12 KiB
0 ms
11 KiB
0 ms
…2/i.gif
(collect.tealiumiq.com)
1 KiB
0 ms
leadsmonitor.io
2 KiB
0 ms
/lm.js
(homair-1.leadsmonitor.io)
1 KiB
0 ms
/pixel.gif?id=IS3TMDHY1AFLKG2J
(homair-1.leadsmonitor.io)
0 KiB
0 ms
Google/Doubleclick Ads
ad
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Serve images in next-gen formats Potential savings of 50 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
homair.com
1st party
165.4 KiB
49.5 KiB
section#hp-carousel > div#hp-carousel-block > div#carousel-home > div.carousel-cell
<div class="carousel-cell cell-0" style="background-image: url(&quot;https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2…&quot;);">
82.3 KiB
23.0 KiB
div.flickity-slider > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2025-02/vignette-paques…" alt="">
30.0 KiB
9.6 KiB
div.flickity-slider > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2025-01/nouveautes-2025…" alt="">
27.6 KiB
8.7 KiB
div.flickity-slider > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2025-03/regionvedette-v…" alt="">
25.5 KiB
8.3 KiB
Reduce unused CSS Potential savings of 43 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
homair.com
1st party
46.3 KiB
42.7 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
46.3 KiB
42.7 KiB
Avoid an excessive DOM size 2,146 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
2,146
Maximum DOM Depth
Argelès-sur-Mer
<a href="/camping-argeles-sur-mer">
16
Maximum Child Elements
body.home
<body class="home lang-fr onMobileDevice mobyletteLoaded">
44
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
homair.com
1st party
div.track-promo > div.carousel-block > div.col-lg-6 > img
<img src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2025-02/offre-printemps…" alt="" loading="eager" fetchpriority="high">
Camping Homair
<img class="logo-image tooltip-homair-logo tooltipstered" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg" alt="Camping Homair">
…HV/logo.svg
(cdn-2.homair.com)
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
…HV/logo.svg
(cdn-2.homair.com)
Catalogue Homair
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-01/mockup-catalogue-homai…" alt="Catalogue Homair">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
Unattributable
Homair Logo
<img alt="Homair Logo" src="" id="footer-logo" loading="lazy">
Serve static assets with an efficient cache policy 33 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
homair.com
1st party
574 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
None
83 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
None
47 KiB
/2.24.0/hv-main.js
(cdn.homair.com)
None
37 KiB
None
27 KiB
/2.24.0/hv-map.css
(cdn.homair.com)
None
6 KiB
None
5 KiB
None
4 KiB
/2.24.0/hv-home.css
(cdn.homair.com)
None
4 KiB
/2.24.0/hv-home.js
(cdn.homair.com)
None
1 KiB
/2.24.0/hv-widgets.js
(cdn.homair.com)
None
1 KiB
None
1 KiB
16d
83 KiB
16d
31 KiB
16d
29 KiB
16d
28 KiB
16d
27 KiB
16d
24 KiB
16d
24 KiB
16d
20 KiB
16d
19 KiB
16d
19 KiB
16d
18 KiB
/gfx/spritesheet.png
(cdn-2.homair.com)
16d
13 KiB
16d
10 KiB
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
16d
5 KiB
16d
5 KiB
…HV/logo.svg
(cdn-2.homair.com)
16d
3 KiB
…4x3/fr.svg
(cdn-2.homair.com)
16d
1 KiB
Noibu
utility
73 KiB
/collect.js
(cdn.noibu.com)
30m
73 KiB
mcangelus.com
40 KiB
…i/78a2d9a….js
(eudevil.mcangelus.com)
12h
40 KiB
Tealium
tag-manager
11 KiB
5m
11 KiB
AB Tasty
analytics
2 KiB
/84cc8d9….js
(try.abtasty.com)
6h
2 KiB
leadsmonitor.io
1 KiB
/lm.js
(homair-1.leadsmonitor.io)
None
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
homair.com
1st party
50 ms
20 ms
20 ms
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Source
homair.com
1st party
Defer offscreen images Potential savings of 54 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
homair.com
1st party
54.3 KiB
54.3 KiB
div.flickity-slider > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2025-01/nouveautes-2025…" alt="">
27.6 KiB
27.6 KiB
Catalogue Homair
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-01/mockup-catalogue-homai…" alt="Catalogue Homair">
23.0 KiB
23.0 KiB
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
3.7 KiB
3.7 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 21 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
leadsmonitor.io
7.8 KiB
/lm.js
(homair-1.leadsmonitor.io)
7.8 KiB
/lm.js:75:4
(homair-1.leadsmonitor.io)
Date.now
Google Tag Manager
tag-manager
7.4 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
7.4 KiB
/gtm.js?id=GTM-TVMQPKZ:13:1776
(www.googletagmanager.com)
Date.prototype.toJSON
homair.com
1st party
5.9 KiB
5.8 KiB
Object.keys
Object.values
@babel/plugin-transform-classes
/2.24.0/hv-vendors.js
(cdn.homair.com)
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
/2.24.0/hv-main.js
(cdn.homair.com)
0.0 KiB
@babel/plugin-transform-classes
Reduce unused JavaScript Potential savings of 554 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
727.3 KiB
341.6 KiB
/gtag/js?id=AW-103…
(www.googletagmanager.com)
105.8 KiB
81.9 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
157.9 KiB
58.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
140.2 KiB
53.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
105.0 KiB
53.3 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
92.3 KiB
48.2 KiB
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
126.1 KiB
46.2 KiB
homair.com
1st party
265.4 KiB
166.4 KiB
183.3 KiB
111.8 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
82.1 KiB
54.7 KiB
Noibu
utility
72.0 KiB
45.8 KiB
/collect.js
(cdn.noibu.com)
72.0 KiB
45.8 KiB
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
homair.com
1st party
1,043 ms
7,827 ms
387 ms
11,419 ms
207 ms
14,378 ms
130 ms
4,737 ms
98 ms
1,231 ms
81 ms
4,625 ms
74 ms
1,342 ms
66 ms
Google Tag Manager
tag-manager
310 ms
/gtag/js?id=…
(www.googletagmanager.com)
14,214 ms
164 ms
/gtag/js?id=…
(www.googletagmanager.com)
11,270 ms
77 ms
/gtag/destination?id=…
(www.googletagmanager.com)
15,278 ms
69 ms
mcangelus.com
79 ms
…i/78a2d9a….js
(eudevil.mcangelus.com)
11,191 ms
79 ms
AB Tasty
analytics
75 ms
12,777 ms
75 ms
Noibu
utility
58 ms
/collect.js
(cdn.noibu.com)
10,916 ms
58 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
RECHERCHEZ VOTRE CAMPING-VILLAGE : Tous 2 Personnes Rechercher Nos offres à ne …
<section id="hp-carousel">
0.039
Catalogue Homair
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-01/mockup-catalogue-homai…" alt="Catalogue Homair">
Media element lacking an explicit size
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,695.928 ms
Initial Navigation
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
- 23.094 ms, 19.75 KiB
- 22.544 ms, 28.28 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
- 1,539.798 ms, 46.81 KiB
/2.24.0/hv-home.css
(cdn.homair.com)
- 1,797.463 ms, 4.22 KiB
- 1,010.231 ms, 4.45 KiB
/2.24.0/hv-map.css
(cdn.homair.com)
- 1,042.233 ms, 6.35 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 600 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
homair.com
1st party
600 ms
600 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 2,001 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google Tag Manager
tag-manager
733.9 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
159.0 KiB
/gtag/js?id=…
(www.googletagmanager.com)
141.3 KiB
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
127.2 KiB
/gtag/js?id=AW-103…
(www.googletagmanager.com)
106.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
106.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
93.4 KiB
homair.com
1st party
571.8 KiB
221.5 KiB
184.4 KiB
83.2 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
82.6 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
section#hp-carousel > div#hp-carousel-block > div#carousel-home > div.carousel-cell
<div class="carousel-cell cell-0" style="background-image: url(&quot;https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2…&quot;);">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Failing Elements
div#menu-langues-mobile > div.menu-langue-top > div.menu-langue-toggle-wrapper > button#menu-langue-toggle
<button id="menu-langue-toggle">
div.container > div#header-right > div#header-buttons > button#custarea-tooltip
<button class="btn-custarea tooltip-title tooltipstered" id="custarea-tooltip" data-tooltip-content="#tooltip_custarea_content" onclick="location.href=&quot;/espace-client&quot;">
div.container > div#header-right > div#header-buttons > button.basket-tooltip
<button class="basket-tooltip js-basket-count" data-tooltip-content="#tooltip_basket_content">
div.form-widget > div.DateRangePicker > div.DateRangePickerInput > button.DateRangePickerInput_calendarIcon
<button class="DateRangePickerInput_calendarIcon DateRangePickerInput_calendarIcon_1" type="button">
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2024-05/acheter-un-mobi…">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
body.home > div#_lm_pix > img
<img src="https://homair-1.leadsmonitor.io/pixel.gif?id=IS3TMDHY1AFLKG2J" width="1" height="1" border="0">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
RECHERCHEZ VOTRE CAMPING-VILLAGE :
<h2 id="hp-search-title">
RECHERCHEZ VOTRE CAMPING-VILLAGE : Tous 2 Personnes Rechercher
<div id="hp-search">
-28%
<span class="hvnew-pourcentage discount-28">
273€*
<span class="hvnew-price">
La Grande Métairie France - Bretagne - Carnac du 12/04 au 19/04 -28%
<div class="hvnew-bloc-camping clearfix">
250 campings où se ressourcer
<h3 class="hvnew-title">
250 campings où se ressourcer AU RYTHME DES VAGUES En savoir plus
<div class="hvnew-bloc-inter-idees-sejours">
DEVENEZ PROPRIÉTAIRE
<div class="hvnew-title">
DEVENEZ PROPRIÉTAIRE DEVENEZ PROPRIÉTAIRE Découvrez notre marque dédiée à la ve…
<div class="hvnew-bloc-inter-thema">
RECEVEZ TOUS NOS BONS PLANS !
<div class="title pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Inscrivez-vous à notre newsletter et recevez nos ventes flash et promos en avan…
<div>
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Votre adresse de messagerie est uniquement utilisée pour vous envoyer les newsl…
<div class="complement">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
En savoir plus sur la gestion de vos données et vos droits
<button data-type="iframe" data-src="https://www.homair.com/charte-de-protection-des-donnees-personnelles?forma…" class="alinkstyle popinIframe" style="color: #ffffff; text-decoration: underline;">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
notre centre d'aide
<button class="alinkstyle" onclick="window.open('https://contact.homair.com/hc/fr', '_blank');" style="color: #ffffff; text-decoration: underline;">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
LE CATALOGUE 2025
<div class="pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Feuilleter les pages, se projeter, s'inspirer... Et si vous consultiez notre ca…
<p>
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
SUIVEZ-NOUS SUR :
<div class="pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
CONTINUER SANS ACCEPTER
<div class="digiConsentButtons rejectAll" id="digiconsentbanddecline">
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪 Les cookies nous permettent de vo…
<div id="digiConsentWelcome" style="display: flex;">
PARAMÉTRER MES COOKIES
<div class="digiConsentButtons" id="digiconsentbandparam">
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪 Les cookies nous permettent de vo…
<div id="digiConsentWelcome" style="display: flex;">
ACCEPTER ET CONTINUER
<div class="digiConsentButtons acceptAll" id="digiconsentbandaccept">
These are opportunities to improve the legibility of your content.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Alsace
<a href="/camping-alsace">
Annecy
<a href="/camping-annecy">
Annecy
<a href="/camping-annecy">
Alsace
<a href="/camping-alsace">
Arcachon
<a href="/arcachon">
Arcachon
<a href="/arcachon">
Annecy
<a href="/camping-annecy">
Ardèche
<a href="/ardeche">
Ardèche
<a href="/ardeche">
Arcachon
<a href="/arcachon">
Ardennes
<a href="/ardennes">
Ardennes
<a href="/ardennes">
Ardèche
<a href="/ardeche">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Ardennes
<a href="/ardennes">
Aveyron
<a href="/camping-aveyron">
Aveyron
<a href="/camping-aveyron">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Bretagne
<a href="/bretagne">
Bretagne
<a href="/bretagne">
Aveyron
<a href="/camping-aveyron">
Cap d'Agde
<a href="/camping-cap-dagde">
Cap d'Agde
<a href="/camping-cap-dagde">
Bretagne
<a href="/bretagne">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Cap d'Agde
<a href="/camping-cap-dagde">
Charente Maritime
<a href="/charente-maritime">
Charente Maritime
<a href="/charente-maritime">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Corse
<a href="/camping-corse">
Charente Maritime
<a href="/charente-maritime">
Corse du Sud
<a href="/camping-corse-du-sud">
Corse du Sud
<a href="/camping-corse-du-sud">
Côte d'Azur
<a href="/camping-cote-dazur">
Côte d'Azur
<a href="/camping-cote-dazur">
Corse du Sud
<a href="/camping-corse-du-sud">
Dordogne
<a href="/dordogne">
Dordogne
<a href="/dordogne">
Côte d'Azur
<a href="/camping-cote-dazur">
Gironde
<a href="/gironde">
Gironde
<a href="/gironde">
Dordogne
<a href="/dordogne">
Ile de France
<a href="/ile-de-france">
Ile de France
<a href="/ile-de-france">
Gironde
<a href="/gironde">
Landes
<a href="/camping-landes">
Landes
<a href="/camping-landes">
Ile de France
<a href="/ile-de-france">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Normandie
<a href="/normandie">
Normandie
<a href="/normandie">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Pays-Basque
<a href="/pays-basque">
Pays-Basque
<a href="/pays-basque">
Normandie
<a href="/normandie">
Picardie
<a href="/camping-picardie">
Picardie
<a href="/camping-picardie">
Pays-Basque
<a href="/pays-basque">
Porto Vecchio
<a href="/porto-vecchio">
Porto Vecchio
<a href="/porto-vecchio">
Picardie
<a href="/camping-picardie">
PACA
<a href="/camping-paca">
Porto Vecchio
<a href="/porto-vecchio">
Var
<a href="/camping-var">
Var
<a href="/camping-var">
PACA
<a href="/camping-paca">
Vendée
<a href="/camping-en-vendee">
Vendée
<a href="/camping-en-vendee">
Var
<a href="/camping-var">
Barcelone
<a href="/barcelone">
Cantabrie
<a href="/camping-cantabrie">
Cantabrie
<a href="/camping-cantabrie">
Barcelone
<a href="/barcelone">
Costa Brava
<a href="/costa-brava">
Costa Brava
<a href="/costa-brava">
Cantabrie
<a href="/camping-cantabrie">
Costa Dorada
<a href="/camping-costa-dorada">
Costa Dorada
<a href="/camping-costa-dorada">
Costa Brava
<a href="/costa-brava">
Costa Blanca
<a href="/camping-costa-blanca">
Costa Blanca
<a href="/camping-costa-blanca">
Costa Dorada
<a href="/camping-costa-dorada">
Dalmatie
<a href="/camping-en-dalmatie">
Istrie
<a href="/camping-istrie">
Istrie
<a href="/camping-istrie">
Dalmatie
<a href="/camping-en-dalmatie">
Gorizia
<a href="/gorizia">
Emilie Romagne
<a href="/emilie-romagne">
Lac de garde
<a href="/lac-de-garde">
Lac de garde
<a href="/lac-de-garde">
Gorizia
<a href="/gorizia">
Latium
<a href="/latium">
Latium
<a href="/latium">
Lac de garde
<a href="/lac-de-garde">
Toscane
<a href="/toscane">
Toscane
<a href="/toscane">
Latium
<a href="/latium">
Sardaigne
<a href="/camping-en-sardaigne">
Sardaigne
<a href="/camping-en-sardaigne">
Toscane
<a href="/toscane">
Venise
<a href="/camping-venise">
Venise
<a href="/camping-venise">
Sardaigne
<a href="/camping-en-sardaigne">
Camping en Allemagne
<a href="/camping-allemagne">
Camping en Autriche
<a href="/camping-autriche">
Camping en Autriche
<a href="/camping-autriche">
Camping en Allemagne
<a href="/camping-allemagne">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping en Autriche
<a href="/camping-autriche">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping au Portugal
<a href="/camping-portugal">
Camping au Portugal
<a href="/camping-portugal">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping en Slovénie
<a href="/camping-slovenie">
Camping en Slovénie
<a href="/camping-slovenie">
Camping au Portugal
<a href="/camping-portugal">
Camping en Suisse
<a href="/camping-suisse">
Camping en Suisse
<a href="/camping-suisse">
Camping en Slovénie
<a href="/camping-slovenie">
Toutes nos thématiques
<a href="/toutes-nos-thematiques">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Toutes nos thématiques
<a href="/toutes-nos-thematiques">
Tous nos campings
<a href="/search">
Tous nos campings
<a href="/search">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Campings Early Booking
<a href="/early-booking-aout">
Campings Early Booking
<a href="/early-booking-aout">
Tous nos campings
<a href="/search">
Camping Black Friday
<a href="/camping-black-friday">
Camping Black Friday
<a href="/camping-black-friday">
Campings Early Booking
<a href="/early-booking-aout">
Vacances en Bungalow
<a href="/bungalow">
Vacances en Mobil-home
<a href="/hebergements">
Vacances en Mobil-home
<a href="/hebergements">
Vacances en Bungalow
<a href="/bungalow">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Vacances en Mobil-home
<a href="/hebergements">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Campings 5 étoiles
<a href="/camping-5-etoiles">
Campings 5 étoiles
<a href="/camping-5-etoiles">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Camping avec piscine
<a href="/camping-avec-piscine">
Camping piscine couverte
<a href="/camping-piscine-couverte">
Camping piscine couverte
<a href="/camping-piscine-couverte">
Camping avec piscine
<a href="/camping-avec-piscine">
Camping avec parc aquatique
<a href="/camping-parc-aquatique">
Camping avec parc aquatique
<a href="/camping-parc-aquatique">
Camping piscine couverte
<a href="/camping-piscine-couverte">
Camping bord de mer
<a href="/camping-pieds-dans-leau">
Camping bord de mer
<a href="/camping-pieds-dans-leau">
Camping avec parc aquatique
<a href="/camping-parc-aquatique">
Camping près de Disneyland Paris
<a href="/camping-disneyland-paris">
These items highlight common accessibility best practices.
ARIA
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
div#header-right > div#header-langues > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
div.digiConsentTitle > div.languageSelector > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
div.digiConsentTitle > div.languageSelector > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (23)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (28)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
Noibu
utility
Unload event listeners are deprecated and will be removed.
/collect.js:1:224530
(cdn.noibu.com)
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
Noibu
utility
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Bootstrap
5.3.2
jQuery
3.7.1
React
Moment.js
Moment Timezone
core-js
core-js-global@3.39.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
homair.com
1st party
Large JavaScript file is missing a source map
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (12)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 97.57% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
homair.com
1st party
footer p.footer-small-text
2.03%
11px
#nav #menu-langues-mobile .div-like-table-cell, #nav #menu-favorites-mobile .div-like-table-cell
0.24%
11px
.baseline-mobile h1, .baseline-mobile h2
0.14%
11px
.long-title .stars-wrapper .icon-star, .icon-xs .stars-wrapper .icon-star, .long-title .stars-wrapper .icon-wgt-star, .icon-xs .stars-wrapper .icon-wgt-star
0.02%
10px
sub, sup
0.00%
8.25px
Unattributable
Legible text
97.57%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/mobile/hv/images/2024-05/acheter-un-mobi…">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
body.home > div#_lm_pix > img
<img src="https://homair-1.leadsmonitor.io/pixel.gif?id=IS3TMDHY1AFLKG2J" width="1" height="1" border="0">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Showing results for URL: https://www.homair.com/
Run with original URL
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.3 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)4%75th Percentile - 1.3 sCore Web Vital
Interaction to Next Paint (INP)
280 ms
Page LoadsGood (≤ 200 ms)67%Needs Improvement (200 ms - 500 ms)18%Poor (> 500 ms)14%75th Percentile - 280 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)94%Needs Improvement (0.1 - 0.25)4%Poor (> 0.25)2%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.3 s
Page LoadsGood (≤ 1.8 s)85%Needs Improvement (1.8 s - 3 s)9%Poor (> 3 s)6%75th Percentile - 1.3 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)85%Needs Improvement (0.8 s - 1.8 s)12%Poor (> 1.8 s)3%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)88%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)5%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
177 ms
Page LoadsGood (≤ 200 ms)77%Needs Improvement (200 ms - 500 ms)12%Poor (> 500 ms)10%75th Percentile - 177 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)94%Needs Improvement (0.1 - 0.25)3%Poor (> 0.25)3%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.3 s
Page LoadsGood (≤ 1.8 s)84%Needs Improvement (1.8 s - 3 s)9%Poor (> 3 s)6%75th Percentile - 1.3 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)78%Needs Improvement (0.8 s - 1.8 s)15%Poor (> 1.8 s)7%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
74 FCP+9LCP+19TBT+15CLS+25SI+5 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.006
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 11, 2025, 8:00 AM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 491 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
homair.com
1st party
770 ms
234 ms
33 ms
497 ms
7 ms
7 ms
113 ms
90 ms
23 ms
97 ms
82 ms
1 ms
63 ms
55 ms
2 ms
Google Tag Manager
tag-manager
693 ms
622 ms
36 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
300 ms
287 ms
9 ms
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
168 ms
148 ms
12 ms
/gtag/js?id=…
(www.googletagmanager.com)
153 ms
122 ms
8 ms
/gtag/js?id=…
(www.googletagmanager.com)
72 ms
64 ms
7 ms
Noibu
utility
453 ms
120 ms
4 ms
/collect.js
(cdn.noibu.com)
453 ms
120 ms
4 ms
mcangelus.com
242 ms
183 ms
2 ms
…i/78a2d9a….js
(eudevil.mcangelus.com)
242 ms
183 ms
2 ms
Unattributable
149 ms
31 ms
0 ms
Unattributable
149 ms
31 ms
0 ms
AB Tasty
analytics
89 ms
81 ms
7 ms
89 ms
81 ms
7 ms
Minimize main-thread work 2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,441 ms
Other
458 ms
Style & Layout
341 ms
Rendering
165 ms
Script Parsing & Compilation
108 ms
Parse HTML & CSS
67 ms
Garbage Collection
42 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 290 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
735 KiB
254 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
127 KiB
98 ms
/gtag/js?id=…
(www.googletagmanager.com)
141 KiB
98 ms
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
159 KiB
37 ms
/gtag/js?id=…
(www.googletagmanager.com)
106 KiB
21 ms
/gtag/js?id=AW-103…
(www.googletagmanager.com)
106 KiB
0 ms
/gtag/destination?id=…
(www.googletagmanager.com)
94 KiB
0 ms
2 KiB
0 ms
Noibu
utility
79 KiB
26 ms
/collect.js
(cdn.noibu.com)
73 KiB
26 ms
/collect-worker.js
(cdn.noibu.com)
6 KiB
0 ms
AB Tasty
analytics
100 KiB
8 ms
74 KiB
8 ms
7 KiB
0 ms
/shared/me.0c0baf9….js
(try.abtasty.com)
4 KiB
0 ms
/84cc8d9…/initiator.js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
/84cc8d9….js
(try.abtasty.com)
2 KiB
0 ms
/84cc8d9…/manifest.json
(try.abtasty.com)
1 KiB
0 ms
1 KiB
0 ms
/v1/geoip?weather=false
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
/v1/ua-parser
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
0 KiB
0 ms
mcangelus.com
42 KiB
0 ms
…i/78a2d9a….js
(eudevil.mcangelus.com)
40 KiB
0 ms
/ct?id=…
(potter.mcangelus.com)
2 KiB
0 ms
/mon
(potter.mcangelus.com)
1 KiB
0 ms
/tracker/tc_imp.gif?e=37dfbd8…
(potter.mcangelus.com)
0 KiB
0 ms
Tealium
tag-manager
12 KiB
0 ms
11 KiB
0 ms
…2/i.gif
(collect.tealiumiq.com)
1 KiB
0 ms
leadsmonitor.io
2 KiB
0 ms
/lm.js
(homair-1.leadsmonitor.io)
1 KiB
0 ms
/pixel.gif?id=BLZMBXFJFCEZNI6K
(homair-1.leadsmonitor.io)
0 KiB
0 ms
Google/Doubleclick Ads
ad
0 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Largest Contentful Paint element 1,640 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
section#hp-carousel > div#hp-carousel-block > div#carousel-home > div.carousel-cell
<div class="carousel-cell cell-0" style="background-image: url(&quot;https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/…&quot;);">
Phase
% of LCP
Timing
TTFB
23%
380 ms
Load Delay
7%
110 ms
Load Time
4%
60 ms
Render Delay
67%
1,090 ms
Serve images in next-gen formats Potential savings of 86 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
homair.com
1st party
131.9 KiB
86.5 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-03/regionvedette-vendee-v…" alt="">
67.4 KiB
46.0 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/vignette-paques.jpg" alt="">
64.5 KiB
40.5 KiB
Properly size images Potential savings of 79 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
homair.com
1st party
159.7 KiB
79.1 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-03/regionvedette-vendee-v…" alt="">
67.4 KiB
33.4 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/vignette-paques.jpg" alt="">
64.5 KiB
32.0 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-01/nouveautes-2025-vignet…" alt="">
27.8 KiB
13.8 KiB
Eliminate render-blocking resources Potential savings of 260 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
homair.com
1st party
60.6 KiB
930 ms
/2.24.0/hv-main.css
(cdn.homair.com)
46.8 KiB
320 ms
/2.24.0/hv-home.css
(cdn.homair.com)
4.2 KiB
200 ms
4.4 KiB
200 ms
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
5.2 KiB
200 ms
Reduce unused JavaScript Potential savings of 567 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
726.6 KiB
350.6 KiB
/gtag/js?id=AW-103…
(www.googletagmanager.com)
105.0 KiB
81.4 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
157.9 KiB
58.5 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
92.4 KiB
58.0 KiB
/gtag/js?id=…
(www.googletagmanager.com)
140.1 KiB
55.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
105.0 KiB
51.8 KiB
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
126.1 KiB
45.8 KiB
homair.com
1st party
265.4 KiB
170.6 KiB
183.3 KiB
112.2 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
82.1 KiB
58.4 KiB
Noibu
utility
72.0 KiB
46.1 KiB
/collect.js
(cdn.noibu.com)
72.0 KiB
46.1 KiB
Efficiently encode images Potential savings of 39 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
URL
Resource Size
Potential Savings
homair.com
1st party
131.9 KiB
38.9 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-03/regionvedette-vendee-v…" alt="">
67.4 KiB
23.2 KiB
div#featured-slides-row > div.col-12 > a > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/vignette-paques.jpg" alt="">
64.5 KiB
15.7 KiB
Reduce unused CSS Potential savings of 43 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
homair.com
1st party
46.3 KiB
43.1 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
46.3 KiB
43.1 KiB
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
homair.com
1st party
div.track-promo > div.carousel-block > div.col-lg-6 > img
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/offre-printemps-hp.png" alt="" loading="eager" fetchpriority="high">
Camping Homair
<img class="logo-image tooltip-homair-logo tooltipstered" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg" alt="Camping Homair">
…HV/logo.svg
(cdn-2.homair.com)
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
…HV/logo.svg
(cdn-2.homair.com)
Catalogue Homair
<img src="https://cdn-2.homair.com/hopal_v2/hv/images/2025-01/mockup-catalogue-homai…" alt="Catalogue Homair">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
Unattributable
Homair Logo
<img alt="Homair Logo" src="" id="footer-logo" loading="lazy">
Serve static assets with an efficient cache policy 34 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
homair.com
1st party
1,018 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
None
83 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
None
47 KiB
/2.24.0/hv-main.js
(cdn.homair.com)
None
37 KiB
None
27 KiB
/2.24.0/hv-map.css
(cdn.homair.com)
None
6 KiB
None
5 KiB
None
4 KiB
/2.24.0/hv-home.css
(cdn.homair.com)
None
4 KiB
/2.24.0/hv-home.js
(cdn.homair.com)
None
1 KiB
/2.24.0/hv-widgets.js
(cdn.homair.com)
None
1 KiB
None
1 KiB
16d
440 KiB
16d
68 KiB
16d
65 KiB
16d
29 KiB
16d
28 KiB
16d
24 KiB
16d
24 KiB
16d
20 KiB
16d
19 KiB
16d
19 KiB
16d
18 KiB
/gfx/spritesheet.png
(cdn-2.homair.com)
16d
13 KiB
/gfx/mini-carto.jpg
(cdn-2.homair.com)
16d
11 KiB
16d
9 KiB
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
16d
5 KiB
16d
5 KiB
…HV/logo.svg
(cdn-2.homair.com)
16d
3 KiB
…4x3/fr.svg
(cdn-2.homair.com)
16d
1 KiB
Noibu
utility
73 KiB
/collect.js
(cdn.noibu.com)
30m
73 KiB
mcangelus.com
40 KiB
…i/78a2d9a….js
(eudevil.mcangelus.com)
12h
40 KiB
Tealium
tag-manager
11 KiB
5m
11 KiB
AB Tasty
analytics
2 KiB
/84cc8d9….js
(try.abtasty.com)
6h
2 KiB
leadsmonitor.io
1 KiB
/lm.js
(homair-1.leadsmonitor.io)
None
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
homair.com
1st party
50 ms
30 ms
20 ms
Avoid serving legacy JavaScript to modern browsers Potential savings of 21 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
leadsmonitor.io
7.8 KiB
/lm.js
(homair-1.leadsmonitor.io)
7.8 KiB
/lm.js:75:4
(homair-1.leadsmonitor.io)
Date.now
Google Tag Manager
tag-manager
7.4 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
7.4 KiB
/gtm.js?id=GTM-TVMQPKZ:13:1776
(www.googletagmanager.com)
Date.prototype.toJSON
homair.com
1st party
5.9 KiB
5.8 KiB
Object.keys
Object.values
@babel/plugin-transform-classes
/2.24.0/hv-vendors.js
(cdn.homair.com)
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
/2.24.0/hv-main.js
(cdn.homair.com)
0.0 KiB
@babel/plugin-transform-classes
Avoid an excessive DOM size 2,106 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
2,106
Maximum DOM Depth
Argelès-sur-Mer
<a href="/camping-argeles-sur-mer">
16
Maximum Child Elements
body.home
<body class="home lang-fr mobyletteLoaded">
44
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
504 ms
/gtag/js?id=…
(www.googletagmanager.com)
2,587 ms
148 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
2,735 ms
100 ms
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
1,857 ms
98 ms
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
1,955 ms
87 ms
/gtag/js?id=…
(www.googletagmanager.com)
2,909 ms
71 ms
homair.com
1st party
303 ms
3,105 ms
153 ms
2,980 ms
95 ms
536 ms
55 ms
AB Tasty
analytics
58 ms
2,851 ms
58 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Nos offres à ne pas manquer ! Profitez de réductions jusqu'à -25% sur vos vacan…
<div class="container" id="hp-slides-featured">
0.006
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,063.786 ms
Initial Navigation
…css/fontello.css?v=2.1.0
(cdn-2.homair.com)
- 26.065 ms, 19.76 KiB
- 22.397 ms, 28.28 KiB
/2.24.0/hv-main.css
(cdn.homair.com)
- 1,319.489 ms, 46.81 KiB
/2.24.0/hv-home.css
(cdn.homair.com)
- 1,056.741 ms, 4.22 KiB
- 1,041.995 ms, 4.45 KiB
/2.24.0/hv-map.css
(cdn.homair.com)
- 1,076.097 ms, 6.35 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 460 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
homair.com
1st party
460 ms
460 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 2,442 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
homair.com
1st party
928.4 KiB
439.8 KiB
221.6 KiB
184.4 KiB
/2.24.0/hv-vendors.js
(cdn.homair.com)
82.6 KiB
Google Tag Manager
tag-manager
733.1 KiB
/gtm.js?id=GTM-TVMQPKZ
(www.googletagmanager.com)
159.0 KiB
/gtag/js?id=…
(www.googletagmanager.com)
141.2 KiB
/gtm.js?id=GTM-KDFPWB3&l=ecgDataLayer
(www.googletagmanager.com)
127.2 KiB
/gtag/js?id=AW-103…
(www.googletagmanager.com)
106.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
106.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
93.5 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
section#hp-carousel > div#hp-carousel-block > div#carousel-home > div.carousel-cell
<div class="carousel-cell cell-0" style="background-image: url(&quot;https://cdn-2.homair.com/hopal_v2/hv/images/2025-02/…&quot;);">
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Failing Elements
div.container > div#header-right > div#header-buttons > button#helpDesk-tooltip
<button class="d-none d-sm-flex tooltipstered" id="helpDesk-tooltip" data-tooltip-content="#tooltip_helpdesk_content" onclick="window.open(&quot;https://contact.homair.com/hc/fr&quot;)">
div.container > div#header-right > div#header-buttons > button#phone-tooltip
<button class="d-none d-sm-flex tooltipstered" id="phone-tooltip" data-tooltip-content="#tooltip_content">
div.container > div#header-right > div#header-buttons > button.btn-favorites
<button class="btn-favorites tooltip-title d-none d-sm-flex tooltipstered" data-favoritelink="/search?favorites=1&amp;park_id=">
div.container > div#header-right > div#header-buttons > button#custarea-tooltip
<button class="btn-custarea tooltip-title tooltipstered" id="custarea-tooltip" data-tooltip-content="#tooltip_custarea_content" onclick="location.href=&quot;/espace-client&quot;">
div.container > div#header-right > div#header-buttons > button.basket-tooltip
<button class="basket-tooltip js-basket-count" data-tooltip-content="#tooltip_basket_content">
div.DateRangePicker > div > div.DateRangePickerInput > button.DateRangePickerInput_calendarIcon
<button class="DateRangePickerInput_calendarIcon DateRangePickerInput_calendarIcon_1" type="button">
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2024-05/acheter-un-mobil-home_…">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2021-02/parc-aquatique_0.jpg">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2024-12/experience-homair.jpg">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/images/2017-12/mobile-home.jpg">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
body.home > div#_lm_pix > img
<img src="https://homair-1.leadsmonitor.io/pixel.gif?id=BLZMBXFJFCEZNI6K" width="1" height="1" border="0">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
-28%
<span class="hvnew-pourcentage discount-28">
273€*
<span class="hvnew-price">
La Grande Métairie France - Bretagne - Carnac du 12/04 au 19/04 -28%
<div class="hvnew-bloc-camping clearfix">
-25%
<span class="hvnew-pourcentage discount-25">
462€*
<span class="hvnew-price">
La Pinède France - Charente Maritime - Les Mathes du 12/04 au 19/04 -25%
<div class="hvnew-bloc-camping clearfix">
-25%
<span class="hvnew-pourcentage discount-25">
441€*
<span class="hvnew-price">
Le Domaine des Naïades France - Provence Côte d'Azur - Port Grimaud du 12/04 au…
<div class="hvnew-bloc-camping clearfix">
-26%
<span class="hvnew-pourcentage discount-26">
238€*
<span class="hvnew-price">
Les Dunes France - Languedoc Roussillon - Torreilles du 12/04 au 19/04 -26%
<div class="hvnew-bloc-camping clearfix">
RECEVEZ TOUS NOS BONS PLANS !
<div class="title pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Inscrivez-vous à notre newsletter et recevez nos ventes flash et promos en avan…
<div>
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Votre adresse de messagerie est uniquement utilisée pour vous envoyer les newsl…
<div class="complement">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
En savoir plus sur la gestion de vos données et vos droits
<button data-type="iframe" data-src="https://www.homair.com/charte-de-protection-des-donnees-personnelles?forma…" class="alinkstyle popinIframe" style="color: #ffffff; text-decoration: underline;">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
notre centre d'aide
<button class="alinkstyle" onclick="window.open('https://contact.homair.com/hc/fr', '_blank');" style="color: #ffffff; text-decoration: underline;">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
LE CATALOGUE 2025
<div class="pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
Feuilleter les pages, se projeter, s'inspirer... Et si vous consultiez notre ca…
<p>
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
SUIVEZ-NOUS SUR :
<div class="pre-footer-title">
RECEVEZ TOUS NOS BONS PLANS ! Inscrivez-vous à notre newsletter et recevez nos …
<section id="pre-footer">
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪
<span>
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪
<div class="digiConsentTitle">
CONTINUER SANS ACCEPTER
<div class="digiConsentButtons rejectAll" id="digiconsentbanddecline">
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪 Les cookies nous permettent de vo…
<div id="digiConsentWelcome" style="display: flex;">
PARAMÉTRER MES COOKIES
<div class="digiConsentButtons" id="digiconsentbandparam">
GESTION DE VOS PRÉFÉRENCES SUR LES COOKIES 🍪 Les cookies nous permettent de vo…
<div id="digiConsentWelcome" style="display: flex;">
ACCEPTER ET CONTINUER
<div class="digiConsentButtons acceptAll" id="digiconsentbandaccept">
These are opportunities to improve the legibility of your content.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Alsace
<a href="/camping-alsace">
Annecy
<a href="/camping-annecy">
Annecy
<a href="/camping-annecy">
Alsace
<a href="/camping-alsace">
Arcachon
<a href="/arcachon">
Arcachon
<a href="/arcachon">
Annecy
<a href="/camping-annecy">
Ardèche
<a href="/ardeche">
Ardèche
<a href="/ardeche">
Arcachon
<a href="/arcachon">
Ardennes
<a href="/ardennes">
Ardennes
<a href="/ardennes">
Ardèche
<a href="/ardeche">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Ardennes
<a href="/ardennes">
Aveyron
<a href="/camping-aveyron">
Aveyron
<a href="/camping-aveyron">
Argelès sur Mer
<a href="/camping-argeles-sur-mer">
Bretagne
<a href="/bretagne">
Bretagne
<a href="/bretagne">
Aveyron
<a href="/camping-aveyron">
Cap d'Agde
<a href="/camping-cap-dagde">
Cap d'Agde
<a href="/camping-cap-dagde">
Bretagne
<a href="/bretagne">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Cap d'Agde
<a href="/camping-cap-dagde">
Charente Maritime
<a href="/charente-maritime">
Charente Maritime
<a href="/charente-maritime">
Centre Val de Loire
<a href="/camping-centre-val-de-loire">
Corse
<a href="/camping-corse">
Charente Maritime
<a href="/charente-maritime">
Corse du Sud
<a href="/camping-corse-du-sud">
Corse du Sud
<a href="/camping-corse-du-sud">
Côte d'Azur
<a href="/camping-cote-dazur">
Côte d'Azur
<a href="/camping-cote-dazur">
Corse du Sud
<a href="/camping-corse-du-sud">
Dordogne
<a href="/dordogne">
Dordogne
<a href="/dordogne">
Côte d'Azur
<a href="/camping-cote-dazur">
Gironde
<a href="/gironde">
Gironde
<a href="/gironde">
Dordogne
<a href="/dordogne">
Ile de France
<a href="/ile-de-france">
Ile de France
<a href="/ile-de-france">
Gironde
<a href="/gironde">
Landes
<a href="/camping-landes">
Landes
<a href="/camping-landes">
Ile de France
<a href="/ile-de-france">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Languedoc Roussillon
<a href="/camping-languedoc-roussillon">
Normandie
<a href="/normandie">
Normandie
<a href="/normandie">
Nord Pas de Calais
<a href="/camping-nord-pas-de-calais">
Pays-Basque
<a href="/pays-basque">
Pays-Basque
<a href="/pays-basque">
Normandie
<a href="/normandie">
Picardie
<a href="/camping-picardie">
Picardie
<a href="/camping-picardie">
Pays-Basque
<a href="/pays-basque">
Porto Vecchio
<a href="/porto-vecchio">
Porto Vecchio
<a href="/porto-vecchio">
Picardie
<a href="/camping-picardie">
PACA
<a href="/camping-paca">
Porto Vecchio
<a href="/porto-vecchio">
Var
<a href="/camping-var">
Var
<a href="/camping-var">
PACA
<a href="/camping-paca">
Vendée
<a href="/camping-en-vendee">
Vendée
<a href="/camping-en-vendee">
Var
<a href="/camping-var">
Barcelone
<a href="/barcelone">
Cantabrie
<a href="/camping-cantabrie">
Cantabrie
<a href="/camping-cantabrie">
Barcelone
<a href="/barcelone">
Costa Brava
<a href="/costa-brava">
Costa Brava
<a href="/costa-brava">
Cantabrie
<a href="/camping-cantabrie">
Costa Dorada
<a href="/camping-costa-dorada">
Costa Dorada
<a href="/camping-costa-dorada">
Costa Brava
<a href="/costa-brava">
Costa Blanca
<a href="/camping-costa-blanca">
Costa Blanca
<a href="/camping-costa-blanca">
Costa Dorada
<a href="/camping-costa-dorada">
Dalmatie
<a href="/camping-en-dalmatie">
Istrie
<a href="/camping-istrie">
Istrie
<a href="/camping-istrie">
Dalmatie
<a href="/camping-en-dalmatie">
Gorizia
<a href="/gorizia">
Emilie Romagne
<a href="/emilie-romagne">
Lac de garde
<a href="/lac-de-garde">
Lac de garde
<a href="/lac-de-garde">
Gorizia
<a href="/gorizia">
Latium
<a href="/latium">
Latium
<a href="/latium">
Lac de garde
<a href="/lac-de-garde">
Toscane
<a href="/toscane">
Toscane
<a href="/toscane">
Latium
<a href="/latium">
Sardaigne
<a href="/camping-en-sardaigne">
Sardaigne
<a href="/camping-en-sardaigne">
Toscane
<a href="/toscane">
Venise
<a href="/camping-venise">
Venise
<a href="/camping-venise">
Sardaigne
<a href="/camping-en-sardaigne">
Camping en Allemagne
<a href="/camping-allemagne">
Camping en Autriche
<a href="/camping-autriche">
Camping en Autriche
<a href="/camping-autriche">
Camping en Allemagne
<a href="/camping-allemagne">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping en Autriche
<a href="/camping-autriche">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping au Luxembourg
<a href="/camping-luxembourg">
Camping au Portugal
<a href="/camping-portugal">
Camping au Portugal
<a href="/camping-portugal">
Camping aux Pays Bas
<a href="/camping-pays-bas">
Camping en Slovénie
<a href="/camping-slovenie">
Camping en Slovénie
<a href="/camping-slovenie">
Camping au Portugal
<a href="/camping-portugal">
Camping en Suisse
<a href="/camping-suisse">
Camping en Suisse
<a href="/camping-suisse">
Camping en Slovénie
<a href="/camping-slovenie">
Toutes nos thématiques
<a href="/toutes-nos-thematiques">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Toutes nos thématiques
<a href="/toutes-nos-thematiques">
Tous nos campings
<a href="/search">
Tous nos campings
<a href="/search">
Toutes nos destinations
<a href="/toutes-nos-destinations">
Campings Early Booking
<a href="/early-booking-aout">
Campings Early Booking
<a href="/early-booking-aout">
Tous nos campings
<a href="/search">
Camping Black Friday
<a href="/camping-black-friday">
Camping Black Friday
<a href="/camping-black-friday">
Campings Early Booking
<a href="/early-booking-aout">
Vacances en Bungalow
<a href="/bungalow">
Vacances en Mobil-home
<a href="/hebergements">
Vacances en Mobil-home
<a href="/hebergements">
Vacances en Bungalow
<a href="/bungalow">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Vacances en Mobil-home
<a href="/hebergements">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Campings 3 étoiles
<a href="/camping-3-etoiles">
Campings 5 étoiles
<a href="/camping-5-etoiles">
Campings 5 étoiles
<a href="/camping-5-etoiles">
Campings 4 étoiles
<a href="/camping-4-etoiles">
Camping avec piscine
<a href="/camping-avec-piscine">
Camping piscine couverte
<a href="/camping-piscine-couverte">
Camping piscine couverte
<a href="/camping-piscine-couverte">
Camping avec piscine
<a href="/camping-avec-piscine">
Camping avec parc aquatique
<a href="/camping-parc-aquatique">
Camping bord de mer
<a href="/camping-pieds-dans-leau">
Camping avec parc aquatique
<a href="/camping-parc-aquatique">
Camping près de Disneyland Paris
<a href="/camping-disneyland-paris">
These items highlight common accessibility best practices.
ARIA
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
div#header-right > div#header-langues > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
div.digiConsentTitle > div.languageSelector > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
div.digiConsentTitle > div.languageSelector > div.dropdown > a#dropdownMenuLink
<a class="dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-bs-toggle="dropdown" aria-expanded="false">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (23)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (28)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
Noibu
utility
Unload event listeners are deprecated and will be removed.
/collect.js:1:224530
(cdn.noibu.com)
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
Noibu
utility
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
/collect.js:1:132693
(cdn.noibu.com)
WebSocket connection to 'wss://input.noibu.com/pv_part' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Bootstrap
5.3.2
jQuery
3.7.1
React
Moment.js
Moment Timezone
core-js
core-js-global@3.39.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
homair.com
1st party
Large JavaScript file is missing a source map
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (3)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2024-05/acheter-un-mobil-home_…">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2021-02/parc-aquatique_0.jpg">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/hv/images/2024-12/experience-homair.jpg">
a.hvnew-bloc-link > div.hvnew-bloc-inter-thema > div.imgPlaceholder > img.hvnew-thema-image
<img class="hvnew-thema-image lazy" data-src="https://cdn-2.homair.com/hopal_v2/images/2017-12/mobile-home.jpg">
div.footer-block-zone > div.footer-content > a.avisVerifies > img
<img src="https://cdn-2.homair.com/gfx/verified-reviews/verified-review-fr.png">
div#digiconsentpopinwrapper > div#digiConsentWelcome > div.digiConsentLogo > img.logo-image
<img class="logo-image" src="https://cdn-2.homair.com/gfx/logos/HV/logo.svg">
body.home > div#_lm_pix > img
<img src="https://homair-1.leadsmonitor.io/pixel.gif?id=BLZMBXFJFCEZNI6K" width="1" height="1" border="0">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.