11.3 sec in total
456 ms
9.9 sec
957 ms
Click here to check amazing Congres Auteuil content. Otherwise, check out these important facts you probably never knew about congres-auteuil.com
Restaurant traditionnel situé à la Porte d’Auteuil, à deux pas de Roland Garros, du Parc des Princes et des champs de courses d’Auteuil / Longchamp.
Visit congres-auteuil.comWe analyzed Congres-auteuil.com page load time and found that the first response time was 456 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
congres-auteuil.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.4 s
0/100
25%
Value10.8 s
6/100
10%
Value310 ms
78/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
456 ms
911 ms
96 ms
180 ms
259 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 54% of them (64 requests) were addressed to the original Congres-auteuil.com, 22% (26 requests) were made to Bookings.zenchef.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Bookings.zenchef.com.
Page size can be reduced by 841.8 kB (75%)
1.1 MB
285.7 kB
In fact, the total size of Congres-auteuil.com main page is 1.1 MB. 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 637.3 kB which makes up the majority of the site volume.
Potential reduce by 28.7 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 28.7 kB or 75% of the original size.
Potential reduce by 428.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 428.9 kB or 67% of the original size.
Potential reduce by 384.3 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. Congres-auteuil.com needs all CSS files to be minified and compressed as it can save up to 384.3 kB or 85% of the original size.
Number of requests can be reduced by 73 (73%)
100
27
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Congres Auteuil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
congres-auteuil.com
456 ms
911 ms
widgetkit-19579bbc.css
96 ms
modal.css
180 ms
rounded.css
259 ms
bootstrap.min.css
338 ms
bootstrap-responsive.min.css
261 ms
font-awesome.css
263 ms
mobile-menu.css
293 ms
template.css
269 ms
preset3.css
347 ms
custom.css
369 ms
cw-default.css
376 ms
cwsl_style.css
380 ms
settings.css
376 ms
captions.css
412 ms
template.css
420 ms
jquery.min.js
514 ms
jquery-noconflict.js
430 ms
jquery-migrate.min.js
428 ms
widgetkit-7407f92f.js
427 ms
mootools-core.js
647 ms
core.js
482 ms
mootools-more.js
783 ms
modal.js
639 ms
jquery-noconflict.js
637 ms
bootstrap.min.js
729 ms
modernizr-2.6.2.min.js
740 ms
helix.core.js
747 ms
menu.js
736 ms
easing.js
740 ms
init.js
742 ms
jquery.themepunch.plugins.min.js
752 ms
jquery.themepunch.revolution.min.js
1172 ms
bootstrap-extended.css
1132 ms
css
14 ms
lightbox.js
546 ms
mediaelement-and-player.js
537 ms
spotlight.js
538 ms
all.js
163 ms
fr.gif
384 ms
en.gif
384 ms
bg_header.png
716 ms
logo-header.png
382 ms
bg_drillmenu.png
513 ms
brasserie-paris-ambiance1.jpg
890 ms
brasserie-paris-ambiance2.jpg
737 ms
brasserie-paris-ambiance3.jpg
719 ms
logo-small.png
511 ms
bg_footer.png
1037 ms
cw_social_32.png
413 ms
mem8YaGs126MiZpBA-UFVZ0d.woff
259 ms
mem5YaGs126MiZpBA-UN_r8OUuhv.woff
264 ms
mem5YaGs126MiZpBA-UN7rgOUuhv.woff
264 ms
mem5YaGs126MiZpBA-UN8rsOUuhv.woff
254 ms
fontawesome-webfont.woff
592 ms
MuseoSlab.woff
666 ms
ga.js
336 ms
timer.png
420 ms
loader.gif
425 ms
all.js
110 ms
__utm.gif
137 ms
results
908 ms
css2
108 ms
163 ms
7a43941ca2ba5e870758eebe6c1ddfda666d5c0b_CSS.0dc4c429.chunk.css
104 ms
styles.0e06bd10.chunk.css
293 ms
polyfills-d38ffb8ec6b605acb21b.js
453 ms
results.js
303 ms
_app.js
478 ms
webpack-4b7ad33d4898e1bb0b74.js
290 ms
framework.4503cc20512dbab0b6d3.js
477 ms
8313d723.1b025c93df65efdc1694.js
476 ms
924c863fbfb54bb9d26b68cc812884a3fb89434f.f37777566327fe6b8cf4.js
475 ms
d96f6499a73ef812ce70631a65576b74b7bb9a1f.1b1eaff76641a616da2a.js
687 ms
67fa3ea728ee8b3cbd8d64587c93f14fab58a149.777f72af46085d507d1c.js
707 ms
2f4b4fc2accfbd03c11468262ea14b5126b10b42.faeb0156728421f73b71.js
710 ms
d1e04e3a198cfe21cf48569f0587fa3d455b8ba4.8ac552cd166f28158507.js
704 ms
7a43941ca2ba5e870758eebe6c1ddfda666d5c0b.b39f132c720f6b556f1c.js
714 ms
7a43941ca2ba5e870758eebe6c1ddfda666d5c0b_CSS.8d20fa8ceffc8a76b073.js
701 ms
cfd2c4cfcd8c079df701b3bb2ec8b35e5dd11475.8051e0be67a38623908f.js
715 ms
1b7d706c863035fdeae6dfadb7f10040fe731565.9e1b70903ca2475bb028.js
780 ms
styles.1f8442f47fad8de99d11.js
743 ms
main-3f81788ad59cf254780a.js
775 ms
_buildManifest.js
777 ms
_ssgManifest.js
778 ms
logo_zenchef_200px.png
380 ms
80a4ed4719ed2aa65879060f8926fb91.png
492 ms
KFOlCnqEu92Fr1MmEU9vAA.woff
252 ms
KFOmCnqEu92Fr1Me5g.woff
255 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
255 ms
8ef67ec0529b9e739dd58f5fb8629a08.ttf
1865 ms
3279d94bef4a77aea46dc044d80b157f.ttf
1829 ms
m-outer-7e4b9b871fee876475cf1d5d316fe456.html
213 ms
m-outer-1e6b80c19bc40eb0f8d834532a510a68.js
1591 ms
translation.json
512 ms
analytics.js
343 ms
getAvailabilities
1397 ms
inner.html
519 ms
collect
426 ms
sessions.bugsnag.com
418 ms
horaires_auteuil.jpg
1116 ms
collect
127 ms
like.php
159 ms
bg_n.png
263 ms
bg_ne.png
261 ms
bg_e.png
273 ms
bg_se.png
291 ms
bg_s.png
294 ms
bg_sw.png
344 ms
bg_w.png
345 ms
bg_nw.png
355 ms
spinner.gif
383 ms
closebox.png
384 ms
wo9QQu7xzcO.js
56 ms
OqOE21UvWe3.png
44 ms
cavalry_endpoint.php
84 ms
4
136 ms
congres-auteuil.com accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
congres-auteuil.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
congres-auteuil.com SEO score
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 uses legible font sizes
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Congres-auteuil.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Congres-auteuil.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.
congres-auteuil.com
Open Graph description is not detected on the main page of Congres Auteuil. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: