2.1 sec in total
79 ms
1.8 sec
240 ms
Click here to check amazing Whistleblower content for United States. Otherwise, check out these important facts you probably never knew about whistleblower.org
Government Accountability Project. Protecting Whistleblowers since 1977
Visit whistleblower.orgWe analyzed Whistleblower.org page load time and found that the first response time was 79 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
whistleblower.org performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value10.5 s
0/100
25%
Value7.3 s
29/100
10%
Value460 ms
62/100
30%
Value0.216
58/100
15%
Value10.0 s
26/100
10%
79 ms
640 ms
48 ms
72 ms
73 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 75% of them (64 requests) were addressed to the original Whistleblower.org, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (640 ms) belongs to the original domain Whistleblower.org.
Page size can be reduced by 512.2 kB (50%)
1.0 MB
510.9 kB
In fact, the total size of Whistleblower.org main page is 1.0 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. 35% of websites need less resources to load. Images take 379.3 kB which makes up the majority of the site volume.
Potential reduce by 48.9 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 48.9 kB or 82% of the original size.
Potential reduce by 44.8 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, Whistleblower needs image optimization as it can save up to 44.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 227.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 227.8 kB or 63% of the original size.
Potential reduce by 190.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. Whistleblower.org needs all CSS files to be minified and compressed as it can save up to 190.7 kB or 85% of the original size.
Number of requests can be reduced by 55 (71%)
77
22
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whistleblower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
whistleblower.org
79 ms
www.whistleblower.org
640 ms
system.base.css
48 ms
system.menus.css
72 ms
system.messages.css
73 ms
system.theme.css
74 ms
jquery.ui.core.min.css
76 ms
jquery.ui.theme.min.css
87 ms
jquery.ui.button.min.css
88 ms
jquery.ui.resizable.min.css
95 ms
jquery.ui.dialog.min.css
95 ms
date.css
97 ms
views.css
99 ms
ckeditor.css
115 ms
ctools.css
115 ms
camera.css
118 ms
superfish.css
120 ms
bootstrap.css
212 ms
bootstrap-theme.css
146 ms
main.css
172 ms
modernizr.custom.18527.js
145 ms
jquery.min.js
188 ms
jquery.once.js
143 ms
drupal.js
189 ms
jquery.ui.core.min.js
173 ms
jquery.ui.widget.min.js
170 ms
jquery.ui.button.min.js
193 ms
jquery.ui.mouse.min.js
198 ms
jquery.ui.draggable.min.js
228 ms
jquery.ui.position.min.js
220 ms
jquery.ui.resizable.min.js
219 ms
jquery.ui.dialog.min.js
220 ms
ajax.js
270 ms
jquery_update.js
268 ms
linkit.js
269 ms
progress.js
267 ms
linkitDialog.js
268 ms
buttons.js
229 ms
googleanalytics.js
264 ms
jquery.easing.1.3.js
239 ms
camera.min.js
231 ms
home.js
215 ms
jquery.hoverIntent.minified.js
213 ms
sfsmallscreen.js
213 ms
supposition.js
204 ms
superfish.js
200 ms
supersubs.js
209 ms
superfish.js
205 ms
script.js
215 ms
css
63 ms
analytics.js
272 ms
getAllAppDefault.esi
115 ms
close.gif
43 ms
logo.png
43 ms
search.gif
44 ms
wipo-logo.jpg
44 ms
Coleman.jpg
43 ms
logo_small.png
43 ms
subscribe_bottom.gif
68 ms
subscribe.gif
68 ms
youtube.png
68 ms
facebook.png
67 ms
twitter.png
69 ms
email.png
69 ms
camera_skins.png
128 ms
camera-loader.gif
102 ms
wipo-logo.jpg
275 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
84 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
101 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
125 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
126 ms
collect
15 ms
collect
78 ms
getSegment.php
33 ms
t.dhj
37 ms
t.dhj
9 ms
hbpix
106 ms
cm
92 ms
4 ms
s-3271.xgi
5 ms
39 ms
Coleman.jpg
96 ms
xrefid.xgi
7 ms
img;m=11022203137504;cache=
23 ms
whistleblower.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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
whistleblower.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
whistleblower.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
Image elements do not have [alt] attributes
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 Whistleblower.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 Whistleblower.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.
whistleblower.org
Open Graph description is not detected on the main page of Whistleblower. 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: