6.3 sec in total
430 ms
5.7 sec
115 ms
Welcome to stadtplan2.dresden.de homepage info - get ready to check Stadtplan 2 Dresden best content for Germany right away, or after learning these important things about stadtplan2.dresden.de
Visit stadtplan2.dresden.deWe analyzed Stadtplan2.dresden.de page load time and found that the first response time was 430 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
stadtplan2.dresden.de performance score
430 ms
156 ms
111 ms
1767 ms
1106 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 97% of them (98 requests) were addressed to the original Stadtplan2.dresden.de, 1% (1 request) were made to Tile1stadtplan.dresden.de and 1% (1 request) were made to Tile2stadtplan.dresden.de. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Stadtplan2.dresden.de.
Page size can be reduced by 644.8 kB (75%)
864.0 kB
219.2 kB
In fact, the total size of Stadtplan2.dresden.de main page is 864.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 539.4 kB which makes up the majority of the site volume.
Potential reduce by 499.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 499.8 kB or 93% of the original size.
Potential reduce by 20.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. Obviously, Stadtplan 2 Dresden needs image optimization as it can save up to 20.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 124.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. Stadtplan2.dresden.de needs all CSS files to be minified and compressed as it can save up to 124.8 kB or 84% of the original size.
Number of requests can be reduced by 61 (63%)
97
36
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stadtplan 2 Dresden. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
stadtplan2.dresden.de
430 ms
spdd.aspx
156 ms
stadtplan2.dresden.de
111 ms
spdd.aspx
1767 ms
jdh.ashx
1106 ms
res.ashx
462 ms
res.ashx
294 ms
res.ashx
405 ms
jdh.ashx
398 ms
jdh.ashx
419 ms
header.gif
509 ms
verlauf_splash.png
505 ms
preloader.gif
513 ms
splash_screen.jpg
526 ms
prototype.ashx
473 ms
core.ashx
628 ms
ms.ashx
525 ms
converter.ashx
528 ms
ASP.spdd_controls_mapcontainer_ascx,App_Web_cltnledl.ashx
543 ms
IDU.cardoMap3.Web.Controls.DefaultThemeTree,cardo.Map3Lib.ashx
580 ms
IDU.cardoMap3.Web.Controls.IndexSearch,cardo.Map3Lib.ashx
635 ms
ASP.spdd_controls_supplementedindexsearch_ascx,App_Web_cltnledl.ashx
638 ms
IDU.cardoMap3.Web.Controls.DefaultLayout,cardo.Map3Lib.ashx
650 ms
IDU.cardoMap3.Web.Controls.Legend,cardo.Map3Lib.ashx
687 ms
IDU.cardoMap3.Web.Controls.CoordTool,cardo.Map3Lib.ashx
733 ms
IDU.cardoMap3.Web.Controls.PermalinkControl,cardo.Map3Lib.ashx
743 ms
ASP.spdd_controls_districtoverview_ascx,App_Web_cltnledl.ashx
744 ms
ASP.spdd_controls_streetsearch_ascx,App_Web_cltnledl.ashx
757 ms
IDU.cardoMap3.Web.Controls.Print.PrintManagerControl,cardo.Map3Lib.ashx
793 ms
jdh.ashx
1115 ms
res.ashx
896 ms
res.ashx
896 ms
res.ashx
898 ms
res.ashx
897 ms
spdd.css
1046 ms
jdh.ashx
1267 ms
jdh.ashx
1045 ms
res.ashx
841 ms
res.ashx
900 ms
res.ashx
935 ms
res.ashx
850 ms
res.ashx
849 ms
res.ashx
953 ms
res.ashx
939 ms
res.ashx
901 ms
res.ashx
853 ms
res.ashx
849 ms
res.ashx
950 ms
res.ashx
994 ms
res.ashx
897 ms
res.ashx
901 ms
res.ashx
899 ms
res.ashx
887 ms
res.ashx
928 ms
res.ashx
883 ms
res.ashx
896 ms
res.ashx
894 ms
res.ashx
885 ms
res.ashx
852 ms
res.ashx
914 ms
ogcsl.ashx
1050 ms
ogcsl.ashx
1058 ms
ogcsl.ashx
1057 ms
Content.aspx
325 ms
bullet_arrow_light.gif
107 ms
advertisement.aspx
154 ms
button_arrow_right.gif
112 ms
verlauf_header.gif
110 ms
bullet_right_arrow_down.gif
106 ms
icon_close_white.gif
108 ms
res.ashx
161 ms
res.ashx
219 ms
res.ashx
223 ms
res.ashx
224 ms
res.ashx
220 ms
entry-expand-sprite.gif
216 ms
res.ashx
268 ms
checkbox_state0.gif
321 ms
checkbox_state0_dumb.gif
322 ms
bullet_arrow_light_left.gif
327 ms
res.ashx
328 ms
res.ashx
332 ms
res.ashx
375 ms
res.ashx
428 ms
res.ashx
429 ms
res.ashx
435 ms
res.ashx
436 ms
res.ashx
439 ms
res.ashx
482 ms
res.ashx
536 ms
webmap.aspx
395 ms
res.ashx
348 ms
res.ashx
350 ms
res.ashx
352 ms
res.ashx
396 ms
overview_map.gif
442 ms
res.ashx
457 ms
res.ashx
494 ms
res.ashx
497 ms
res.ashx
501 ms
webmap.aspx
356 ms
stadtplan2.dresden.de SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stadtplan2.dresden.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Stadtplan2.dresden.de 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.
stadtplan2.dresden.de
Open Graph description is not detected on the main page of Stadtplan 2 Dresden. 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: