7.6 sec in total
2.7 sec
4.6 sec
222 ms
Visit congress.org now to see the best up-to-date Congress content for United States and also check out these interesting facts you probably never knew about congress.org
Enter your information and quickly identify and contact the elected officials currently representing you.
Visit congress.orgWe analyzed Congress.org page load time and found that the first response time was 2.7 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
congress.org performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value7.1 s
5/100
25%
Value9.1 s
13/100
10%
Value930 ms
30/100
30%
Value0
100/100
15%
Value13.3 s
11/100
10%
2701 ms
16 ms
6 ms
15 ms
7 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 18% of them (13 requests) were addressed to the original Congress.org, 15% (11 requests) were made to Scout.scoutanalytics.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Congress.org.
Page size can be reduced by 447.4 kB (58%)
771.3 kB
324.0 kB
In fact, the total size of Congress.org main page is 771.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 442.6 kB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.1 kB or 77% of the original size.
Potential reduce by 11.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. Congress images are well optimized though.
Potential reduce by 295.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 295.4 kB or 67% of the original size.
Potential reduce by 118.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. Congress.org needs all CSS files to be minified and compressed as it can save up to 118.4 kB or 83% of the original size.
Number of requests can be reduced by 36 (56%)
64
28
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Congress. 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 7 to 1 for CSS and as a result speed up the page load time.
congress.org
2701 ms
jquery.js
16 ms
jquery-migrate.min.js
6 ms
jquery.cycle.all.2.72.js
15 ms
style.css
7 ms
css
26 ms
base.css
3 ms
layout.css
4 ms
controltag
19 ms
ga.js
27 ms
195 ms
header-womanshooting.jpg
11 ms
banner-stateofstate.jpg
9 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
54 ms
__utm.gif
30 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
33 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
43 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
61 ms
CAjsform.js
32 ms
CAjslib.js
31 ms
CASCjslib.js
35 ms
tylayer.js
34 ms
capwiz.css
30 ms
caonly.css
13 ms
xc.css
23 ms
congressorg-megavote-logo.png
54 ms
sat.ashx
261 ms
spacer.gif
25 ms
mv_example2.gif
46 ms
mv_signup.gif
44 ms
PageHit.ashx
412 ms
Sat.ashx
456 ms
satcombined_min4.0.0.142.js
174 ms
Sat.ashx
375 ms
empty.html
86 ms
side-moneyline.gif
105 ms
housead.jpg
7 ms
all.js
267 ms
side-moneyline.gif
18 ms
logo-cqrollcall.png
17 ms
154 ms
sat.ashx
88 ms
munchkin.js
6 ms
xd_arbiter.php
430 ms
xd_arbiter.php
574 ms
munchkin.js
5 ms
visitWebPage
409 ms
PageHit.ashx
332 ms
like_box.php
347 ms
Sat.ashx
83 ms
Sat.ashx
396 ms
optout_check
15 ms
jTuqQ-OPDr6.css
292 ms
n370yiaI2G6.css
359 ms
_rx8naC75Dy.js
497 ms
x5F9OMjKyLw.js
626 ms
ICDbTSzjQEg.js
518 ms
TTCre3391I0.js
517 ms
empty.html
87 ms
optout_check
23 ms
935923_10151635964472110_491454526_n.jpg
284 ms
969934_10151635963527110_1610356054_n.png
349 ms
1970629_224295027778514_1760938683_n.jpg
420 ms
10354686_10150004552801856_220367501106153455_n.jpg
484 ms
73293_114183495310626_6463283_n.jpg
487 ms
12791117_676222512518503_1203491116545439788_n.jpg
489 ms
10153901_10204107218660427_7845547438673918105_n.jpg
486 ms
12717349_494897307383365_794112533487840674_n.jpg
489 ms
11659397_100944113633472_6551793108000294571_n.jpg
486 ms
wL6VQj7Ab77.png
72 ms
s7jcwEQH7Sx.png
73 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
70 ms
congress.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
congress.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
Browser errors were logged to the console
congress.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Congress.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 Congress.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.
congress.org
Open Graph description is not detected on the main page of Congress. 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: