5.3 sec in total
328 ms
4.5 sec
455 ms
Visit embl.de now to see the best up-to-date EMBL content for China and also check out these interesting facts you probably never knew about embl.de
EMBL's administrative headquarters in the Southern German city of Heidelberg hosts five research units and many of the laboratory's core facilities.
Visit embl.deWe analyzed Embl.de page load time and found that the first response time was 328 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
embl.de performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value6.0 s
13/100
25%
Value10.6 s
7/100
10%
Value10 ms
100/100
30%
Value0.063
97/100
15%
Value11.4 s
19/100
10%
328 ms
1803 ms
63 ms
236 ms
467 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 61% of them (40 requests) were addressed to the original Embl.de, 24% (16 requests) were made to and 8% (5 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Embl.de.
Page size can be reduced by 607.8 kB (14%)
4.3 MB
3.7 MB
In fact, the total size of Embl.de main page is 4.3 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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 36.4 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 32% 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 36.4 kB or 84% of the original size.
Potential reduce by 25.6 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. EMBL images are well optimized though.
Potential reduce by 80.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 80.2 kB or 58% of the original size.
Potential reduce by 465.7 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. Embl.de needs all CSS files to be minified and compressed as it can save up to 465.7 kB or 51% of the original size.
Number of requests can be reduced by 9 (21%)
43
34
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EMBL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
embl.de
328 ms
www.embl.de
1803 ms
a280603e-e48c-4c76-8c1d-05b1dc7496c3.css
63 ms
fonts.css
236 ms
embl.min.css
467 ms
modernizr.js
276 ms
327C29D349C0FA8EE.css
1623 ms
jquery.min.js
30 ms
embl.min.js
375 ms
lightbox-close.png
114 ms
loading.gif
187 ms
lightbox-prev.png
113 ms
lightbox-next.png
189 ms
embl_logo.png
365 ms
icon_menu.png
187 ms
icon_search_menu.png
187 ms
insync-slider.jpg
769 ms
S_S_conference_embl.jpg
1094 ms
phd_recruitment.jpg
1183 ms
EHT16-01.jpg
1555 ms
lll_conference_ebi.jpg
912 ms
rubic-slider1.jpg
1166 ms
PicR16feb16-ex.jpg
1135 ms
1602-heart-transcription-factors-ex.jpg
1094 ms
1602-self-organisation-ex.jpg
1277 ms
1602-tara-ex.jpg
1188 ms
Biogen_news_ex.jpg
1317 ms
1602-rubic-ex.jpg
1348 ms
unit1.jpg
1455 ms
unit2.jpg
1277 ms
unit3.jpg
1368 ms
unit4.jpg
1641 ms
unit5.jpg
1500 ms
icon_social_facebook_sprite.png
1439 ms
icon_social_twitter_sprite.png
1460 ms
icon_social_youtube_sprite.png
1530 ms
icon_social_plus_sprite.png
1545 ms
gtm.js
108 ms
arrow_dropdown_sprite.png
1546 ms
icon_search_sprite.png
1582 ms
arrow_right_small_sprite.png
1611 ms
arrow_left_big_sprite.png
1626 ms
arrow_right_big_sprite.png
1633 ms
arrow_right_small_sprite_blue.png
1633 ms
analytics.js
33 ms
c=
18 ms
lhD4w==
18 ms
+VQpE94RXBMoGLuZ7mjlkqNDew4NVjvyBiGkTJ4vHNVljF0taS5DBPYIzg80FRoP9Ou18BJzYzOu9ZJLyQf+PhJkT6lPS1nfHnT0yZPTz+Y8jcfMUPr
17 ms
8=
16 ms
QZQXEP3
15 ms
+WEPj
15 ms
4+EmRPqU9LWd8edPTJk9PP5jyNx8xQ+s=
15 ms
8=
14 ms
530dee22-e3c1-4e9f-bf62-c31d510d9656.woff
49 ms
bcf54343-d033-41ee-bbd7-2b77df3fe7ba.woff
82 ms
60be5c39-863e-40cb-9434-6ebafb62ab2b.woff
82 ms
50d35bbc-dfd4-48f1-af16-cf058f69421d.woff
103 ms
+VQZk94ZXBMoGLuZ7WllkqNLWw5NVhvyRjGkTJ4vHNRljH0jaS5jBPYITjc01RoP9Ou18BJzYzOu85JLyQf+fi0zJ7SHpczvrzpaZNnxx9M9RtgwUP7
13 ms
wjTLZjE98+xK6v9yKNInvCI4JlAx97PcUkulxga2nBqst2QMw0gZPN65KssYulrSXIYJ7BEcHmgqtJ9p12vgpGZG513rpBeSD3z8pEif0p6WM7686WmTp6cfTPkbDsxD5w==
12 ms
dD8w==
11 ms
A3t80Pf
10 ms
+VQZk94ZXBMoGLuZ7WllkqNLWw5NVhvyRjGkTJ4vHNRljH0jaS5jBPYITjc01RoP9Ou18BJzYzOu85JLyQf+fi0zJ7SHpczvrzpaZNnxx9M9RtgwUP7
9 ms
KRIn9KeljO+vOlpk6enH0z5Gw7MQ+c=
9 ms
M=
9 ms
e9LTJ09MPpvwN7fND3w==
9 ms
collect
24 ms
embl.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
embl.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
embl.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Embl.de 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 Embl.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.
embl.de
Open Graph description is not detected on the main page of EMBL. 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: