6 sec in total
344 ms
4.3 sec
1.3 sec
Click here to check amazing Darmstadt content for Germany. Otherwise, check out these important facts you probably never knew about darmstadt.de
Visit darmstadt.deWe analyzed Darmstadt.de page load time and found that the first response time was 344 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
darmstadt.de performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value6.2 s
12/100
25%
Value9.0 s
15/100
10%
Value350 ms
73/100
30%
Value0.031
100/100
15%
Value14.8 s
8/100
10%
344 ms
987 ms
195 ms
294 ms
295 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 90% of them (74 requests) were addressed to the original Darmstadt.de, 7% (6 requests) were made to Wiga.t-online.de and 2% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Darmstadt.de.
Page size can be reduced by 591.5 kB (11%)
5.2 MB
4.6 MB
In fact, the total size of Darmstadt.de main page is 5.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. 80% 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 4.5 MB which makes up the majority of the site volume.
Potential reduce by 113.7 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 113.7 kB or 84% of the original size.
Potential reduce by 53.7 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. Darmstadt images are well optimized though.
Potential reduce by 205.7 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 205.7 kB or 76% of the original size.
Potential reduce by 218.5 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. Darmstadt.de needs all CSS files to be minified and compressed as it can save up to 218.5 kB or 86% of the original size.
Number of requests can be reduced by 32 (43%)
74
42
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Darmstadt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
darmstadt.de
344 ms
www.darmstadt.de
987 ms
stylesheet_4a21628c78.css
195 ms
flexslider.css
294 ms
magnific-popup.css
295 ms
bootstrap.css
396 ms
flexslider.css
295 ms
csc.css
297 ms
main.css
373 ms
jquery.min.js
63 ms
jquery-ui.min.js
84 ms
jquery.socialshareprivacy.min.js
390 ms
bootstrap.min.js
391 ms
default.css
388 ms
wetterboxen.css
950 ms
getWetterinfoTemplate.php
1087 ms
jquery.flexslider-min.js
634 ms
jquery.magnific-popup.min.js
665 ms
jquery.filter-isImageFile.min.js
666 ms
hoverIntent.js
667 ms
superfish.js
666 ms
StartJS.js
666 ms
jquery.ui.totop.js
667 ms
bjq-Slider.js
675 ms
jquery.flexslider-min.js
676 ms
jquery.datetimepicker.js
677 ms
parsley.min.js
678 ms
Tabs.js
676 ms
Form.js
678 ms
Marketing.js
861 ms
wetter_info.gif
440 ms
stadt.png
234 ms
contrastNegativ.png
232 ms
en.png
231 ms
Darmstadt_Logo.png
259 ms
clear.gif
243 ms
fb1.png
242 ms
twitter1.png
277 ms
rss1.png
259 ms
csm_wahl_kreuz_800x400_f855dc8ca0.jpg
402 ms
csm_parkende_autos_andreas_trapp_pixelio_800_400_4a73253847.jpg
1040 ms
csm_jugendehrung_2016_wissenschaftsstadt_darmstadt_800x400_b5a00dc2bc.jpg
1029 ms
csm_andre_schellenberg_800_400_e09ec2128c.jpg
998 ms
csm_merck_stadion_sv98_800x400_d1a5458152.jpg
1038 ms
csm_sanierung_toilettenanlagen_lgg_ida_800x400_effda833a5.jpg
998 ms
csm_sperrmuell_heike_irmen_pixelio_800x400_4cb8e10ec2.jpg
1040 ms
csm_luisenplatz_weltkugel_huebers_pixelio_800x400_911b883772.jpg
1027 ms
csm_rainer_sturm_800x400_1c44a952a5.jpg
1037 ms
csm_umweltdiplom_2016_800x400_c10f30764f.jpg
1037 ms
csm_oberbuergermeister_fenster_800x400_57de99e3e0.jpg
1041 ms
csm_luisenplatz_oez_800x400_e6011ace6f.jpg
1069 ms
csm_darmstadt_bleibt_weltoffen_800x500_e3e7f46d94.jpg
1040 ms
csm_Stadtlexikon_Partsch_6fe72b7133.jpg
1083 ms
csm_strassenschaeden_lichtkunst.73_pixelio_800_400_7a2e561c83.jpg
1115 ms
csm_kanalarbeiten_hartmut910_pixelio_800x500_857a68ed63.jpg
1058 ms
csm_mathildenhoehe_nikolaus_heiss_800x400_14aa1e91f8.jpg
1103 ms
csm_gesicht_zeigen_800x400_0ce519ce17.jpg
1067 ms
csm_wohnart_3_bauverein_800_400_60bc6ccd93.jpg
1106 ms
csm_IHK_Ausbildung_MATSE_Merckschule800x400_b22021c405.jpg
1195 ms
kerstin_briese_privat_800x400.jpg
1106 ms
justus_liebig_haus_oez_800x400.jpg
1112 ms
stadtlexikon.jpg
1187 ms
zukunftsstadt.jpg
1192 ms
kampagne_fluechtlinge.jpg
1202 ms
buergerbeteiligung.jpg
1203 ms
DINWeb.woff
1005 ms
DINWeb-Medium.woff
1071 ms
fontawesome-webfont.woff
1087 ms
DINWeb-Bold.woff
1086 ms
gadget_small.jpg
544 ms
iconSprite.png
616 ms
iconSprite_small.png
615 ms
socialshareprivacy.css
788 ms
de.lang
992 ms
index.php
927 ms
dummy_facebook.png
100 ms
dummy_twitter.png
98 ms
dummy_gplus.png
98 ms
flexslider-icon.woff
108 ms
flexslider-icon.woff
107 ms
socialshareprivacy_on_off.png
187 ms
socialshareprivacy_info.png
249 ms
darmstadt.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Form elements do not have associated labels
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.
darmstadt.de 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
Missing source maps for large first-party JavaScript
darmstadt.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Darmstadt.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Darmstadt.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.
darmstadt.de
Open Graph description is not detected on the main page of Darmstadt. 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: