5 sec in total
504 ms
3.8 sec
681 ms
Visit hub.berlin now to see the best up-to-date Hub content for Germany and also check out these interesting facts you probably never knew about hub.berlin
plug into the digital future
Visit hub.berlinWe analyzed Hub.berlin page load time and found that the first response time was 504 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 70% of websites can load faster. This domain responded with an error, which can significantly jeopardize Hub.berlin rating and web reputation
hub.berlin performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value13.5 s
0/100
25%
Value8.2 s
20/100
10%
Value830 ms
35/100
30%
Value0.134
80/100
15%
Value9.9 s
27/100
10%
504 ms
138 ms
111 ms
221 ms
335 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 48% of them (51 requests) were addressed to the original Hub.berlin, 41% (44 requests) were made to Img.youtube.com and 4% (4 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hub.berlin.
Page size can be reduced by 943.9 kB (30%)
3.1 MB
2.2 MB
In fact, the total size of Hub.berlin main page is 3.1 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 106.0 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. This page needs HTML code to be minified as it can gain 14.1 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 106.0 kB or 89% of the original size.
Potential reduce by 17.5 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. Hub images are well optimized though.
Potential reduce by 231.2 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 231.2 kB or 58% of the original size.
Potential reduce by 589.1 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. Hub.berlin needs all CSS files to be minified and compressed as it can save up to 589.1 kB or 90% of the original size.
Number of requests can be reduced by 29 (29%)
99
70
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
hub.berlin
504 ms
de
138 ms
css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css
111 ms
css_oFBikwymPfjM4wTbfjt367YKbLy_vSw7Gsjrg8BX8Aw.css
221 ms
css_0ukqCSNKUpiVtH3u__Oga4PfVPMzOtyrNlJjFlTrDuY.css
335 ms
css_Gp1bl1sD3hzd0g_AIOCTDE-gynsCLCepS0KIZfbfai0.css
660 ms
css_POQkvJiShsvVXBJAmF5pDix3Y1SC7QS4pHai2ip1q4w.css
335 ms
jquery.min.js
739 ms
jquery.once.js
326 ms
drupal.js
437 ms
admin_devel.js
433 ms
de_vgKTvS5C0_ywx0GLKN9AMfSph-bcGa-hgM-ch8NaMIk.js
434 ms
custom.js
434 ms
webform.js
747 ms
googleanalytics.js
541 ms
modernizr.js
541 ms
foundation.min.js
865 ms
custom.modernizr.js
842 ms
liga.js
842 ms
owl.carousel.min.js
893 ms
map.js
873 ms
bitkom.js
873 ms
bitkom-ajax.js
872 ms
js
94 ms
e.js
518 ms
oct.js
138 ms
news.jpg
868 ms
cebit.jpg
888 ms
play_ohne_button_0.png
1243 ms
logo_Schriftzug.png
543 ms
start5.jpg
1057 ms
shane_wall_0_0.jpg
195 ms
komma.png
551 ms
keyvisual_hub-conf-2016_original_1200x900px.jpg
640 ms
ken_goldberg.jpg.jpeg
550 ms
inno_pitch_3.jpg
674 ms
red_stage_1.jpg
731 ms
blue_stage.jpg
639 ms
start_up_area_1.jpg
638 ms
red_stage_3.jpg
855 ms
red_stage_2.jpg
855 ms
red_stage_4.jpg
855 ms
start_up_area_2.jpg
884 ms
inno_pitch_4.jpg
942 ms
inno_pitch_1.jpg
1175 ms
inno_pitch_2.jpg
1101 ms
black_stage_1.jpg
1100 ms
analytics.js
149 ms
TheSans_B4_500_.woff
1083 ms
bitkom-hub.woff
911 ms
TheSerif_700_.woff
1239 ms
TheSerif_400_.woff
1151 ms
bitkom-piktos.ttf
1033 ms
jquery-1.8.3.min.js
938 ms
802 ms
t.js
994 ms
collect
14 ms
adsct
395 ms
adsct
394 ms
sddefault.jpg
270 ms
owl.video.play.png
683 ms
sddefault.jpg
190 ms
sddefault.jpg
189 ms
sddefault.jpg
203 ms
sddefault.jpg
190 ms
sddefault.jpg
205 ms
sddefault.jpg
355 ms
sddefault.jpg
204 ms
sddefault.jpg
205 ms
sddefault.jpg
219 ms
sddefault.jpg
218 ms
sddefault.jpg
220 ms
sddefault.jpg
220 ms
sddefault.jpg
221 ms
sddefault.jpg
238 ms
sddefault.jpg
238 ms
sddefault.jpg
241 ms
sddefault.jpg
239 ms
sddefault.jpg
240 ms
sddefault.jpg
241 ms
sddefault.jpg
239 ms
sddefault.jpg
272 ms
sddefault.jpg
272 ms
sddefault.jpg
273 ms
sddefault.jpg
272 ms
sddefault.jpg
272 ms
sddefault.jpg
286 ms
sddefault.jpg
273 ms
sddefault.jpg
286 ms
sddefault.jpg
273 ms
sddefault.jpg
307 ms
sddefault.jpg
287 ms
sddefault.jpg
287 ms
sddefault.jpg
306 ms
sddefault.jpg
307 ms
sddefault.jpg
307 ms
sddefault.jpg
161 ms
sddefault.jpg
123 ms
sddefault.jpg
137 ms
sddefault.jpg
124 ms
sddefault.jpg
122 ms
sddefault.jpg
122 ms
sddefault.jpg
121 ms
sddefault.jpg
134 ms
cnt_js.php
134 ms
cntcc
141 ms
css_mfSuHYCS4oRokM_WzsuVK3qOWGgdJ_hSeM3G2cg6Fk8.css
110 ms
hub.berlin 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
Image elements do not have [alt] attributes
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.
hub.berlin 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
hub.berlin SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 doesn't use legible font sizes
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hub.berlin can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Hub.berlin 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.
hub.berlin
Open Graph data is detected on the main page of Hub. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: