5.4 sec in total
252 ms
4.9 sec
323 ms
Click here to check amazing France Topo content. Otherwise, check out these important facts you probably never knew about francetopo.fr
Carte topographique libre
Visit francetopo.frWe analyzed Francetopo.fr page load time and found that the first response time was 252 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
francetopo.fr performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value2.9 s
79/100
25%
Value3.3 s
90/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value2.9 s
96/100
10%
252 ms
25 ms
152 ms
155 ms
159 ms
Our browser made a total of 198 requests to load all elements on the main page. We found that 94% of them (186 requests) were addressed to the original Francetopo.fr, 2% (4 requests) were made to Pagead2.googlesyndication.com and 2% (3 requests) were made to 0. The less responsive or slowest element that took the longest time to load (899 ms) belongs to the original domain Francetopo.fr.
Page size can be reduced by 2.1 MB (43%)
4.9 MB
2.8 MB
In fact, the total size of Francetopo.fr main page is 4.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. 75% 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. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 233.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 233.8 kB or 87% of the original size.
Potential reduce by 112.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. France Topo images are well optimized though.
Potential reduce by 1.5 MB
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 1.5 MB or 73% of the original size.
Potential reduce by 268.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. Francetopo.fr needs all CSS files to be minified and compressed as it can save up to 268.8 kB or 88% of the original size.
Number of requests can be reduced by 138 (72%)
192
54
The browser has sent 192 CSS, Javascripts, AJAX and image requests in order to completely render the main page of France Topo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
francetopo.fr
252 ms
style.css
25 ms
polices.css
152 ms
interface.css
155 ms
sprites.css
159 ms
ext-all.css
235 ms
xtheme-carto-blanc.css
159 ms
ext-base.js
161 ms
ext-all.js
615 ms
GeoExt.js
310 ms
proj4js-compressed.js
307 ms
DisplayProjectionSelectorCombo.js
231 ms
GeoNamesSearchCombo.js
231 ms
Measure.js
307 ms
MeasureArea.js
307 ms
MeasureLength.js
309 ms
LoadingPanel.js
384 ms
adsbygoogle.js
7 ms
OpenLayers.js
247 ms
s.gif
885 ms
entete_MEDIUM.png
886 ms
bouton_right.png
882 ms
bouton_left.png
882 ms
banniere.png
886 ms
presentation.jpg
886 ms
logo_viacarto.png
883 ms
logo-partir-en-vtt.png
887 ms
champagne_limousines-thick-webfont.woff
880 ms
champagne_limousines-thickbold-webfont.woff
880 ms
champagne_limousines-thickitalic-webfont.woff
879 ms
ca-pub-9400106338137878.js
324 ms
sprite-legende.png
286 ms
sprite-icones.png
501 ms
piwik.js
231 ms
champagne_limousines-thickbolditalic-webfont.woff
229 ms
style.css
317 ms
tip-sprite.gif
204 ms
tip-anchor-sprite.gif
203 ms
left-right.png
206 ms
left-corners.png
205 ms
right-corners.png
232 ms
top-bottom.png
233 ms
IconeApropos.png
233 ms
tool-sprites.gif
238 ms
s-handle.gif
238 ms
e-handle.gif
310 ms
ne-handle.gif
312 ms
nw-handle.gif
311 ms
se-handle.gif
314 ms
sw-handle.gif
313 ms
white-top-bottom.gif
385 ms
mini-left.gif
386 ms
bg.gif
387 ms
btn.gif
388 ms
icone_pan.png
390 ms
icone_zoom_avant.png
391 ms
icone_zoom_arriere.png
462 ms
icone_zoom_selection.png
463 ms
icone_zoom_max.png
464 ms
text-bg.gif
465 ms
trigger.gif
467 ms
icone_previous_view.png
468 ms
icone_next_view.png
537 ms
icone_refresh.png
539 ms
grid-blue-split.gif
540 ms
IconeOutils.png
541 ms
IconeOpacity.png
543 ms
IconeGeolocalisation.png
545 ms
s.gif
200 ms
zrt_lookup.html
25 ms
show_ads_impl.js
47 ms
search-trigger.gif
534 ms
IconePermalien.png
520 ms
mq_logo.png
71 ms
ads
175 ms
IconeCoordonnees.png
424 ms
IconeTreePresentation.png
424 ms
light-hd.gif
427 ms
IconeTreeOverlays.png
426 ms
IconeRechercher.png
495 ms
osd.js
14 ms
ads
156 ms
IconeLegende.png
468 ms
IconeLicence.png
469 ms
loader-orange.gif
469 ms
tilecache.py
466 ms
tilecache.py
466 ms
tilecache.py
496 ms
tilecache.py
492 ms
tilecache.py
465 ms
tilecache.py
492 ms
tilecache.py
465 ms
tilecache.py
466 ms
tilecache.py
470 ms
tilecache.py
470 ms
tilecache.py
470 ms
tilecache.py
494 ms
tilecache.py
493 ms
tilecache.py
491 ms
tilecache.py
468 ms
tilecache.py
472 ms
tilecache.py
472 ms
tilecache.py
495 ms
tilecache.py
495 ms
tilecache.py
493 ms
tilecache.py
469 ms
tilecache.py
473 ms
tilecache.py
471 ms
tilecache.py
494 ms
tilecache.py
492 ms
tilecache.py
491 ms
tilecache.py
462 ms
tilecache.py
467 ms
tilecache.py
464 ms
tilecache.py
486 ms
tilecache.py
485 ms
tilecache.py
484 ms
tilecache.py
464 ms
tilecache.py
467 ms
tilecache.py
468 ms
tilecache.py
796 ms
tilecache.py
796 ms
tilecache.py
794 ms
tilecache.py
539 ms
tilecache.py
695 ms
tilecache.py
617 ms
tilecache.py
666 ms
tilecache.py
748 ms
tilecache.py
743 ms
tilecache.py
697 ms
tilecache.py
719 ms
tilecache.py
794 ms
tilecache.py
845 ms
tilecache.py
818 ms
tilecache.py
821 ms
tilecache.py
698 ms
tilecache.py
715 ms
tilecache.py
771 ms
tilecache.py
844 ms
tilecache.py
845 ms
tilecache.py
816 ms
tilecache.py
775 ms
tilecache.py
772 ms
tilecache.py
794 ms
tilecache.py
821 ms
tilecache.py
824 ms
tilecache.py
825 ms
tilecache.py
799 ms
tilecache.py
797 ms
tilecache.py
795 ms
tilecache.py
822 ms
tilecache.py
899 ms
tilecache.py
825 ms
tilecache.py
799 ms
tilecache.py
796 ms
tilecache.py
795 ms
tilecache.py
697 ms
tilecache.py
618 ms
tilecache.py
568 ms
tilecache.py
567 ms
tilecache.py
544 ms
tilecache.py
592 ms
tilecache.py
593 ms
tilecache.py
547 ms
tilecache.py
563 ms
tilecache.py
566 ms
tilecache.py
538 ms
tilecache.py
536 ms
tilecache.py
516 ms
tilecache.py
518 ms
tilecache.py
491 ms
tilecache.py
489 ms
tilecache.py
487 ms
tilecache.py
516 ms
tilecache.py
465 ms
tilecache.py
464 ms
tilecache.py
485 ms
tilecache.py
467 ms
tilecache.py
466 ms
tilecache.py
513 ms
tilecache.py
465 ms
tilecache.py
464 ms
tilecache.py
485 ms
tilecache.py
462 ms
tilecache.py
461 ms
tilecache.py
510 ms
tilecache.py
463 ms
tilecache.py
462 ms
tilecache.py
462 ms
tilecache.py
462 ms
IconeTreeLayer.png
463 ms
IconeTreeVierge.png
464 ms
IconeTreeOccsol.png
462 ms
s.gif
462 ms
IconeTreeHodographie.png
461 ms
IconeTreeIsohypses.png
461 ms
IconeTreeDessin.png
459 ms
IconeTreeGeodesie.png
460 ms
francetopo.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.
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
Image elements do not have [alt] attributes
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.
francetopo.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
francetopo.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Francetopo.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 Francetopo.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.
francetopo.fr
Open Graph description is not detected on the main page of France Topo. 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: