2.9 sec in total
562 ms
2 sec
265 ms
Click here to check amazing Bluebee content for Belgium. Otherwise, check out these important facts you probably never knew about bluebee.com
Delivering a streamlined way for users to analyze, explore, and manage large-scale genomics data in the cloud.
Visit bluebee.comWe analyzed Bluebee.com page load time and found that the first response time was 562 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
bluebee.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value29.5 s
0/100
25%
Value15.1 s
1/100
10%
Value2,860 ms
3/100
30%
Value0.098
90/100
15%
Value30.7 s
0/100
10%
562 ms
242 ms
401 ms
163 ms
244 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 94% of them (49 requests) were addressed to the original Bluebee.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (699 ms) belongs to the original domain Bluebee.com.
Page size can be reduced by 578.6 kB (46%)
1.3 MB
683.2 kB
In fact, the total size of Bluebee.com main page is 1.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. 45% of websites need less resources to load. Images take 523.1 kB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.7 kB or 81% of the original size.
Potential reduce by 30.0 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. Bluebee images are well optimized though.
Potential reduce by 340.3 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 340.3 kB or 69% of the original size.
Potential reduce by 165.5 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. Bluebee.com needs all CSS files to be minified and compressed as it can save up to 165.5 kB or 86% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bluebee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.bluebee.com
562 ms
wp-emoji-release.min.js
242 ms
style.css
401 ms
layout.css
163 ms
blue.css
244 ms
responsive.css
163 ms
formalize.css
223 ms
superfish.css
245 ms
prettyPhoto.css
325 ms
nonverblaster.css
302 ms
flexslider.css
320 ms
settings.css
479 ms
jquery.js
560 ms
jquery-migrate.min.js
381 ms
swfobject.js
404 ms
jquery.themepunch.tools.min.js
644 ms
jquery.themepunch.revolution.min.js
699 ms
css
21 ms
effect.min.js
344 ms
superfish.js
344 ms
jquery.jcarousellite.js
420 ms
jquery.fitvids.js
420 ms
jquery.isotope.min.js
443 ms
jquery.formalize.min.js
501 ms
nonverblaster.js
502 ms
app.js
502 ms
jquery.prettyPhoto.js
502 ms
jquery.flexslider.min.js
604 ms
comment-reply.min.js
604 ms
wp-embed.min.js
604 ms
to-top.png
274 ms
Bluebeelogo-webpage1.jpg
275 ms
www.bluebee.com
432 ms
16429223_xl-e1412927337927.jpg
279 ms
27055773_xxl-e1412927363448.jpg
277 ms
6119826_xxl-3-e1413284297280.jpg
276 ms
19706824_xxl1-e1412927260857.jpg
320 ms
icon-bar1.png
274 ms
icon-search1.png
320 ms
icons-cogs.png
326 ms
icons-sharesquare.png
324 ms
twitter.png
327 ms
facebook.png
398 ms
linkedin.png
399 ms
excerpt-icon.png
379 ms
divider1.png
380 ms
analytics.js
27 ms
loader.gif
137 ms
bullet.png
209 ms
large_left.png
210 ms
large_right.png
214 ms
collect
12 ms
bluebee.com 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
bluebee.com 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
bluebee.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bluebee.com 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 Bluebee.com 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.
bluebee.com
Open Graph description is not detected on the main page of Bluebee. 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: