2.5 sec in total
57 ms
1.8 sec
690 ms
Click here to check amazing Reportingon Health content for United States. Otherwise, check out these important facts you probably never knew about reportingonhealth.org
We empower and equip journalists to tell stories of health in collaboration with communities.
Visit reportingonhealth.orgWe analyzed Reportingonhealth.org page load time and found that the first response time was 57 ms and then it took 2.5 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.
reportingonhealth.org performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value7.6 s
4/100
25%
Value3.2 s
92/100
10%
Value250 ms
84/100
30%
Value0.009
100/100
15%
Value6.8 s
55/100
10%
57 ms
72 ms
45 ms
72 ms
47 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Reportingonhealth.org, 45% (36 requests) were made to Centerforhealthjournalism.org and 25% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (516 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 445.7 kB (37%)
1.2 MB
774.1 kB
In fact, the total size of Reportingonhealth.org main page is 1.2 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. 70% of websites need less resources to load. Images take 655.9 kB which makes up the majority of the site volume.
Potential reduce by 55.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 55.1 kB or 77% of the original size.
Potential reduce by 30.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. Reportingon Health images are well optimized though.
Potential reduce by 108.8 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 108.8 kB or 55% of the original size.
Potential reduce by 251.6 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. Reportingonhealth.org needs all CSS files to be minified and compressed as it can save up to 251.6 kB or 86% of the original size.
Number of requests can be reduced by 40 (52%)
77
37
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reportingon Health. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
reportingonhealth.org
57 ms
www.centerforhealthjournalism.org
72 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
45 ms
css_R7nbm6twOcbaXTJh5KSAtFcc50VWiCI0XDFXKxmyKRA.css
72 ms
css_Jr4jAhRz_cSQMKvRuazYUqZHUH23bxjSsTO_1FzjBq8.css
47 ms
css
134 ms
css_sXTWJ5cidJ3la-0prD3keUNlbkkGF7RjPe-Y6fkLJbY.css
61 ms
css_tTgyOKRkuw_xsg7polaCW4LKx8hb16w9A5bWnXUkR64.css
58 ms
labjs.min.js
57 ms
jquery.min.js
89 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
88 ms
js_p24PQUTDFVBe9mGO-XMu80a3moP9zhZmzRs5O80P8W0.js
87 ms
js_mboWjZtWYzVAmyaKYmpPAEEZdxtfplW_W7TX2ioN--w.js
88 ms
js_AC5522n-6IN8pPeOBGXrWHDR72fG9WMOqCYqB8VjhCg.js
86 ms
js_y7t7IEpf_fjSGg6RthWFnDWnsJXJXzf8AZ-a3evYl-4.js
85 ms
js_1Fb-WI8QalE5dMg6ZhXnQBv0kSdITIjLSGCRS4CClL0.js
84 ms
css_aqq0qwoadCM3fimNZRpYUFaa666A0IQHH67CUMIZU8o.css
3 ms
bdr7dqu.js
244 ms
analytics.js
147 ms
annenberg_logo.png
141 ms
OVmGCSYU_normal.jpg
195 ms
all.js
291 ms
usc_logo.png
62 ms
chj-logo.png
82 ms
search.png
53 ms
social.png
62 ms
menu-leaf.png
60 ms
menu-collapsed.png
58 ms
photo_23.jpg
84 ms
pill.jpg
85 ms
Girshman_0397.jpg
83 ms
voiceofoc_thy_sample7.jpg
110 ms
Food-Infographic-1024x524.jpg
111 ms
waneyPlanoProfile.png
195 ms
030616-kinship-care-HS05.jpg
191 ms
photo_20.jpg
179 ms
topostgenentech%20sign.jpg
179 ms
186998000_e7135a531d_z.jpg
190 ms
photo_17.jpg
190 ms
newsletter-signup-icon.png
192 ms
National-Bold.otf
197 ms
National-Regular.otf
196 ms
NationalWeb-Light.woff
193 ms
likebox.php
264 ms
collect
146 ms
d
211 ms
ebiMDO3r-8l.css
184 ms
jGc-59L_9lo.css
228 ms
k5BhlqovqZn.css
270 ms
Pa4LYC3smxF.js
344 ms
FJmpeSpHpjS.js
382 ms
0wM5s1Khldu.js
306 ms
1bNoFZUdlYZ.js
307 ms
OloiM1PZafe.js
307 ms
LTv6ZK-5zxz.js
434 ms
1FCa-btixu2.js
397 ms
Oagsvfb4VWi.js
401 ms
pObvZSrFc_4.js
401 ms
HgJbVwzBr8E.js
397 ms
H3EKDTObx05.js
420 ms
OZFAYTv-ZUg.js
423 ms
37 ms
xd_arbiter.php
128 ms
xd_arbiter.php
270 ms
12729389_10154017323343846_6109657288475077898_n.png
394 ms
12191476_10153790346398846_6831042405688734443_n.jpg
432 ms
12651274_10103725471013123_9004052726772521899_n.jpg
473 ms
11951215_10207889338013158_8612796913250240580_n.jpg
515 ms
10606230_185170581837114_212096698064571086_n.jpg
516 ms
10375988_1449156378687837_5851535549490636415_n.jpg
514 ms
1069165_402923893159814_725320254_n.jpg
512 ms
12729360_500521666817238_7749171289036268871_n.jpg
514 ms
wL6VQj7Ab77.png
222 ms
s7jcwEQH7Sx.png
223 ms
gxbPuQdXIZP.png
43 ms
I6-MnjEovm5.js
62 ms
pQrUxxo5oQp.js
82 ms
nr-885.min.js
16 ms
ping
56 ms
af75fd10f1
54 ms
reportingonhealth.org 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
<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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
reportingonhealth.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
reportingonhealth.org 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
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 Reportingonhealth.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 Reportingonhealth.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.
reportingonhealth.org
Open Graph description is not detected on the main page of Reportingon Health. 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: