4.2 sec in total
21 ms
3.7 sec
529 ms
Click here to check amazing Retraction Watch Wordpress content for United States. Otherwise, check out these important facts you probably never knew about retractionwatch.wordpress.com
Tracking retractions as a window into the scientific process
Visit retractionwatch.wordpress.comWe analyzed Retractionwatch.wordpress.com page load time and found that the first response time was 21 ms and then it took 4.2 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.wordpress.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value4.8 s
31/100
25%
Value3.6 s
87/100
10%
Value20 ms
100/100
30%
Value0.046
99/100
15%
Value4.6 s
81/100
10%
21 ms
1581 ms
126 ms
187 ms
248 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Retractionwatch.wordpress.com, 19% (22 requests) were made to O.twimg.com and 16% (18 requests) were made to Retractionwatch.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Retractionwatch.com.
Page size can be reduced by 460.3 kB (26%)
1.8 MB
1.3 MB
In fact, the total size of Retractionwatch.wordpress.com main page is 1.8 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 234.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 234.0 kB or 83% of the original size.
Potential reduce by 16.7 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 Wordpress 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 101.7 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.wordpress.com needs all CSS files to be minified and compressed as it can save up to 101.7 kB or 75% of the original size.
Number of requests can be reduced by 55 (49%)
112
57
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Retraction Watch Wordpress. 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 14 to 1 for CSS and as a result speed up the page load time.
retractionwatch.wordpress.com
21 ms
retractionwatch.com
1581 ms
style.css
126 ms
genericons.css
187 ms
jetpack.css
248 ms
jquery.js
309 ms
jquery-migrate.min.js
140 ms
wp-emoji-release.min.js
124 ms
books.jpg
21 ms
AJPS2015012714522401.jpg
20 ms
cover.png
15 ms
Screen-Shot-2016-02-22-at-10.19.43-AM.png
16 ms
ioannidis.jpg
15 ms
rsl.jpg
18 ms
kato.jpg
17 ms
Screen-Shot-2016-03-15-at-12.04.43-PM.png
17 ms
top.gif
71 ms
rss.png
72 ms
2.cover_.gif
17 ms
1.jpg
18 ms
gtm.js
95 ms
bubble_right.gif
86 ms
bubble_left.gif
86 ms
quote.gif
85 ms
photon.js
65 ms
devicepx-jetpack.js
28 ms
gprofiles.js
63 ms
wpgroho.js
85 ms
wp-embed.min.js
85 ms
sharing.js
93 ms
e-201611.js
27 ms
loading.gif
344 ms
Genericons.svg
347 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
24 ms
sdk.js
344 ms
widgets.js
292 ms
analytics.js
5 ms
collect
263 ms
hovercard.css
77 ms
services.css
80 ms
graph.facebook.com
74 ms
g.gif
20 ms
graph.facebook.com
94 ms
graph.facebook.com
71 ms
graph.facebook.com
92 ms
graph.facebook.com
70 ms
graph.facebook.com
113 ms
graph.facebook.com
111 ms
graph.facebook.com
111 ms
graph.facebook.com
110 ms
graph.facebook.com
110 ms
g.gif
7 ms
g.gif
8 ms
g.gif
9 ms
g.gif
8 ms
g.gif
8 ms
g.gif
8 ms
g.gif
57 ms
g.gif
56 ms
g.gif
56 ms
g.gif
55 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
124 ms
149 ms
xd_arbiter.php
221 ms
xd_arbiter.php
479 ms
syndication
96 ms
601326179430301696
158 ms
530043868238999553
134 ms
proxy.jpg
91 ms
proxy.jpg
105 ms
proxy.jpg
108 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
70 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
72 ms
proxy.jpg
73 ms
proxy.jpg
80 ms
proxy.jpg
72 ms
proxy.jpg
92 ms
proxy.jpg
92 ms
proxy.jpg
90 ms
proxy.jpg
85 ms
proxy.jpg
84 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
35 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
33 ms
bearcubtwitter_normal.jpg
46 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
39 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
57 ms
U_YUjFeu_normal.jpg
37 ms
Cd6lvUPUMAATNDC.jpg:small
35 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
30 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
54 ms
page.php
106 ms
proxy.jpg
4 ms
proxy.jpg
5 ms
proxy.jpg
3 ms
Ezryo55Cca5.css
282 ms
1kPfZUdGrka.js
419 ms
HQ1UKbUXIBt.js
619 ms
Qd7TTBR3F_S.js
553 ms
proxy.jpg
4 ms
proxy.jpg
4 ms
proxy.jpg
4 ms
proxy.jpg
5 ms
proxy.jpg
4 ms
proxy.jpg
4 ms
proxy.jpg
5 ms
proxy.jpg
6 ms
12417699_881348835317041_3133766881319000306_n.jpg
284 ms
11990491_826925434092715_3952489425852667364_n.jpg
352 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
78 ms
jot.html
28 ms
R9GKCzjAnbk.js
71 ms
AWWjhOengNF.js
69 ms
YnSasnyq68i.js
71 ms
kQf_jlUv-kX.js
134 ms
retractionwatch.wordpress.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.wordpress.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.wordpress.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.wordpress.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.wordpress.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.wordpress.com
Open Graph data is detected on the main page of Retraction Watch Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: