2.8 sec in total
315 ms
2.4 sec
174 ms
Visit openstreetmap.com now to see the best up-to-date Open Street Map content and also check out these interesting facts you probably never knew about openstreetmap.com
OpenStreetMap is the free wiki world map.
Visit openstreetmap.comWe analyzed Openstreetmap.com page load time and found that the first response time was 315 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
openstreetmap.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.8 s
30/100
25%
Value4.3 s
75/100
10%
Value570 ms
52/100
30%
Value0
100/100
15%
Value5.0 s
77/100
10%
315 ms
375 ms
641 ms
232 ms
156 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Openstreetmap.com, 25% (14 requests) were made to A.tile.openstreetmap.org and 24% (13 requests) were made to Openstreetmap.org. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source Openstreetmap.org.
Page size can be reduced by 2.6 MB (69%)
3.8 MB
1.2 MB
In fact, the total size of Openstreetmap.com main page is 3.8 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. 35% of websites need less resources to load. Javascripts take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 24.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 24.6 kB or 80% of the original size.
Potential reduce by 15.3 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. Open Street Map images are well optimized though.
Potential reduce by 2.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 2.5 MB or 79% of the original size.
Potential reduce by 57.0 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. Openstreetmap.com needs all CSS files to be minified and compressed as it can save up to 57.0 kB or 73% of the original size.
Number of requests can be reduced by 10 (19%)
53
43
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Street Map. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
openstreetmap.com
315 ms
www.openstreetmap.org
375 ms
application-a58621c5b74a846b2cabb87c4908cb58e05f5cc2f02b3bc5611f3ec2d7139186.js
641 ms
screen-ltr-c682071f163f889b8d9a51c4a30cab7f48598d2a21cd32e0ae0e8734f508bc57.css
232 ms
leaflet-all-6a764748ecb320fb225ae17114fe6a580c88369a0440e02bdac32ac203febdea.css
156 ms
index-0ff88cb0bed6e8ac66180e4de2908d0a132fbba204d82c269592d7633c506c08.js
234 ms
piwik.js
329 ms
10.png
343 ms
10.png
341 ms
9.png
431 ms
11.png
470 ms
10.png
389 ms
10.png
470 ms
8.png
391 ms
12.png
470 ms
9.png
549 ms
11.png
470 ms
8.png
471 ms
12.png
550 ms
9.png
555 ms
11.png
558 ms
8.png
554 ms
12.png
553 ms
9.png
290 ms
11.png
221 ms
11.png
292 ms
12.png
293 ms
8.png
219 ms
8.png
381 ms
10.png
380 ms
9.png
370 ms
12.png
376 ms
10.png
376 ms
9.png
378 ms
12.png
533 ms
11.png
290 ms
9.png
209 ms
9.png
290 ms
8.png
215 ms
10.png
208 ms
12.png
291 ms
12.png
373 ms
11.png
376 ms
8.png
372 ms
10.png
450 ms
11.png
374 ms
8.png
375 ms
osm_logo-0e19527a1cc9fdf566c217d6e1863d88cac7bb743914792dea5d8db813501ad6.png
79 ms
menu-icon-ba3407aa1c5ff7b2153008abeb7f8789165716ecc0195a606d4569d0e8e0b716.png
81 ms
directions-cdf916d315f444a4f1d51a46d2293f28dc13cbda1fac640da8968735e69b28ff.png
80 ms
marker-green-a9c0b29cb063cce2ad2e158dc81d3ba69e192f83e6d99d8fbdce51f510333c69.png
81 ms
marker-red-642ccf845d55fc3aff154f0d0d7664fe3a9842b5f32a9858df1e1c827641499f.png
156 ms
searching-b66184be88a18bc2147e414ab67bde941db2507a69d455439a09d5280a8bdb63.gif
161 ms
sprite-c994382b12586b415ff33689e361207178da827a1cf164baa50d4dc7d75f66fc.svg
156 ms
print-ltr-f0e982d0ba074e914962563e26dfc48b3d2d9a05e5442932889cec8769cd2eaf.css
78 ms
openstreetmap.com 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
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
openstreetmap.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
openstreetmap.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 uses legible font sizes
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openstreetmap.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 Openstreetmap.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
openstreetmap.com
Open Graph data is detected on the main page of Open Street Map. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: