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.
{{url}}
{{time}} 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.
{{og_description}}
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: