2.8 sec in total
167 ms
2 sec
706 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 167 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
congress.org performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value8.0 s
2/100
25%
Value7.1 s
32/100
10%
Value1,670 ms
11/100
30%
Value0.001
100/100
15%
Value15.9 s
6/100
10%
167 ms
131 ms
93 ms
26 ms
16 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Congress.org, 19% (16 requests) were made to Votervoice.net and 10% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (615 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 347.7 kB (36%)
969.2 kB
621.5 kB
In fact, the total size of Congress.org main page is 969.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 406.5 kB which makes up the majority of the site volume.
Potential reduce by 243.8 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 68.2 kB, which is 24% 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 243.8 kB or 84% of the original size.
Potential reduce by 3.7 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 50.1 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 50.1 kB or 12% of the original size.
Potential reduce by 50.0 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 50.0 kB or 34% of the original size.
Number of requests can be reduced by 50 (77%)
65
15
The browser has sent 65 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 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
congress.org
167 ms
www.congress.org
131 ms
find-your-legislator
93 ms
sharer.min.js
26 ms
new.css
16 ms
app-c310af66.css
36 ms
htmx.min.js
75 ms
otSDKStub.js
75 ms
teknkl-formsplus-emailpattern-1.0.3.js
76 ms
Plugin.js
163 ms
css2
55 ms
gtm.js
130 ms
Find-Your_Leg-89811086.jpg
277 ms
white-facebook-01_200603_145351.svg
259 ms
white-twitter-01_200603_145415.svg
255 ms
white-linkedin-01_200603_145432.svg
257 ms
white-youtube-01_200603_145452.svg
259 ms
white-angellist-01_200603_145510.svg
257 ms
white-instagram-01_200603_145527.svg
452 ms
white-medium-01_200603_145543.svg
454 ms
aa25133e-da51-4174-81d9-9ff5ab9a1bf3-test.json
195 ms
Directory
119 ms
uni-neue-400-983bd459.woff
116 ms
uni-neue-300-461d7b0d.woff
116 ms
uni-neue-700-65b1bafe.woff
116 ms
uni-neue-800-20cb39d4.woff
176 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G.woff
186 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_G.woff
342 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G.woff
535 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G.woff
615 ms
616f04ad-c371-492a-857e-56fb23fe93cf.js
563 ms
js
119 ms
analytics.js
387 ms
uwt.js
385 ms
bb26aac2-7dd7-4afc-a7f3-90e6f01ca6b1.js
384 ms
bat.js
458 ms
fbevents.js
376 ms
destination
276 ms
insight.min.js
442 ms
munchkin.js
365 ms
otBannerSdk.js
73 ms
Address
227 ms
en.json
382 ms
jquery-1.11.3.min.js
271 ms
jquery-migrate-1.2.1.min.js
343 ms
jquery.address-1.5.min.js
404 ms
jquery.placeholder.min.js
419 ms
jquery-ui-1.10.2.all.min.js
419 ms
UserSiteText.en-us.js
443 ms
Advocacy.Address
417 ms
embed.js
472 ms
iframely.load.js
442 ms
jquery-ui-1.10.2.all.min.css
482 ms
css
279 ms
css
401 ms
fontawesome-all.min.css
556 ms
narrow
475 ms
Advocacy.css
487 ms
js
341 ms
js
472 ms
364 ms
collect
254 ms
munchkin.js
217 ms
6si.min.js
124 ms
otFlat.json
129 ms
otPcCenter.json
142 ms
otCommonStyles.css
145 ms
adsct
496 ms
adsct
495 ms
collect
64 ms
visitWebPage
547 ms
ga-audiences
242 ms
308 ms
vvpoweredby-gray-fiscalnote.en-US.png
229 ms
ajax-loader.gif
157 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
112 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
112 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
185 ms
js
105 ms
js
60 ms
collect
18 ms
collect
20 ms
congress.org accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
congress.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
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
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
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 data is detected on the main page of Congress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: