8.1 sec in total
296 ms
7.3 sec
408 ms
Click here to check amazing Berlin Biennale content for United States. Otherwise, check out these important facts you probably never knew about berlinbiennale.de
Visit berlinbiennale.deWe analyzed Berlinbiennale.de page load time and found that the first response time was 296 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
berlinbiennale.de performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value58.9 s
0/100
25%
Value12.7 s
3/100
10%
Value2,210 ms
6/100
30%
Value0.158
73/100
15%
Value35.4 s
0/100
10%
296 ms
1854 ms
24 ms
191 ms
44 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Berlinbiennale.de, 80% (66 requests) were made to Bb9.berlinbiennale.de and 5% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Bb9.berlinbiennale.de.
Page size can be reduced by 2.9 MB (32%)
8.9 MB
6.1 MB
In fact, the total size of Berlinbiennale.de main page is 8.9 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. 65% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.8 kB or 83% 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. Berlin Biennale images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 75% of the original size.
Potential reduce by 1.4 MB
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. Berlinbiennale.de needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 90% of the original size.
Number of requests can be reduced by 58 (77%)
75
17
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berlin Biennale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
berlinbiennale.de
296 ms
bb9.berlinbiennale.de
1854 ms
css
24 ms
layerslider.css
191 ms
css
44 ms
style.css
197 ms
font-awesome.min.css
202 ms
style.min.css
199 ms
stylesheet.min.css
507 ms
style_dynamic.css
203 ms
responsive.css
290 ms
style_dynamic_responsive.css
294 ms
js_composer.css
708 ms
custom_css.css
297 ms
style.css
295 ms
widget-this-week-skeleton.min.css
388 ms
greensock.js
590 ms
jquery.js
595 ms
jquery-migrate.min.js
395 ms
layerslider.kreaturamedia.jquery.js
584 ms
layerslider.transitions.js
493 ms
snazzymaps.js
593 ms
widget-this-week.min.js
600 ms
wp-emoji-release.min.js
650 ms
qode-like.min.js
606 ms
plugins.js
1407 ms
jquery.carouFredSel-6.2.1.min.js
611 ms
lemmon-slider.min.js
616 ms
jquery.fullPage.min.js
699 ms
jquery.mousewheel.min.js
702 ms
jquery.touchSwipe.min.js
709 ms
isotope.pkgd.min.js
715 ms
js
76 ms
default_dynamic.js
715 ms
default.js
1003 ms
custom_js.js
801 ms
comment-reply.min.js
807 ms
js_composer_front.js
817 ms
masonry.pkgd.min.js
817 ms
imagesloaded.pkgd.min.js
900 ms
artist.js
904 ms
stage.js
819 ms
dis.js
814 ms
news.js
892 ms
countdown.min.js
894 ms
header.js
903 ms
wp-embed.min.js
814 ms
style.css
892 ms
fonts.css
897 ms
custom.css
898 ms
artist.css
816 ms
events.css
808 ms
nav.css
791 ms
news.css
761 ms
quote.css
709 ms
video.css
714 ms
footer.css
708 ms
bb9.gif
3617 ms
ga.js
59 ms
Logo_desktop_icon.png
117 ms
NHaasGroteskDSPro-45Lt.ttf
1114 ms
1px.png
116 ms
bb9_oculus_balcony-3ADK.jpg
3837 ms
IMG_9087-copy.jpg
2188 ms
KW.png
672 ms
KB.png
672 ms
156527635
103 ms
156565172
277 ms
NHaasGroteskDSPro-65Md.ttf
1259 ms
NHaasGroteskDSPro-26ThIt.ttf
1454 ms
NHaasGroteskDSPro-25Th.ttf
1525 ms
NHaasGroteskDSPro-35XLt.ttf
1647 ms
icons.ttf
1554 ms
__utm.gif
166 ms
player.js
574 ms
player.css
560 ms
ga.js
573 ms
vuid.min.js
572 ms
proxy.html
118 ms
11808261_60x60.jpg
121 ms
__utm.gif
67 ms
__utm.gif
36 ms
557614747.jpg
78 ms
berlinbiennale.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
berlinbiennale.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
berlinbiennale.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berlinbiennale.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Berlinbiennale.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.
berlinbiennale.de
Open Graph description is not detected on the main page of Berlin Biennale. 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: