3.4 sec in total
336 ms
2.9 sec
182 ms
Click here to check amazing Ensembl content for China. Otherwise, check out these important facts you probably never knew about ensembl.org
Visit ensembl.orgWe analyzed Ensembl.org page load time and found that the first response time was 336 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ensembl.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.6 s
34/100
25%
Value7.5 s
26/100
10%
Value230 ms
87/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
336 ms
105 ms
555 ms
712 ms
1094 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 15% of them (5 requests) were addressed to the original Ensembl.org, 26% (9 requests) were made to Static.ensembl.org and 15% (5 requests) were made to Ensembl.info. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.ensembl.org.
Page size can be reduced by 779.8 kB (39%)
2.0 MB
1.2 MB
In fact, the total size of Ensembl.org main page is 2.0 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. 40% of websites need less resources to load. Images take 884.6 kB which makes up the majority of the site volume.
Potential reduce by 41.8 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 41.8 kB or 79% of the original size.
Potential reduce by 17.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. Ensembl images are well optimized though.
Potential reduce by 544.6 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 544.6 kB or 69% of the original size.
Potential reduce by 176.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. Ensembl.org needs all CSS files to be minified and compressed as it can save up to 176.1 kB or 69% of the original size.
Number of requests can be reduced by 9 (28%)
32
23
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ensembl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.ensembl.org
336 ms
index.html
105 ms
c5d3e910a7d41271091f321670ff6255.css
555 ms
9e5fb866ea5d8e4b2a686605ac218e47.image.css
712 ms
c1abd10076e4fe935734f5770cb66318.js
1094 ms
8331e5348dbe9e115a00aea02c2ce595.js
789 ms
9b4333c48659ba022dc34458e46acb34.png
311 ms
a0986ee1fa08dd655721db906739ca57.jpg
524 ms
cdc31f372fd4b641fbf8e57fac742d42.png
203 ms
widgets.js
8 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
91 ms
analytics.js
79 ms
accounts_dropdown
205 ms
piwik2.js
157 ms
bx_loader.gif
87 ms
controls.png
88 ms
syndication
104 ms
490156138512396288
105 ms
linkid.js
10 ms
collect
14 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
CropperCapture577.png
468 ms
CropperCapture570.png
691 ms
Homo_sapiens.png
596 ms
Mus_musculus.png
649 ms
Homo_sapiens-e1438860291690.png
805 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
piwik.php
271 ms
c78866538728fa858fac76b5a3ce0424_normal.png
47 ms
mrr_caricature_normal.jpg
46 ms
f3440ef862fb192536702911df40825c_normal.png
49 ms
CcI4K0bW0AIy8z2.jpg:small
50 ms
CcFO2ZSW0AAx4qy.png:small
51 ms
jot
30 ms
ensembl.org 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
ensembl.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ensembl.org 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ensembl.org 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 Ensembl.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ensembl.org
Open Graph description is not detected on the main page of Ensembl. 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: