4.7 sec in total
614 ms
2.6 sec
1.5 sec
Visit metropole.paris.fr now to see the best up-to-date Metropole Paris content for France and also check out these interesting facts you probably never knew about metropole.paris.fr
Au 1er janvier 2016, Paris et les communes des départements de Seine-Saint-Denis, des Hauts-de-Seine et du Val-de-Marne ainsi qu'Argenteuil et les communes des Portes de l'Essonne se sont regr...
Visit metropole.paris.frWe analyzed Metropole.paris.fr page load time and found that the first response time was 614 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
metropole.paris.fr performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value30.8 s
0/100
25%
Value16.8 s
0/100
10%
Value18,980 ms
0/100
30%
Value0.07
96/100
15%
Value26.9 s
0/100
10%
614 ms
402 ms
256 ms
174 ms
178 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Metropole.paris.fr, 42% (14 requests) were made to Paris.fr and 24% (8 requests) were made to Api-site.paris.fr. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Api-site.paris.fr.
Page size can be reduced by 813.0 kB (42%)
1.9 MB
1.1 MB
In fact, the total size of Metropole.paris.fr main page is 1.9 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. 40% of websites need less resources to load. Javascripts take 933.6 kB which makes up the majority of the site volume.
Potential reduce by 37.6 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 37.6 kB or 69% of the original size.
Potential reduce by 56.2 kB
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. Metropole Paris images are well optimized though.
Potential reduce by 697.6 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 697.6 kB or 75% of the original size.
Potential reduce by 21.7 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. Metropole.paris.fr needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 80% of the original size.
Number of requests can be reduced by 13 (48%)
27
14
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Metropole Paris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
metropole.paris.fr
614 ms
metropole-192
402 ms
paris.css
256 ms
modernizr.custom.js
174 ms
vwr-paris.css
178 ms
jquery-2.1.4.min.js
4 ms
paris.js
515 ms
jquery.cookie.min.js
17 ms
jquery-ui.min.js
5 ms
jquery.ui.touch-punch-improved.js
182 ms
soundmanager2.js
323 ms
vwr.js
190 ms
jquery-ui.min.css
181 ms
css
23 ms
gtm.js
74 ms
71231
1047 ms
nef.svg
208 ms
paris.svg
299 ms
vox-icon.png
207 ms
mairie-de-paris.png
209 ms
78609
1104 ms
78165
990 ms
78984
922 ms
76925
928 ms
79189
791 ms
119178.jpg
962 ms
78990
1039 ms
Montserrat-Light-webfont.woff
274 ms
Montserrat-Regular-webfont.woff
238 ms
Montserrat-Bold-webfont.woff
239 ms
paris-icons.woff
274 ms
piwik.js
600 ms
print.css
180 ms
metropole.paris.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
<frame> or <iframe> elements do not have a title
metropole.paris.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
metropole.paris.fr SEO score
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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metropole.paris.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Metropole.paris.fr 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.
metropole.paris.fr
Open Graph description is not detected on the main page of Metropole Paris. 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: