773 ms in total
47 ms
641 ms
85 ms
Visit assemblathon.org now to see the best up-to-date Assemblathon content and also check out these interesting facts you probably never knew about assemblathon.org
An offshoot of the Genome 10K project, and primarily organized by the UC Davis Genome Center, Assemblathons are contests to assess state-of-the-art methods in the field of genome assembly....
Visit assemblathon.orgWe analyzed Assemblathon.org page load time and found that the first response time was 47 ms and then it took 726 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
assemblathon.org performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value4.3 s
42/100
25%
Value2.7 s
96/100
10%
Value300 ms
78/100
30%
Value0
100/100
15%
Value5.6 s
69/100
10%
47 ms
172 ms
72 ms
76 ms
75 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Assemblathon.org, 30% (13 requests) were made to Static.tumblr.com and 26% (11 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (224 ms) relates to the external source Px.srvcs.tumblr.com.
Page size can be reduced by 164.4 kB (41%)
396.8 kB
232.4 kB
In fact, the total size of Assemblathon.org main page is 396.8 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. 65% of websites need less resources to load. Javascripts take 147.2 kB which makes up the majority of the site volume.
Potential reduce by 91.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 91.0 kB or 76% of the original size.
Potential reduce by 66.2 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. Obviously, Assemblathon needs image optimization as it can save up to 66.2 kB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 754 B
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. Assemblathon.org has all CSS files already compressed.
Number of requests can be reduced by 22 (61%)
36
14
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Assemblathon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
assemblathon.org
47 ms
assemblathon.org
172 ms
pre_tumblelog.js
72 ms
index.build.css
76 ms
jquery.fancybox-1.3.1.css
75 ms
style.css
78 ms
modernizr.2.6.1.min.js
82 ms
bilmur.min.js
97 ms
tumblelog_post_message_queue.js
77 ms
stylesheet.css
73 ms
tweets.js
36 ms
jquery.min.js
97 ms
script.js
107 ms
widgets.js
55 ms
plusone.js
126 ms
index.build.js
106 ms
tumblr_inline_p9ph04MEoB1rh4uu5_500.jpg
210 ms
5cbd4b4d287f21a7674db2235c532a8c2ad12bac.jpg
207 ms
avatar_9299fbe764ca_64.pnj
207 ms
effector-sprite.png
147 ms
tumblr_static_assemblathon_banner_940_px.png
203 ms
post_shadow.png
146 ms
photo_btns_med.png
174 ms
cb=gapi.loaded_0
167 ms
impixu
224 ms
g.gif
149 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
114 ms
impixu
137 ms
analytics.html
64 ms
login_check.html
19 ms
post_shadow.png
57 ms
effector-sprite.png
56 ms
topbar_bg.png
53 ms
header_shadow.png
53 ms
g.gif
73 ms
photo_btns_med.png
46 ms
consent
92 ms
cs.js
13 ms
header.build.js
3 ms
exceptions.js
5 ms
index.build.js
7 ms
cdn.json
21 ms
g.gif
5 ms
assemblathon.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
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.
assemblathon.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
assemblathon.org SEO score
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
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 Assemblathon.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 Assemblathon.org 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.
assemblathon.org
Open Graph data is detected on the main page of Assemblathon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: