3.2 sec in total
345 ms
2.7 sec
206 ms
Visit fablab.berlin now to see the best up-to-date Fab Lab content for Germany and also check out these interesting facts you probably never knew about fablab.berlin
We bring open innovation to the world from Berlin.
Visit fablab.berlinWe analyzed Fablab.berlin page load time and found that the first response time was 345 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fablab.berlin performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value5.1 s
26/100
25%
Value4.3 s
76/100
10%
Value880 ms
32/100
30%
Value0.01
100/100
15%
Value5.3 s
73/100
10%
345 ms
184 ms
267 ms
269 ms
269 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 80% of them (44 requests) were addressed to the original Fablab.berlin, 7% (4 requests) were made to S.ytimg.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fablab.berlin.
Page size can be reduced by 1.1 MB (50%)
2.1 MB
1.1 MB
In fact, the total size of Fablab.berlin main page is 2.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. 65% of websites need less resources to load. Images take 737.9 kB which makes up the majority of the site volume.
Potential reduce by 67.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. 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 67.0 kB or 84% of the original size.
Potential reduce by 27.3 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. Fab Lab images are well optimized though.
Potential reduce by 477.1 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 477.1 kB or 66% of the original size.
Potential reduce by 492.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. Fablab.berlin needs all CSS files to be minified and compressed as it can save up to 492.1 kB or 85% of the original size.
Number of requests can be reduced by 38 (73%)
52
14
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fab Lab. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
345 ms
global.css
184 ms
highdpi.css
267 ms
responsive-tables.css
269 ms
uniform.default.css
269 ms
product_list.css
271 ms
blockcart.css
274 ms
blockcategories.css
296 ms
blockcurrencies.css
353 ms
blocklanguages.css
354 ms
blockcontact.css
356 ms
blocknewsletter.css
358 ms
blocksearch.css
360 ms
jquery.autocomplete.css
386 ms
blocktags.css
440 ms
blockuserinfo.css
440 ms
blockviewed.css
444 ms
editorial.css
444 ms
settings.css
449 ms
static-captions.css
476 ms
dynamic-captions.css
525 ms
front.css
526 ms
blocktopmenu.css
531 ms
superfish-modified.css
532 ms
fablabberlin-1413372635.jpg
564 ms
neu-logo.png
565 ms
9340272-1458042744.jpg
1138 ms
3130813-1440413224.jpg
872 ms
4563037-1441703081.jpg
884 ms
3465820-1440413254.jpg
886 ms
4160713-1440413237.jpg
712 ms
v_82_e60c0eafd0919dd20f7ee4ced7063d37.js
1024 ms
transparent.png
801 ms
search-white.png
346 ms
footer-bg.png
415 ms
fab-lab-icon.png
427 ms
alef-regular.woff
413 ms
fontawesome-webfont.woff
425 ms
analytics.js
98 ms
iframe_api
75 ms
loader.gif
125 ms
coloredbg.png
124 ms
large_left.png
124 ms
large_right.png
123 ms
small_left.png
124 ms
small_right.png
124 ms
ec.js
20 ms
www-widgetapi.js
116 ms
collect
51 ms
rFOilpyJjQc
60 ms
www-embed-player-vflfNyN_r.css
14 ms
www-embed-player.js
41 ms
base.js
57 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
63 ms
ad_status.js
98 ms
fablab.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
fablab.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
fablab.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fablab.berlin can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fablab.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.
fablab.berlin
Open Graph description is not detected on the main page of Fab Lab. 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: