1.7 sec in total
61 ms
1.3 sec
302 ms
Welcome to centerforinvestigativereporting.org homepage info - get ready to check Center For Investigative Reporting best content right away, or after learning these important things about centerforinvestigativereporting.org
We engage and empower the public through investigative journalism and groundbreaking storytelling that sparks action, improves lives and protects our democracy.
Visit centerforinvestigativereporting.orgWe analyzed Centerforinvestigativereporting.org page load time and found that the first response time was 61 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
centerforinvestigativereporting.org performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value5.7 s
16/100
25%
Value3.9 s
82/100
10%
Value400 ms
68/100
30%
Value0.177
68/100
15%
Value5.6 s
69/100
10%
61 ms
63 ms
27 ms
46 ms
46 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Centerforinvestigativereporting.org, 78% (51 requests) were made to Cironline.org and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Yeti-cir-test.s3.amazonaws.com.
Page size can be reduced by 690.7 kB (47%)
1.5 MB
773.1 kB
In fact, the total size of Centerforinvestigativereporting.org main page is 1.5 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. 55% of websites need less resources to load. Javascripts take 616.7 kB which makes up the majority of the site volume.
Potential reduce by 80.6 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 80.6 kB or 75% of the original size.
Potential reduce by 51.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. Center For Investigative Reporting images are well optimized though.
Potential reduce by 416.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 416.4 kB or 68% of the original size.
Potential reduce by 142.4 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. Centerforinvestigativereporting.org needs all CSS files to be minified and compressed as it can save up to 142.4 kB or 88% of the original size.
Number of requests can be reduced by 40 (63%)
63
23
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Center For Investigative Reporting. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
centerforinvestigativereporting.org
61 ms
cironline.org
63 ms
date.css
27 ms
google_admanager.css
46 ms
lightbox.css
46 ms
node_embed.css
47 ms
views_slideshow.css
46 ms
wysiwyg_linebreaks.css
47 ms
cir_misc.css
47 ms
ds_2col.css
64 ms
field_group.css
65 ms
flexslider_img.css
64 ms
reset.css
83 ms
system.base.css
87 ms
system.theme.css
102 ms
search.css
101 ms
formalize.css
103 ms
flexslider.css
103 ms
screen.css
104 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
130 ms
js_aWiQ9fvPkOXyPwxBu2QprjK_mqzskAq4obsa04reQJE.js
121 ms
lightbox.js
122 ms
js_obEkyMiNHP4uVP3jrEFgeiCK4F1fwGl0B1scPHoV5pA.js
121 ms
dez4ajo.js
142 ms
js_Thfu6KrVhcf7z8KPJHmub6ji0zHIVOH4RWTZDGmrRGU.js
121 ms
js_Mc79owH0BY4uPSVc9iaaFrqiPx_DrVo0F9piioWiBjk.js
121 ms
js_i_X3IeOYncYpIbqZOegjIu0omgIKqbNyy-O7uE1qwiM.js
174 ms
munchkin.js
13 ms
addthis_widget.js
9 ms
ga.js
181 ms
btn-donate-cta.png
1028 ms
reveal_banner.png
195 ms
logo.png
161 ms
icons_social.png
152 ms
icons.png
160 ms
kendle-bags-tout.jpg
160 ms
payday-ca-flag-tout.jpg
159 ms
strawberries2-0013-tout.jpg
192 ms
generation_z_frame_grab.png
219 ms
derika_moses-27-feature_0.jpg
214 ms
select_arrow.gif
189 ms
ap746877223374-web.jpg
189 ms
icons_reports-authors.png
189 ms
icons_reports-tags.png
214 ms
ap101209080734.jpg
213 ms
candy-man033_0.jpg
214 ms
strawberries-0003-thumb.jpg
214 ms
icons_reports-projects.png
218 ms
preschool-ext_web.jpg
218 ms
candy-man078_2.jpg
220 ms
onion.jpg
218 ms
guilty-guard-generic.jpg
220 ms
munchkin.js
105 ms
boost
48 ms
300lo.json
45 ms
prev.gif
90 ms
next.gif
90 ms
expand.gif
91 ms
contract.gif
92 ms
loading.gif
92 ms
icons_carousel-nav.png
96 ms
sh.07f0d9bf220d07a763adad1e.html
32 ms
inpage_linkid.js
30 ms
visitWebPage
155 ms
__utm.gif
13 ms
centerforinvestigativereporting.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
centerforinvestigativereporting.org 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
Browser errors were logged to the console
Page has valid source maps
centerforinvestigativereporting.org SEO score
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 Centerforinvestigativereporting.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 Centerforinvestigativereporting.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.
centerforinvestigativereporting.org
Open Graph description is not detected on the main page of Center For Investigative Reporting. 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: