4.8 sec in total
1.1 sec
3.1 sec
489 ms
Visit sourcewatch.org now to see the best up-to-date Source Watch content for United States and also check out these interesting facts you probably never knew about sourcewatch.org
Visit sourcewatch.orgWe analyzed Sourcewatch.org page load time and found that the first response time was 1.1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sourcewatch.org performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value4.2 s
44/100
25%
Value8.1 s
21/100
10%
Value4,100 ms
1/100
30%
Value0
100/100
15%
Value12.8 s
13/100
10%
1146 ms
502 ms
292 ms
715 ms
5 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 44% of them (24 requests) were addressed to the original Sourcewatch.org, 9% (5 requests) were made to Pagead2.googlesyndication.com and 7% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Sourcewatch.org.
Page size can be reduced by 547.4 kB (52%)
1.1 MB
515.2 kB
In fact, the total size of Sourcewatch.org main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 365.1 kB which makes up the majority of the site volume.
Potential reduce by 111.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 111.6 kB or 79% of the original size.
Potential reduce by 17.4 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. Source Watch images are well optimized though.
Potential reduce by 216.5 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 216.5 kB or 59% of the original size.
Potential reduce by 201.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. Sourcewatch.org needs all CSS files to be minified and compressed as it can save up to 201.9 kB or 83% of the original size.
Number of requests can be reduced by 20 (42%)
48
28
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Source 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 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
SourceWatch
1146 ms
load.php
502 ms
load.php
292 ms
load.php
715 ms
show_ads.js
5 ms
page.js
9 ms
load.php
221 ms
load.php
213 ms
share_save_171_16.png
27 ms
Chris_Horner-Arch_Coal200px.jpg
26 ms
Electric-car-plug200px.jpg
61 ms
Danger_OSHA_violators200px.jpg
26 ms
Ford_dumps_ALEC200px.jpg
59 ms
We_Are_Not_Problem200px.jpg
59 ms
STOP-TTIP200px.jpg
61 ms
Obama_signs_FPSW_EO-2014-Pete_Souza_CC_BY_3.0_US-200px.jpg
58 ms
200px-Danger_OSHA_Dupont_Poison_Gas.png
61 ms
200px-Caution_lobbying_hazard.png
61 ms
Marco_Rubio-CC_BY_2.0-Gage_Skidmore-200px.jpg
60 ms
John_Kasich-Beth_Hansen200px.jpg
60 ms
KochExposed.org200px.jpg
60 ms
cc-by-sa.png
74 ms
poweredby_mediawiki_88x31.png
74 ms
wiki.png
55 ms
Icons-mini-file_acrobat.gif
59 ms
ca-pub-1565478203452184.js
50 ms
zrt_lookup.html
107 ms
show_ads_impl.js
53 ms
0xdgVnI22L0
90 ms
load.php
426 ms
load.php
231 ms
ads
199 ms
osd.js
6 ms
www-embed-player-vflZsBgOl.css
69 ms
www-embed-player.js
90 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
38 ms
ad_status.js
32 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
31 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
32 ms
analytics.js
35 ms
sm13.html
59 ms
css
86 ms
m_js_controller.js
89 ms
abg.js
98 ms
collect
25 ms
ga.js
35 ms
favicon
79 ms
googlelogo_color_112x36dp.png
48 ms
nessie_icon_tiamat_white.png
17 ms
s
34 ms
x_button_blue2.svg
15 ms
ui
21 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
3 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
19 ms
sourcewatch.org accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
sourcewatch.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
Page has valid source maps
sourcewatch.org SEO score
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 Sourcewatch.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 Sourcewatch.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.
sourcewatch.org
Open Graph description is not detected on the main page of Source Watch. 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: