7.3 sec in total
283 ms
6.6 sec
370 ms
Click here to check amazing M Mercure content for France. Otherwise, check out these important facts you probably never knew about m.mercure.com
Discover our 3 and 4-star Mercure hotels and get the best hotel rate for your trips, weekend breaks or events.
Visit m.mercure.comWe analyzed M.mercure.com page load time and found that the first response time was 283 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
m.mercure.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value31.1 s
0/100
25%
Value38.3 s
0/100
10%
Value39,410 ms
0/100
30%
Value0.073
96/100
15%
Value49.3 s
0/100
10%
283 ms
326 ms
264 ms
36 ms
31 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.mercure.com, 8% (4 requests) were made to Cdn.cookielaw.org and 4% (2 requests) were made to Radar.cedexis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Geolocation.onetrust.com.
Page size can be reduced by 343.3 kB (52%)
658.2 kB
314.9 kB
In fact, the total size of M.mercure.com main page is 658.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 314.2 kB which makes up the majority of the site volume.
Potential reduce by 207.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 207.8 kB or 87% of the original size.
Potential reduce by 878 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. M Mercure images are well optimized though.
Potential reduce by 102.9 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 102.9 kB or 33% of the original size.
Potential reduce by 31.8 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. M.mercure.com needs all CSS files to be minified and compressed as it can save up to 31.8 kB or 52% of the original size.
Number of requests can be reduced by 16 (52%)
31
15
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Mercure. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
mercure.accor.com
283 ms
index.jsp
326 ms
index.shtml
264 ms
index.shtml
36 ms
main.js
31 ms
otSDKStub.js
146 ms
styles.css
64 ms
index.css
76 ms
dfp.css
78 ms
main.js
890 ms
main.js
578 ms
jquery-min-cms.js
123 ms
booking-core_en.js
669 ms
booking-engine.js
122 ms
popins.js
670 ms
home.js
692 ms
jquery.cookie-2.1.2.js
693 ms
jquery.dfp.js
694 ms
dfp.js
720 ms
87c4fef0-8732-44e4-bee3-f4faa4ce5a9d.json
612 ms
px.gif
299 ms
ajax-loader.gif
330 ms
logo-mercure.png
329 ms
sprite.png
330 ms
footer-appstore.png
337 ms
footer-googleplay.png
337 ms
houschkaaltpro-bold.woff
72 ms
houschkaaltpro-extrabold.woff
71 ms
houschkaaltpro-bold-webfont.woff
83 ms
houschkaaltpro-demibold-webfont.woff
83 ms
houschkaaltpro-medium-webfont.woff
88 ms
houschkaaltpro-medium.woff
88 ms
lato-bold.woff
88 ms
lato-black.woff
202 ms
houschkaaltpro-medium.ttf
203 ms
lato-regular.woff
205 ms
lato-light.woff
204 ms
location
1943 ms
main.js
167 ms
houschkaaltpro-bold.ttf
145 ms
houschkaaltpro-extrabold.ttf
142 ms
otBannerSdk.js
116 ms
index.en.json
113 ms
en.json
362 ms
erm.en.htm.json
24 ms
getViewBeans.action
724 ms
radar.js
729 ms
autocomplete.en.json
472 ms
radar.js
22 ms
m.mercure.com accessibility score
ARIA
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.
Impact
Issue
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Names and labels
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.
Impact
Issue
Links do not have a discernible name
m.mercure.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
m.mercure.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.mercure.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that M.mercure.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
m.mercure.com
Open Graph data is detected on the main page of M Mercure. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: