3.9 sec in total
676 ms
3 sec
170 ms
Click here to check amazing EggNOG Embl content for China. Otherwise, check out these important facts you probably never knew about eggnog.embl.de
Search for Cluster of Orthologous Groups (COG), pairwise orthology predictions, functional annotation and phylogenetic data for more than 2000 species.
Visit eggnog.embl.deWe analyzed Eggnog.embl.de page load time and found that the first response time was 676 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
eggnog.embl.de performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value13.6 s
0/100
25%
Value11.8 s
4/100
10%
Value340 ms
75/100
30%
Value0.027
100/100
15%
Value13.5 s
11/100
10%
676 ms
564 ms
96 ms
378 ms
278 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eggnog.embl.de, 60% (28 requests) were made to Eggnogdb.embl.de and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Eggnogdb.embl.de.
Page size can be reduced by 337.7 kB (54%)
630.4 kB
292.7 kB
In fact, the total size of Eggnog.embl.de main page is 630.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. CSS take 337.6 kB which makes up the majority of the site volume.
Potential reduce by 19.7 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 7.2 kB, which is 29% 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 19.7 kB or 79% of the original size.
Potential reduce by 3.1 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. EggNOG Embl images are well optimized though.
Potential reduce by 32.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 32.2 kB or 60% of the original size.
Potential reduce by 282.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. Eggnog.embl.de needs all CSS files to be minified and compressed as it can save up to 282.7 kB or 84% of the original size.
Number of requests can be reduced by 16 (43%)
37
21
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EggNOG 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 6 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
eggnog.embl.de
676 ms
eggnogdb.embl.de
564 ms
ga.js
96 ms
bootstrap.min.css
378 ms
animate.min.css
278 ms
font-awesome.min.css
287 ms
simple-line-icons.css
187 ms
font.css
187 ms
app.css
386 ms
eggnog.css
370 ms
css
70 ms
eggnogapp.min.js
1019 ms
analytics.js
7 ms
collect
11 ms
app.html
94 ms
home.html
98 ms
sourcesanspro.woff
285 ms
sourcesanspro-light.woff
284 ms
sourcesanspro-bold.woff
160 ms
hometabs.html
94 ms
header.html
123 ms
aside.html
118 ms
a2.jpg
127 ms
a3.jpg
190 ms
a1.jpg
190 ms
discover_eggnog.png
310 ms
separator_white_vertical.png
191 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
31 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
37 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
38 ms
fontawesome-webfont.woff
483 ms
widgets.js
35 ms
nav.html
131 ms
search_box.html
152 ms
eggnog_icon.png
186 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
21 ms
syndication
127 ms
568017002191937536
190 ms
virus.png
101 ms
proxy.jpg
35 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
9 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
11 ms
DH1g6SbC_normal.png
146 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
28 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
32 ms
proxy.jpg
10 ms
eggnog.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
eggnog.embl.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
eggnog.embl.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Eggnog.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 Eggnog.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.
eggnog.embl.de
Open Graph description is not detected on the main page of EggNOG 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: