38 sec in total
348 ms
9.6 sec
28.1 sec
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
Das B2B-Leadevent für Digitale Transformation. Entdecken Sie neueste Technologien und Lösungen zur Digitalisierung von Geschäftsprozessen.
Visit hub.berlinWe analyzed Hub.berlin page load time and found that the first response time was 348 ms and then it took 37.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
hub.berlin performance score
name
value
score
weighting
Value58.8 s
0/100
10%
Value90.7 s
0/100
25%
Value60.9 s
0/100
10%
Value7,110 ms
0/100
30%
Value0.001
100/100
15%
Value94.8 s
0/100
10%
348 ms
2373 ms
17 ms
416 ms
11 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hub.berlin, 49% (66 requests) were made to Cdn-api.swapcard.com and 28% (38 requests) were made to Transform.show. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Cdn-api.swapcard.com.
Page size can be reduced by 11.8 MB (40%)
29.7 MB
17.9 MB
In fact, the total size of Hub.berlin main page is 29.7 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. HTML takes 15.3 MB which makes up the majority of the site volume.
Potential reduce by 7.7 MB
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 5.1 MB, which is 33% 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 7.7 MB or 50% of the original size.
Potential reduce by 4.2 MB
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, Hub needs image optimization as it can save up to 4.2 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 207 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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.
Number of requests can be reduced by 20 (15%)
130
110
The browser has sent 130 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 16 to 1 for JavaScripts and as a result speed up the page load time.
hub.berlin
348 ms
transform.show
2373 ms
loader.js
17 ms
all.css
416 ms
bundle_legacy.js
11 ms
languages.json
223 ms
gtm.js
88 ms
transform_standard_rgb.svg
115 ms
search-pattern-left.png
224 ms
search-pattern-right.png
428 ms
navbar-pattern.png
429 ms
bue_0330-bearbeitet1.jpg
4477 ms
destination
88 ms
insight.min.js
25 ms
bat.js
59 ms
fbevents.js
16 ms
matomo.js
1002 ms
insight.beta.min.js
36 ms
5883911948323062
106 ms
97082278.js
55 ms
50 ms
de.json
149 ms
56 ms
1px.png
7 ms
translations-de.json
4 ms
78861abbbddb495592db78226693168a.jpeg
3221 ms
4032574c530d473dac61ae3952d3c9fd.png
3191 ms
site.js
257 ms
recaptcha-v2.js
253 ms
213b3322d2af40cc9f423f977fe13f91.jpeg
3211 ms
963bc85f06e54942acb673ca154f15ac.png
3980 ms
8a331cbf84c94df4b8a3f2dc36c1456c.jpeg
3780 ms
ae6c7fb8b1834d1d96489070c4424517.png
3921 ms
a9bc4aae8b41493994de03aaf7ffdfd2.png
3873 ms
3a7d3ff7a3ee42e2b4bc1e35370bb995.jpeg
3808 ms
4ef381debd1f42419c6d36cdf80b3098.jpeg
3787 ms
463a84d0aeef4680a053090bc4d268ae.png
3191 ms
97f7b2bb796243fca81611b7e3a27cad.jpeg
3191 ms
0cc490e6b2d24835bd28588460b49b75.png
3189 ms
8c46d2b406684f639886f802cb5978ec.png
3185 ms
fa0e8a9ad0274fdeacb8f5d0187c3c2a.png
3185 ms
903244b54dda417f8b8d5dd963acd9f6.jpeg
3557 ms
33c8066214024f40889f43b6ad338331.png
3552 ms
f33b6cb5127a412aa6286bbed88b2b09.png
3555 ms
2935ce2520304ddf9f90fe4abaa2dbab.png
3533 ms
744b71f6e90d455dbaa87873ba7fc88d.png
3553 ms
45bcead3521745989e5b17725c5081d3.jpeg
3545 ms
d7450b81e5564e3e9fff6526b8b81e8a.png
3920 ms
c70717559e734f2581742316d9603ee3.png
3920 ms
bb0eff88f104446d9747264299018145.png
3977 ms
3783940ac6134e159173959b88d9eb77.png
3919 ms
1c96ada522d745e4851e783d05098452.png
3920 ms
46f6d3dd985c4ae9a7e96b3d13e22621.png
3920 ms
f51b23b12b6947f6a1c1c6cb022f4682.png
4272 ms
8dc95c240c3c432491dc8bcce8c0a44a.png
4275 ms
c98e63275945492491cf1e486d4b2f3c.png
4277 ms
bc07b3d0308f4fc48b3a1dd3d7412e89.png
4014 ms
5767e50cd2ba43109a21106b74f525ba.png
4020 ms
e0de8690cb7b4fe9a3a2c337c61396c7.jpeg
4274 ms
0f5a4116fd6a443e8b55162ef20d7c9d.png
4382 ms
809557271f9349d9b3b0237dc6315d5a.png
4385 ms
e47dac062362406092a3434e525f6daf.png
4648 ms
b068afc963bb43e2b9f896f325c9ee8a.png
4674 ms
8850235e997e4d299fb847d9e03a857d.png
4631 ms
694ea0297e8b490d985b9d86f0a48629.png
4655 ms
457ab2d90a7e4a7f8a84014d699e9e91.png
4741 ms
8b7c95311fc94bfe9b9452cba62d90a3.png
4740 ms
6f5da01542454dda96f909ee300fc5aa.jpeg
4994 ms
fb1aa84e4fc14b198623c28a872bf5ec.png
4999 ms
e10100d267d84d37a2bac393b560d716.png
5019 ms
8852003a0c96481faf76ebc75eb485b5.png
5032 ms
speaker-slider-pattern.png
3182 ms
speaker-slider-pattern-m.png
3182 ms
news_pattern.png
3182 ms
comment-pattern-m.png
3185 ms
comment-pattern.png
3188 ms
314ec719022786418392f5c2c366aea9.jpg
3389 ms
294115ffc1e87eaf69b3fd8ad82b8238.jpg
3488 ms
c2af6298d87ce32db16e667a527b50d7.jpg
3385 ms
f412cc581f729b28facc063c7d8f78c5.jpg
3283 ms
301af4c3a491b98a9ae82b25a3651f3e.jpg
3379 ms
9b3d3d9fbb72d35fac6d058f583d0698.jpg
3282 ms
expo_icon.svg
3383 ms
lernen_icon.svg
3387 ms
buehnen_icon.svg
3478 ms
netzwerk_icon.svg
3483 ms
fiverr-logo.png
3485 ms
vodafone_stiftung.png
3589 ms
fapro_deconomy.png
3489 ms
tagesspiegel.png
3676 ms
startup_insider-primary.png
3585 ms
prinz.png
3587 ms
logo_tip_large_retina.png
3590 ms
footer-pattern.png
3797 ms
footer-pattern-m.png
3912 ms
bitkom.svg
3689 ms
matomo.php
3089 ms
configs.php
3114 ms
TheSansC4s_Bold.otf
3741 ms
TheSansC4s_ExtraBold.otf
3741 ms
TheSansC4s_Plain.otf
3703 ms
petrol.svg
3577 ms
configs.php
2445 ms
uct
2392 ms
matomo.php
298 ms
61b0fcabc55440b4bdbba3c24f826808.png
1925 ms
155ddd8e0492487a985509f2652f2c97.png
1940 ms
c5de81cf6acf4208a3907993ba700bb8.png
2164 ms
085ebc2a8f8d4e419622b6622a4b0fde.png
2181 ms
f63cd256df2441a6a7a130e9c7a40970.png
2200 ms
a6c59d737734462d9c8dc2989897e2a4.png
2209 ms
143d4063a7c64d8f8fd54ff3a3c0a16c.jpeg
1924 ms
9f99f1b7ad4f4a5fa17a340c26907751.png
1932 ms
01050321629a441080f82d8aacf2d1ca.png
2151 ms
adefe4bd9cd849cdbf6b65219334e254.png
2171 ms
20e179da3a4345bb8d0b1d8be5c9cb3d.png
2209 ms
61f766c49e914adbab4c432f5de34f17.png
2212 ms
791ab5ad0278497b98bf7230bc9b0cb9.png
1892 ms
e5979115a3c64e5fac7595fc22b48f85.jpeg
1657 ms
eafba8568b6e405d8e847ecb1a94d8fa.png
2016 ms
996a124b27d34007a6109b471c24117b.png
2151 ms
b51d9ed8fac9434aaae009603d167f98.png
2104 ms
c5ca399c0f1d4fcba067f2f1b488a699.jpeg
2150 ms
4b9cef32c7c2439db978ab6a6dab614c.png
2113 ms
535a30cbebc7418489bca067a85d52e2.png
2154 ms
c1081daef3a9429c928f2f83d90fbf43.jpeg
1784 ms
a4e195b982224690935674165093eda3.png
2160 ms
478ef1c4ff594808b87ac932e79e3f27.png
2160 ms
5306605a4860440b96e057b908a2dd1a.png
2171 ms
cc94f70d471043d18f7375c6157b6f55.png
2092 ms
c6bccf4ee0714c798ae228f11b34b687.jpeg
2122 ms
d0b9a314ba4c40f5a8d5df1912628d14.jpeg
1914 ms
e1f9f6f6eeff49efa1b966f621afe3b5.png
2139 ms
48c717406358452887490ff28aefc058.png
1882 ms
22666a0222a244a08c1491d12d2328a4.png
2136 ms
hub.berlin accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
hub.berlin 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
![]()
N/A
![]()
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. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. 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: