3.6 sec in total
551 ms
2.7 sec
300 ms
Visit buehnewittenberg.de now to see the best up-to-date Buehne Wittenberg content and also check out these interesting facts you probably never knew about buehnewittenberg.de
Visit buehnewittenberg.deWe analyzed Buehnewittenberg.de page load time and found that the first response time was 551 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
buehnewittenberg.de performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.2 s
71/100
25%
Value4.7 s
69/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value3.2 s
94/100
10%
551 ms
119 ms
234 ms
346 ms
235 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 41% of them (24 requests) were addressed to the original Buehnewittenberg.de, 38% (22 requests) were made to Static.reservix.de and 19% (11 requests) were made to Reservix.de. The less responsive or slowest element that took the longest time to load (697 ms) relates to the external source Static.reservix.de.
Page size can be reduced by 509.2 kB (55%)
929.1 kB
419.9 kB
In fact, the total size of Buehnewittenberg.de main page is 929.1 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. 35% of websites need less resources to load. Javascripts take 519.8 kB which makes up the majority of the site volume.
Potential reduce by 6.5 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 6.5 kB or 76% of the original size.
Potential reduce by 23.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. Buehne Wittenberg images are well optimized though.
Potential reduce by 375.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 375.6 kB or 72% of the original size.
Potential reduce by 103.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. Buehnewittenberg.de needs all CSS files to be minified and compressed as it can save up to 103.8 kB or 82% of the original size.
Number of requests can be reduced by 30 (53%)
57
27
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buehne Wittenberg. 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 8 to 1 for CSS and as a result speed up the page load time.
buehnewittenberg.de
551 ms
mdcr.js
119 ms
style.css
234 ms
mootools.js
346 ms
Loop.js
235 ms
SlideShow.js
244 ms
functions.js
243 ms
login_check.php
442 ms
schatten.png
110 ms
top_back.jpg
216 ms
clearpixel.png
114 ms
3130001.jpg
337 ms
3135001.jpg
336 ms
3140001.jpg
336 ms
Kopie%20(2)%20von%20banner_hae_2013.gif
537 ms
Kopie%20(3)%20von%20banner_hae_2013.gif
439 ms
Kopie%20(4)%20von%20banner_hae_2013.gif
533 ms
Kopie%20von%20banner_hae_2013.gif
560 ms
banner_hae_2013.gif
555 ms
umenu.png
444 ms
shine.png
547 ms
schattenunten.png
559 ms
global.js
333 ms
jquery-1.11.0.min.js
427 ms
jquery-ui.structure.min.css
336 ms
jquery-ui.theme.css
336 ms
jquery-ui.rx.css
336 ms
jquery-ui-1.11.1.custom.min.js
614 ms
jquery.ui.datepicker-de.js
424 ms
responsiveslides.min.js
448 ms
slideshow.js
446 ms
jquery.plugins.js
448 ms
jquery.TextInInput.js
515 ms
customerlogin.js
516 ms
reset.css
518 ms
simple_tool.css
518 ms
simple_main.css
640 ms
portalPanel.js
606 ms
chosen.css
607 ms
chosen.jquery.min.js
639 ms
reservation_events.js
638 ms
bottomHelper.js
697 ms
setjs.php
114 ms
trusted-shops.gif
109 ms
pci-dss_big.png
180 ms
X84F256B263D795EF0E0AA13FE1C1801C.gif
604 ms
bg_submenu_site.png
254 ms
Logo_Simple_Layout.jpg
179 ms
msearch.gif
181 ms
mplan.gif
181 ms
icon-haus-w.gif
181 ms
bg_rubrik2.gif
252 ms
bg_eventkachel.jpg
250 ms
lang_flags.png
94 ms
ui-bg_flat_100_ecebe6_40x100.png
95 ms
bact.png
114 ms
binact.png
110 ms
loader.gif
111 ms
buehnewittenberg.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.
buehnewittenberg.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
buehnewittenberg.de SEO score
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buehnewittenberg.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 Buehnewittenberg.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.
buehnewittenberg.de
Open Graph description is not detected on the main page of Buehne Wittenberg. 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: