5.6 sec in total
1.7 sec
3.1 sec
829 ms
Click here to check amazing Retraction Watch content for United States. Otherwise, check out these important facts you probably never knew about retractionwatch.com
Tracking retractions as a window into the scientific process
Visit retractionwatch.comWe analyzed Retractionwatch.com page load time and found that the first response time was 1.7 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
retractionwatch.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.6 s
61/100
25%
Value3.2 s
92/100
10%
Value0 ms
100/100
30%
Value0.046
99/100
15%
Value3.3 s
94/100
10%
1664 ms
131 ms
195 ms
256 ms
320 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 20% of them (18 requests) were addressed to the original Retractionwatch.com, 12% (11 requests) were made to Pixel.wp.com and 11% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Retractionwatch.com.
Page size can be reduced by 419.9 kB (58%)
727.0 kB
307.2 kB
In fact, the total size of Retractionwatch.com main page is 727.0 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. 60% of websites need less resources to load. HTML takes 277.4 kB which makes up the majority of the site volume.
Potential reduce by 231.1 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 231.1 kB or 83% of the original size.
Potential reduce by 5.9 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. Retraction Watch images are well optimized though.
Potential reduce by 107.9 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 107.9 kB or 57% of the original size.
Potential reduce by 74.9 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. Retractionwatch.com needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 72% of the original size.
Number of requests can be reduced by 50 (57%)
87
37
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Retraction Watch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
retractionwatch.com
1664 ms
style.css
131 ms
genericons.css
195 ms
jetpack.css
256 ms
jquery.js
320 ms
jquery-migrate.min.js
156 ms
wp-emoji-release.min.js
125 ms
Screen-Shot-2016-03-01-at-2.46.54-PM.png
386 ms
cover_nature-1.jpg
300 ms
3.jpg
298 ms
Chinese-med-j.png
380 ms
books.jpg
298 ms
mmr_12_41.gif
378 ms
Nature-protocols.gif
382 ms
bensmall.jpg
378 ms
Screen-Shot-2016-02-25-at-5.21.28-PM.png
379 ms
top.gif
87 ms
rss.png
88 ms
JCS-e1455823490452-147x150.jpg
374 ms
gtm.js
85 ms
bubble_right.gif
145 ms
bubble_left.gif
145 ms
quote.gif
131 ms
photon.js
96 ms
devicepx-jetpack.js
90 ms
gprofiles.js
146 ms
wpgroho.js
89 ms
wp-embed.min.js
90 ms
sharing.js
90 ms
e-201609.js
70 ms
loading.gif
90 ms
Genericons.svg
291 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
79 ms
sdk.js
75 ms
analytics.js
70 ms
widgets.js
75 ms
713 ms
collect
68 ms
xd_arbiter.php
69 ms
xd_arbiter.php
499 ms
hovercard.css
146 ms
services.css
196 ms
graph.facebook.com
248 ms
g.gif
106 ms
graph.facebook.com
265 ms
graph.facebook.com
279 ms
graph.facebook.com
310 ms
graph.facebook.com
300 ms
graph.facebook.com
297 ms
graph.facebook.com
294 ms
graph.facebook.com
308 ms
graph.facebook.com
367 ms
graph.facebook.com
376 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
55 ms
g.gif
22 ms
g.gif
23 ms
g.gif
21 ms
g.gif
21 ms
g.gif
22 ms
g.gif
20 ms
g.gif
13 ms
g.gif
14 ms
g.gif
15 ms
g.gif
8 ms
syndication
116 ms
601326179430301696
155 ms
530043868238999553
195 ms
page.php
139 ms
o_zjiOVHPPW.css
50 ms
_rx8naC75Dy.js
69 ms
t-KLv3gqZy0.js
119 ms
uLtKx7ldlvR.js
111 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
22 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
32 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
182 ms
U_YUjFeu_normal.jpg
305 ms
Ccfd-glUkAAwIP1.jpg:small
304 ms
CcOlm7dVIAAPFQw.jpg:small
311 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
205 ms
12417699_881348835317041_3133766881319000306_n.jpg
235 ms
11990491_826925434092715_3952489425852667364_n.jpg
154 ms
wL6VQj7Ab77.png
132 ms
CSXXCvknpgK.png
132 ms
bearcubtwitter_normal.jpg
110 ms
Ccfd9-vUYAAw36b.jpg:small
109 ms
R9a_DtVRZgv.js
11 ms
cUDgRFxaoIk.js
12 ms
0JBr1QHp8Gi.js
11 ms
kDOzhTr2W91.js
11 ms
retractionwatch.com accessibility score
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
Links do not have a discernible name
retractionwatch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
retractionwatch.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Retractionwatch.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 Retractionwatch.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.
retractionwatch.com
Open Graph data is detected on the main page of Retraction Watch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: