5.3 sec in total
249 ms
4.6 sec
389 ms
Welcome to nanterre.fr homepage info - get ready to check Nanterre best content for France right away, or after learning these important things about nanterre.fr
Site officiel de la ville de Nanterre, retrouvez toutes vos démarches en lignes et toutes les actualités de la ville !
Visit nanterre.frWe analyzed Nanterre.fr page load time and found that the first response time was 249 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nanterre.fr performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value8.2 s
2/100
25%
Value11.7 s
4/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value24.7 s
0/100
10%
249 ms
461 ms
163 ms
163 ms
328 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 75% of them (105 requests) were addressed to the original Nanterre.fr, 11% (15 requests) were made to Nanterre.viewontv.com and 2% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Nanterre.fr.
Page size can be reduced by 898.7 kB (41%)
2.2 MB
1.3 MB
In fact, the total size of Nanterre.fr main page is 2.2 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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 111.9 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. This page needs HTML code to be minified as it can gain 36.3 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 111.9 kB or 79% of the original size.
Potential reduce by 54.9 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. Nanterre images are well optimized though.
Potential reduce by 518.0 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 518.0 kB or 68% of the original size.
Potential reduce by 213.9 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. Nanterre.fr needs all CSS files to be minified and compressed as it can save up to 213.9 kB or 86% of the original size.
Number of requests can be reduced by 91 (66%)
138
47
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanterre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
nanterre.fr
249 ms
www.nanterre.fr
461 ms
formCtrl.js
163 ms
formCtrl-fr.js
163 ms
jquery-1.5.2.min.js
328 ms
jquery-ui-1.8.15.custom.min.js
163 ms
jquery.colorbox-min.js
162 ms
jquery.ui.core.min.js
313 ms
jquery.ui.widget.min.js
321 ms
jquery.ui.datepicker.min.js
403 ms
jquery.ui.datepicker-fr.js
324 ms
core.js
325 ms
modernizr-custom.js
472 ms
html5polyfills.js
486 ms
jquery.modalbox-1.4.1-min.js
489 ms
message.js
435 ms
parent.js
441 ms
rs_exp_v1_fr_fr.js
83 ms
addthis_widget.js
10 ms
all.js
188 ms
widgets.js
7 ms
jquery.cookie.js
484 ms
menu.js
592 ms
actualite.js
592 ms
jquery.jqplugin.1.0.2.min.js
629 ms
jquery.bxSlider.js
718 ms
GAB_NANTERRE_default.css
805 ms
colorbox.css
640 ms
datepicker.css
721 ms
modalbox.css
718 ms
oct.js
4 ms
94 ms
closeCookieCNIL.png
138 ms
cadenas.png
182 ms
header.png
483 ms
logo.png
241 ms
searchSubmit.png
183 ms
menu.png
182 ms
menuNiv1Item.png
242 ms
home.png
322 ms
1852_928_menu_laville.jpg
403 ms
1861_963_menu_lamairie.jpg
403 ms
1862_037_menu_culture.jpg
480 ms
1863_101_menu_sports.jpg
483 ms
1864_163_menu_educationjeunesse.jpg
562 ms
1865_204_menu_solidaritesante.jpg
645 ms
1866_262_menu_cadredevie.jpg
644 ms
1867_290_menu_economieemploi.jpg
719 ms
1868_329_menu_democratiecitoyennete.jpg
720 ms
alerte_fermer.png
643 ms
ALaUnePause.png
721 ms
22657_807_P1050969.jpg
1044 ms
22771_138_beatbox.jpg
965 ms
22770_888_Travaux-ruePaulVCouturierDJ004.jpg
1086 ms
22689_767_TAUSSAT-plage.jpg
1120 ms
RSS.png
879 ms
22773_603_Capture-d-e-cran-2016-02-29-a-16.png
1445 ms
masque.png
1120 ms
23_240_passeport.png
1447 ms
24_354_famille2.png
1524 ms
25_444_droit.png
1565 ms
26_642_etatcivil.png
1279 ms
27_667_logement.png
1280 ms
28_701_sante.png
1439 ms
29_723_Urbanisme.png
1440 ms
31_764_Environnement.png
1600 ms
22442_030_UNE-NANTERRE-407OK.jpg
1838 ms
39_152_planinteractif.png
1674 ms
e_z5UDnv.html
208 ms
adsct
121 ms
adsct
71 ms
300lo.json
71 ms
xd_arbiter.php
128 ms
xd_arbiter.php
257 ms
asap-regular-webfont.woff
1635 ms
sh.7c7179124ea24ac6ba46caac.html
41 ms
asap-bold-webfont.woff
1669 ms
nanterre_inactif.png
1709 ms
logoBottom.png
1583 ms
facebook.png
1622 ms
twitter.png
1686 ms
jquery.min.js
27 ms
jquery.drag.js
162 ms
modernizr.js
164 ms
playerHD.js
176 ms
jquery.tipTip.minified.js
163 ms
style.css
176 ms
xtcore.js
1690 ms
cover.png
1603 ms
PRR_ALAUNE.png
1927 ms
skin.css
163 ms
tipTip.css
161 ms
paginationoff.png
1532 ms
fleche.png
1573 ms
commentaire.png
1604 ms
facebookActu.png
1603 ms
ga.js
30 ms
__utm.gif
12 ms
twitterActu.png
1527 ms
petiteFlecheN.png
1528 ms
bgLienPicto.png
1566 ms
separateurVideo.png
1527 ms
play.png
1605 ms
twitterOiseau.png
1608 ms
billeterie.png
1451 ms
evenementListe_coin.png
1405 ms
PRR_DEMARCHE.png
1442 ms
22197_455_fond-assises.jpg
1875 ms
telechargerPublication.png
1372 ms
voirToutePublication.png
1370 ms
PRR_PRATIQUE.png
1370 ms
annuaireRechercheInnerForm.png
1249 ms
formSubmitAnnuaire.png
1204 ms
blocMairie.png
1207 ms
blocMairieInner.png
1204 ms
blocMairieMaison.png
1243 ms
petiteFleche.png
1283 ms
bandeauBasPuce.png
1243 ms
overlay.png
1208 ms
loading_background.png
1122 ms
loading.gif
1169 ms
suivAgenda.png
1189 ms
precAgenda.png
1129 ms
close.png
1114 ms
ajax-loader.gif
1104 ms
btn-media-supprimer.png
1205 ms
paginationon.png
1198 ms
prevBreve.png
1125 ms
nextBreve.png
1123 ms
swfobject.js
10 ms
swfobject.js
10 ms
hit.xiti
321 ms
getVideo.json
250 ms
skin.js
163 ms
xiti.js
170 ms
poster.js
167 ms
ga.js
169 ms
tracker.js
168 ms
skin.js
162 ms
print.css
83 ms
nanterre.fr accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
nanterre.fr 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
nanterre.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Nanterre.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 Nanterre.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.
nanterre.fr
Open Graph description is not detected on the main page of Nanterre. 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: