2.6 sec in total
177 ms
2 sec
359 ms
Visit plosgenetics.org now to see the best up-to-date PLOS Genetics content for United States and also check out these interesting facts you probably never knew about plosgenetics.org
Visit plosgenetics.orgWe analyzed Plosgenetics.org page load time and found that the first response time was 177 ms and then it took 2.4 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. This domain responded with an error, which can significantly jeopardize Plosgenetics.org rating and web reputation
plosgenetics.org performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value8.4 s
2/100
25%
Value6.2 s
43/100
10%
Value5,050 ms
0/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
177 ms
178 ms
325 ms
187 ms
250 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Plosgenetics.org, 32% (24 requests) were made to Journals.plos.org and 30% (22 requests) were made to Ads.plos.org. The less responsive or slowest element that took the longest time to load (722 ms) relates to the external source Journals.plos.org.
Page size can be reduced by 511.6 kB (55%)
933.9 kB
422.3 kB
In fact, the total size of Plosgenetics.org main page is 933.9 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. 50% of websites need less resources to load. Images take 373.1 kB which makes up the majority of the site volume.
Potential reduce by 28.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 28.8 kB or 74% of the original size.
Potential reduce by 70.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. Obviously, PLOS Genetics needs image optimization as it can save up to 70.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 169.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 169.3 kB or 72% of the original size.
Potential reduce by 243.2 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. Plosgenetics.org needs all CSS files to be minified and compressed as it can save up to 243.2 kB or 85% of the original size.
Number of requests can be reduced by 16 (29%)
56
40
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PLOS Genetics. 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.
plosgenetics.org
177 ms
www.plosgenetics.org
178 ms
325 ms
asset_BMINVXKHMC4Q56QSI3VO4EY63VBE7TVO.css
187 ms
modernizr-v2.7.1.js
250 ms
jquery-2.1.4.min.js
5 ms
asset_LRL5H56HAJSZVJR77SIGWBHUKQ5N66A3.js
373 ms
analytics.js
89 ms
afr.php
203 ms
text.vert.ad.gif
83 ms
logo.png
83 ms
gradient-dark_1x364.png
83 ms
47176f67c01362a09ac020ff6880c0c90fe8a25dc369e6a1f34c3b59697a03cc
722 ms
5a396392962f7b8f4c8eb9913418c337b20376fd037dddacba2c2763c8b246c5
253 ms
asset
674 ms
17ff06fd99e322f2c0d82fe129c3329593571543cdc21448a0087c09357e0f4a
183 ms
3c51bbfb2b5e22cfbe58a7112ee514e2d77d2c29d8e67af4a4139aa0638eaaaa
181 ms
4503c23a7d219eb61ab158586d24ae9e6933b0aeacc73b5b4b42dc604ce78378
183 ms
592deca73e07653e05fbc53bc4b1710dcea5cfcc2dbcbe1a9be8bfc7fb16eb93
251 ms
1e277fbef8ea844c46188d963e765bb8957ab3dcd936dd3180f0fb3f7c9471ab
252 ms
9b82cd40314735c32397c6eca591a9fa3aa770557e4228abc669269e06d85b54
251 ms
77dad4fca647421051f830780a2c16437370e218fc8cda6d05c48c76f00f3a03
420 ms
b61991d97122c237d53a06092a5cd4a786a9c4aa36d4c1cdd0eab836c18fc950
355 ms
a281418733e1eb02d1ad885ca2e5612a8ed7fe5ecfd2374c1a4d348ffe18dbf4
356 ms
logo-plos-footer.png
340 ms
widgets.js
123 ms
afr.php
156 ms
afr.php
155 ms
afr.php
155 ms
fs_albert.ttf
541 ms
fontawesome-webfont.ttf
717 ms
fs_albert-bold-webfont.ttf
562 ms
701 ms
afr.php
347 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
137 ms
afr.php
353 ms
afr.php
382 ms
afr.php
408 ms
syndication
105 ms
478999578797035520
322 ms
ai.php
163 ms
lg.php
163 ms
ai.php
110 ms
lg.php
189 ms
ai.php
95 ms
lg.php
184 ms
ai.php
170 ms
lg.php
170 ms
ai.php
155 ms
lg.php
100 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
71 ms
pk712n4blw8kyf7yzqwc_normal.jpeg
130 ms
G9oBWNXy_normal.jpg
154 ms
PCD_Logo_no_writing_normal.jpg
196 ms
9yvEGqLm_normal.jpeg
227 ms
4lBqKuga_normal.jpeg
233 ms
s0Cj3xzP_normal.jpg
243 ms
OFZs5M7c_normal.png
244 ms
4dEbDGnB_normal.jpg
256 ms
BAh6fBQS_normal.jpeg
253 ms
gio3xwRv_normal.jpg
256 ms
DSC00114_normal.JPG
272 ms
31cc871ea79418dfd3a7da8aade34508_normal.jpeg
273 ms
S-3HD3pT_normal.jpg
284 ms
CcOGnL3XEAEJMYl.jpg:small
285 ms
lg.php
99 ms
lg.php
101 ms
print.css
166 ms
ai.php
78 ms
lg.php
154 ms
Sherwood.-e1456750412141.jpg%20651w
83 ms
social_norms_in_small_scale_societies-5.png%201929w
161 ms
jot
25 ms
plosgenetics.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
plosgenetics.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
Missing source maps for large first-party JavaScript
plosgenetics.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 Plosgenetics.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 Plosgenetics.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.
plosgenetics.org
Open Graph description is not detected on the main page of PLOS Genetics. 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: