5 sec in total
571 ms
4.3 sec
195 ms
Click here to check amazing Weimar content for Germany. Otherwise, check out these important facts you probably never knew about weimar.de
Willkommen in der Kulturstadt Weimar: Informationen zur Stadt, Sehenswürdigkeiten, offizielle Tourist-Information, Rathaus und Wirtschaft.
Visit weimar.deWe analyzed Weimar.de page load time and found that the first response time was 571 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
weimar.de performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.9 s
80/100
25%
Value5.0 s
63/100
10%
Value490 ms
58/100
30%
Value1.133
1/100
15%
Value4.7 s
80/100
10%
571 ms
353 ms
102 ms
202 ms
306 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 88% of them (52 requests) were addressed to the original Weimar.de, 10% (6 requests) were made to Ads.weimar-gmbh.com and 2% (1 request) were made to Stats.weimar-gmbh.com. The less responsive or slowest element that took the longest time to load (879 ms) belongs to the original domain Weimar.de.
Page size can be reduced by 570.9 kB (42%)
1.3 MB
773.2 kB
In fact, the total size of Weimar.de main page is 1.3 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. Images take 701.2 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 30.2 kB or 80% of the original size.
Potential reduce by 76.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, Weimar needs image optimization as it can save up to 76.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 292.0 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 292.0 kB or 72% of the original size.
Potential reduce by 172.4 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. Weimar.de needs all CSS files to be minified and compressed as it can save up to 172.4 kB or 87% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weimar. 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 9 to 1 for CSS and as a result speed up the page load time.
www.weimar.de
571 ms
353 ms
stylesheet_00a48be499.css
102 ms
colorbox.css
202 ms
style.css
306 ms
color.css
298 ms
mobile.css
312 ms
tx_eventcal.css
316 ms
jquery-1.7.x-1.8.x-1.2.x.js
621 ms
jquery.anythingslider-1.9.0.min.js
316 ms
global.js
393 ms
tinynav.min.js
395 ms
jquery-ui-1.8.18.custom.css
402 ms
styles.css
406 ms
scripts.js
490 ms
jquery.colorbox-1.5.13.min.js
493 ms
javascript_e5ee3d85bb.js
502 ms
piwik.js
862 ms
de.png
101 ms
gb.png
107 ms
fr.png
104 ms
nl.png
102 ms
jp.png
104 ms
search.png
99 ms
startseite_header_01.png
879 ms
logo.png
200 ms
logo_print.png
201 ms
tab_normal.png
201 ms
tab_normal.png
203 ms
tab_normal.png
207 ms
tab_normal.png
298 ms
nav_sub_li_normal.png
300 ms
csm_weimarerer-reden_140a83d672.jpg
503 ms
csm_Laut-und-draussen_-Foto-Candy-Welz_-Antenne-Th%C3%BCringen-_2__d1a38a3847.jpg
507 ms
csm_bachwochen_1e6df11e10.jpg
416 ms
content_bg.png
398 ms
csm_Wappen_L%C3%B6we_2cbd886df4.jpg
400 ms
csm_refugees_IMG_0320_cut_2_msi_4022dd5596.jpg
499 ms
csm_logo-bib_msi_40a23beb04.jpg
501 ms
links_extern.png
522 ms
csm_Rathauskurier_01_a4f8c8e0bb.jpg
604 ms
kalender_05.jpg
602 ms
stadtkarte3.jpg
607 ms
links_pdf.png
631 ms
csm_Amt6087neu_13bfecd0aa.jpg
703 ms
csm_geschenke_msi_8e05668739.jpg
707 ms
WFL_banner_500x180.png
708 ms
footer.png
850 ms
facebook+twitter_footer_-_rathaus.png
875 ms
facebook+twitter_footer_-_tourismus.png
803 ms
ajs.php
677 ms
lg.php
162 ms
ajs.php
319 ms
print.css
98 ms
lg.php
158 ms
ajs.php
300 ms
lg.php
159 ms
slider_arrows.png
97 ms
overlay.png
109 ms
weimar.de 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
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.
weimar.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
weimar.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 Weimar.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 Weimar.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.
weimar.de
Open Graph description is not detected on the main page of Weimar. 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: