5.4 sec in total
275 ms
4.8 sec
318 ms
Visit openrailwaymap.org now to see the best up-to-date Open Railway Map content for Germany and also check out these interesting facts you probably never knew about openrailwaymap.org
OpenRailwayMap - An OpenStreetMap-based project for creating a map of the world's railway infrastructure.
Visit openrailwaymap.orgWe analyzed Openrailwaymap.org page load time and found that the first response time was 275 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
openrailwaymap.org performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value8.8 s
1/100
25%
Value8.3 s
19/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
275 ms
361 ms
262 ms
269 ms
523 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 13% of them (22 requests) were addressed to the original Openrailwaymap.org, 14% (24 requests) were made to C.tiles.openrailwaymap.org and 14% (24 requests) were made to C.tile.openstreetmap.org. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source B.tile.openstreetmap.org.
Page size can be reduced by 11.0 MB (73%)
15.0 MB
4.0 MB
In fact, the total size of Openrailwaymap.org main page is 15.0 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. 70% of websites need less resources to load. HTML takes 12.3 MB which makes up the majority of the site volume.
Potential reduce by 10.5 MB
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 10.5 MB or 85% of the original size.
Potential reduce by 356.0 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. Obviously, Open Railway Map needs image optimization as it can save up to 356.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 151.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 151.6 kB or 71% of the original size.
Potential reduce by 35.1 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. Openrailwaymap.org needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 74% of the original size.
Number of requests can be reduced by 18 (11%)
168
150
The browser has sent 168 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Railway Map. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
openrailwaymap.org
275 ms
www.openrailwaymap.org
361 ms
map.css
262 ms
leaflet.css
269 ms
leaflet-0.6.2.js
523 ms
L.TileLayer.Grayscale.js
270 ms
jstranslations.php
271 ms
search.js
274 ms
startposition.js
438 ms
timestamp.js
485 ms
functions.js
445 ms
bitmap-map.js
447 ms
piwik.js
402 ms
load.js
17 ms
btn_donate_LG.gif
105 ms
pixel.gif
75 ms
ad.png
180 ms
locate.png
204 ms
loader.js
37 ms
259 ms
cloudflare.min.js
8 ms
button.css
785 ms
button.js
666 ms
layers.png
179 ms
2.png
451 ms
1.png
310 ms
2.png
413 ms
2.png
1194 ms
1.png
773 ms
2.png
827 ms
ippos.php
182 ms
timestamp.php
181 ms
1.png
807 ms
3.png
808 ms
0.png
812 ms
1.png
812 ms
3.png
811 ms
4.png
1183 ms
0.png
1182 ms
4.png
1183 ms
2.png
1211 ms
2.png
1186 ms
2.png
805 ms
3.png
811 ms
2.png
809 ms
4.png
810 ms
0.png
809 ms
3.png
1176 ms
0.png
1181 ms
1.png
1185 ms
1.png
1181 ms
4.png
1185 ms
4.png
1182 ms
1.png
340 ms
3.png
341 ms
0.png
343 ms
1.png
344 ms
3.png
344 ms
4.png
558 ms
0.png
561 ms
4.png
527 ms
2.png
616 ms
2.png
528 ms
3.png
1177 ms
1.png
806 ms
0.png
806 ms
2.png
804 ms
1.png
805 ms
4.png
1181 ms
4.png
1181 ms
3.png
1181 ms
3.png
1180 ms
0.png
1180 ms
0.png
1195 ms
3.png
295 ms
1.png
304 ms
0.png
302 ms
2.png
304 ms
1.png
306 ms
4.png
477 ms
4.png
491 ms
3.png
573 ms
3.png
492 ms
0.png
526 ms
0.png
599 ms
2.png
277 ms
3.png
293 ms
2.png
299 ms
4.png
299 ms
0.png
302 ms
3.png
455 ms
0.png
493 ms
1.png
513 ms
1.png
519 ms
4.png
520 ms
4.png
489 ms
marker-icon.png
193 ms
marker-shadow.png
193 ms
legend-generator.php
191 ms
390.png
1029 ms
391.png
1033 ms
392.png
1033 ms
391.png
1035 ms
393.png
1036 ms
389.png
1068 ms
392.png
1051 ms
389.png
1053 ms
390.png
1053 ms
390.png
1055 ms
393.png
1061 ms
393.png
1072 ms
391.png
1051 ms
392.png
1030 ms
390.png
1032 ms
389.png
1032 ms
391.png
1034 ms
390.png
1035 ms
393.png
1051 ms
393.png
1053 ms
392.png
1053 ms
392.png
1060 ms
389.png
1059 ms
389.png
1069 ms
390.png
415 ms
391.png
518 ms
392.png
522 ms
391.png
1007 ms
393.png
553 ms
389.png
623 ms
392.png
623 ms
389.png
1001 ms
390.png
1006 ms
390.png
1033 ms
393.png
1016 ms
393.png
1037 ms
391.png
1032 ms
390.png
1031 ms
392.png
1030 ms
389.png
1028 ms
390.png
1028 ms
392.png
1047 ms
393.png
1054 ms
389.png
2102 ms
393.png
1053 ms
391.png
1055 ms
391.png
1055 ms
391.png
468 ms
390.png
474 ms
392.png
479 ms
389.png
976 ms
390.png
613 ms
392.png
617 ms
393.png
988 ms
389.png
988 ms
393.png
992 ms
391.png
1011 ms
391.png
1011 ms
391.png
531 ms
392.png
477 ms
390.png
612 ms
389.png
503 ms
391.png
511 ms
390.png
620 ms
393.png
990 ms
393.png
989 ms
392.png
993 ms
392.png
998 ms
389.png
1003 ms
389.png
1012 ms
legend-generator.php
186 ms
legend.css
185 ms
openrailwaymap.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
openrailwaymap.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
openrailwaymap.org 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
Image elements do not have [alt] attributes
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openrailwaymap.org 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 Openrailwaymap.org 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.
openrailwaymap.org
Open Graph description is not detected on the main page of Open Railway Map. 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: