senate.gov

senate.gov is SSL secured

Free website and domain report on senate.gov

Last Updated: 17th June, 2021 Update Now
Overview

Snoop Summary for senate.gov

This is a free and comprehensive report about senate.gov. Senate.gov is hosted in New York, New York in United States on a server with an IP address of 23.5.234.215, where USD is the local currency and the local language is English. Our records indicate that senate.gov is owned/operated by U.S. Senate. Senate.gov is expected to earn an estimated $970 USD per day from advertising revenue. The sale of senate.gov would possibly be worth $707,952 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Senate.gov is insanely popular with an estimated 154,549 daily unique visitors. This report was last updated 17th June, 2021.

About senate.gov

Site Preview: senate.gov senate.gov
Title: U.S. Senate
Description: Official site of "the living symbol of our union of states." Connect with Senators, and learn about Senate committees, legislation, records, art, history, schedules, news, tours, and visits. Reference material is included too.
Keywords and Tags: government, legislative branch, military, north america, opinions, politics, popular, regional, religion, senate, united states
Related Terms: buddhist symbol, california senate bill 1386, origin symbol, senate elections, senate hearing ph, superman symbol, symbol, triangle symbol, us senate, visits
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$707,952 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 9,649
Alexa Reach: 0.0085%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Australia Flag Australia 16,447
Canada Flag Canada 17,897
India Flag India 78,526
Pakistan Flag Pakistan 11,327
Russian Federation Flag Russian Federation 60,620
Taiwan, Province Of China Flag Taiwan, Province Of China 12,606
United States Flag United States 2,557

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 154,549
Monthly Visitors: 4,703,985
Yearly Visitors: 56,410,385
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Australia Flag Australia Daily: 1,391
Monthly: 42,336
Yearly: 507,693
0.9%
Canada Flag Canada Daily: 2,318
Monthly: 70,560
Yearly: 846,156
1.5%
India Flag India Daily: 2,009
Monthly: 61,152
Yearly: 733,335
1.3%
Other Daily: 14,991
Monthly: 456,287
Yearly: 5,471,807
9.7%
Pakistan Flag Pakistan Daily: 1,545
Monthly: 47,040
Yearly: 564,104
1%
Russian Federation Flag Russian Federation Daily: 927
Monthly: 28,224
Yearly: 338,462
0.6%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: 1,855
Monthly: 56,448
Yearly: 676,925
1.2%
United States Flag United States Daily: 129,512
Monthly: 3,941,939
Yearly: 47,271,903
83.8%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $970 USD
Monthly Revenue: $29,517 USD
Yearly Revenue: $353,971 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Australia Flag Australia Daily: $1 USD
Monthly: $18 USD
Yearly: $210 USD
0.1%
Canada Flag Canada Daily: $1 USD
Monthly: $43 USD
Yearly: $519 USD
0.1%
India Flag India Daily: $2 USD
Monthly: $62 USD
Yearly: $744 USD
0.2%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Pakistan Flag Pakistan Daily: $0 USD
Monthly: $7 USD
Yearly: $80 USD
<0.1%
Russian Federation Flag Russian Federation Daily: $0 USD
Monthly: $2 USD
Yearly: $21 USD
<0.1%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: $0 USD
Monthly: $2 USD
Yearly: $19 USD
<0.1%
United States Flag United States Daily: $965 USD
Monthly: $29,384 USD
Yearly: $352,377 USD
99.5%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: senate.gov 10
Domain Name: senate 6
Extension (TLD): gov 3

Page Speed Analysis

Average Load Time: 0.91 seconds
Load Time Comparison: Faster than 80% of sites

PageSpeed Insights

Avg. (All Categories) 60
Performance 69
Accessibility 61
Best Practices 80
SEO 55
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.senate.gov/
Updated: 17th June, 2021

1.32 seconds
First Contentful Paint (FCP)
86%
10%
4%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
69

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for senate.gov. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://senate.gov/
http/1.1
0
375.82400004612
236
0
301
http://www.senate.gov/
http/1.1
376.36700004805
547.98900004243
260
0
301
text/html
https://www.senate.gov/
http/1.1
548.42000000644
753.2610000344
8570
37206
200
text/html
Document
https://www.senate.gov/resources/styles/boilerplate.css
http/1.1
770.06300003268
905.71200003615
3600
10239
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/main.css
http/1.1
770.28799999971
1007.3759999941
7713
46582
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/nav_menu.css
http/1.1
770.62200004002
951.98900002288
4223
27812
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/skdslider.css
http/1.1
770.86700004293
981.20199999539
1969
7476
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
http/1.1
771.09200000996
1179.7270000097
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
http/1.1
771.31500001997
1032.023000007
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
http/1.1
771.59600000596
985.10200000601
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
http/1.1
771.86400000937
1031.3680000254
7028
29067
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/print.css
http/1.1
772.19300001161
1008.3890000242
1059
2262
200
text/css
Stylesheet
https://www.senate.gov/resources/scripts/respond.min.js
http/1.1
772.5850000279
1088.8300000224
2080
3216
200
text/javascript
Script
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
http/1.1
772.89399999427
1524.0990000311
33724
95997
200
text/javascript
Script
https://www.senate.gov/resources/scripts/skdslider.min.js
http/1.1
773.06100004353
1058.7450000457
2040
5720
200
text/javascript
Script
https://www.senate.gov/resources/scripts/main.js
http/1.1
773.27900001546
1416.1270000041
1323
2393
200
text/javascript
Script
https://www.senate.gov/resources/scripts/floor_status.js
http/1.1
773.47499999451
1343.7610000256
790
862
200
text/javascript
Script
https://www.senate.gov/resources/images/usFlag.png
http/1.1
1506.3160000136
1725.2800000133
17592
17276
200
image/png
Image
https://www.senate.gov/resources/images/senate_logo.png
http/1.1
1531.7619999987
1732.4070000323
11125
10809
200
image/png
Image
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
http/1.1
1551.3030000147
2284.6550000249
197028
196709
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
http/1.1
1551.4689999982
1729.9060000223
121237
120918
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
http/1.1
1551.695000031
1695.3060000087
165210
164891
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
http/1.1
1551.8400000292
1687.0179999969
136492
136173
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
http/1.1
1552.0560000441
1769.1880000057
65115
64798
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
http/1.1
1552.1830000216
1797.2020000452
171482
171163
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
http/1.1
1552.4500000174
1907.4569999939
618696
618377
200
image/jpeg
Image
https://www.senate.gov/resources/images/33_00019.jpg
http/1.1
1552.5610000477
1805.400000012
86825
86507
200
image/jpeg
Image
https://www.senate.gov/resources/images/col2_senatefloor.jpg
http/1.1
1552.9860000242
2044.8170000454
172099
171780
200
image/jpeg
Image
https://www.senate.gov/resources/graphic/history_lbj.jpg
http/1.1
1553.1480000354
1684.5080000348
33646
33329
200
image/jpeg
Image
https://www.senate.gov/resources/images/senate_logo_footer.png
http/1.1
1553.310999996
1784.953000024
21246
20930
200
image/png
Image
https://www.senate.gov/wt_sdc/central_webtrends.load.js
http/1.1
1417.631999997
1504.9640000216
961
1138
200
text/javascript
Script
https://www.senate.gov/resources/images/bkgnd_stripe_c.png
http/1.1
1560.7890000101
1820.0800000341
15777
15461
200
image/png
Image
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
http/1.1
1565.6210000161
1649.9780000304
17849
17500
200
text/plain
Font
https://www.senate.gov/resources/images/banner-bg.png
http/1.1
1566.9130000169
1700.6920000422
24590
24274
200
image/png
Image
https://www.senate.gov/resources/images/senate_logo_black.png
http/1.1
1569.5360000245
2055.6189999916
10559
10243
200
image/png
Image
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
http/1.1
1576.7680000281
1799.113999994
72246
71896
200
text/plain
Font
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
http/1.1
1578.5470000119
1763.8690000167
17729
17380
200
text/plain
Font
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
http/1.1
1579.6260000207
1668.4810000006
17613
17264
200
text/plain
Font
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
http/1.1
1580.6250000023
1826.9610000425
17637
17288
200
text/plain
Font
https://s.webtrends.com/js/webtrends.min.js
h2
1608.2850000239
1692.1760000405
24613
24140
200
application/javascript
Script
https://www.senate.gov/resources/images/slide-bg-active.png
http/1.1
1630.2330000326
1707.0300000487
569
256
200
image/png
Image
https://www.senate.gov/resources/images/slide-bg.png
http/1.1
1630.4150000215
1775.6999999983
569
256
200
image/png
Image
https://www.senate.gov/resources/images/left-arrow.png
http/1.1
1634.0039999923
1877.5690000039
16037
15721
200
image/png
Image
https://www.senate.gov/resources/images/right-arrow.png
http/1.1
1634.1750000138
1725.9080000222
16053
15737
200
image/png
Image
https://www.senate.gov/wt_sdc/webtrends.getcg.js
http/1.1
1698.4790000133
2063.7410000199
826
1140
200
text/javascript
Script
https://s.webtrends.com/js/advancedLinkTracking.js
h2
1698.9290000056
1792.4249999924
33546
33073
200
application/javascript
Script
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/wtid.js?callback=Webtrends.dcss.dcsobj_0.dcsGetIdCallback
h2
1700.593000045
1785.3790000081
414
201
200
application/x-javascript
Script
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/dcs.gif?&dcsdat=1623949188418&dcssip=www.senate.gov&dcsuri=/&WT.tz=-7&WT.bh=9&WT.ul=en-US&WT.cd=24&WT.sr=800x600&WT.jo=No&WT.ti=U.S.%20Senate&WT.js=Yes&WT.jv=1.5&WT.ct=unknown&WT.bs=1350x940&WT.fv=Not%20enabled&WT.slv=Not%20enabled&WT.tv=10.4.14&WT.dl=0&WT.ssl=1&WT.es=www.senate.gov/&WT.ce=2&WT.vt_f_tlv=0&WT.vt_f_tlh=0&WT.vt_f_d=1&WT.vt_f_s=1&WT.vt_f_a=1&WT.vt_f=1&WT.vtvs=1623949188421&WT.vtid=55e3e482-d3bd-48bb-ba1a-8e44f4a0907b&WT.co_f=55e3e482-d3bd-48bb-ba1a-8e44f4a0907b
http/1.1
2088.4810000425
2148.2940000133
1046
0
303
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/dcs.gif?dcsredirect=126&dcstlh=0&dcstlv=0&dcsdat=1623949188418&dcssip=www.senate.gov&dcsuri=/&WT.tz=-7&WT.bh=9&WT.ul=en-US&WT.cd=24&WT.sr=800x600&WT.jo=No&WT.ti=U.S.%20Senate&WT.js=Yes&WT.jv=1.5&WT.ct=unknown&WT.bs=1350x940&WT.fv=Not%20enabled&WT.slv=Not%20enabled&WT.tv=10.4.14&WT.dl=0&WT.ssl=1&WT.es=www.senate.gov/&WT.ce=2&WT.vt_f_tlv=0&WT.vt_f_tlh=0&WT.vt_f_d=1&WT.vt_f_s=1&WT.vt_f_a=1&WT.vt_f=1&WT.vtvs=1623949188421&WT.vtid=55e3e482-d3bd-48bb-ba1a-8e44f4a0907b&WT.co_f=55e3e482-d3bd-48bb-ba1a-8e44f4a0907b
h2
2148.6370000057
2235.474999994
547
67
200
image/gif
Image
https://floor.senate.gov/ViewPublisher.php?view_id=18&callback=jsonCallback&_=1623949187886
http/1.1
2292.2210000106
2766.2200000486
462
263
200
text/html
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
763.677
9.09
776.05
6.708
1538.791
23.451
1562.253
50.883
1613.542
31.907
1669.031
16.319
1687.274
7.188
1700.575
7.45
1729.583
8.324
1778.828
6.431
1807.156
7.081
1828.681
8.01
1845.34
16.86
2061.897
19.099
2083.491
10.039
2095.361
10.877
2299.749
36.77
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Senate.gov should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Senate.gov should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/styles/boilerplate.css
3600
2216
Minify JavaScript — Potential savings of 14 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Senate.gov should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.webtrends.com/js/advancedLinkTracking.js
33546
14629
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Senate.gov should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression — Potential savings of 41 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.webtrends.com/js/advancedLinkTracking.js
33073
26253
https://s.webtrends.com/js/webtrends.min.js
24140
15520
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.senate.gov/
205.839
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Senate.gov should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 2,134 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618696
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
197028
https://www.senate.gov/resources/images/col2_senatefloor.jpg
172099
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
171482
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
165210
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
136492
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
121237
https://www.senate.gov/resources/images/33_00019.jpg
86825
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
72246
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
65115
Avoids an excessive DOM size — 559 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
559
Maximum DOM Depth
12
Maximum Child Elements
51
Avoid chaining critical requests — 18 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Senate.gov should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.senate.gov/
231.983
6.427
1.456
Unattributable
65.362
2.858
0.178
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
123.273
Other
88.862
Style & Layout
80.731
Script Evaluation
60.988
Parse HTML & CSS
19.209
Script Parsing & Compilation
9.21
Keep request counts low and transfer sizes small — 50 requests • 2,134 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
50
2185486
Image
21
1902494
Font
5
143074
Script
11
100779
Stylesheet
9
29027
Document
1
8570
Other
3
1542
Media
0
0
Third-party
5
60166
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
60166
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0.145
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.5 s
The time taken for the primary content of the page to be rendered.

Opportunities

Properly size images — Potential savings of 250 KiB
Images can slow down the page's load time. Senate.gov should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
150653
https://www.senate.gov/resources/images/33_00019.jpg
86507
75868
https://www.senate.gov/resources/graphic/history_lbj.jpg
33329
29230
Efficiently encode images — Potential savings of 703 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618377
615597
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
196709
95787
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
8768
Serve images in next-gen formats — Potential savings of 1,018 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618377
617559
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
196709
148409
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
171163
34667
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
33852
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
136173
29593
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
64798
28310
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
164891
28125
https://www.senate.gov/resources/images/banner-bg.png
24274
21204
https://www.senate.gov/resources/images/33_00019.jpg
86507
21151
https://www.senate.gov/resources/images/usFlag.png
17276
16862
https://www.senate.gov/resources/images/senate_logo_footer.png
20930
15908
https://www.senate.gov/resources/images/right-arrow.png
15737
15549
https://www.senate.gov/resources/images/left-arrow.png
15721
15527
https://www.senate.gov/resources/images/bkgnd_stripe_c.png
15461
15395
Avoid multiple page redirects — Potential savings of 380 ms
Redirects can cause additional delays before the page can begin loading. Senate.gov should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://senate.gov/
190
http://www.senate.gov/
190
https://www.senate.gov/
0

Metrics

Speed Index — 2.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.7 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,010 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Senate.gov should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.senate.gov/resources/styles/boilerplate.css
3600
70
https://www.senate.gov/resources/styles/main.css
7713
190
https://www.senate.gov/resources/styles/nav_menu.css
4223
150
https://www.senate.gov/resources/styles/skdslider.css
1969
150
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
1145
150
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
1145
150
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
1145
70
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
7028
70
https://www.senate.gov/resources/styles/print.css
1059
70
https://www.senate.gov/resources/scripts/respond.min.js
2080
70
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
33724
190
https://www.senate.gov/resources/scripts/skdslider.min.js
2040
70
https://www.senate.gov/resources/scripts/main.js
1323
70
https://www.senate.gov/resources/scripts/floor_status.js
790
70

Diagnostics

Serve static assets with an efficient cache policy — 44 resources found
Senate.gov can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
0
618696
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
0
197028
https://www.senate.gov/resources/images/col2_senatefloor.jpg
0
172099
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
0
171482
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
0
165210
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
0
136492
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
0
121237
https://www.senate.gov/resources/images/33_00019.jpg
0
86825
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
0
72246
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
0
65115
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
0
33724
https://www.senate.gov/resources/graphic/history_lbj.jpg
0
33646
https://s.webtrends.com/js/advancedLinkTracking.js
0
33546
https://s.webtrends.com/js/webtrends.min.js
0
24613
https://www.senate.gov/resources/images/banner-bg.png
0
24590
https://www.senate.gov/resources/images/senate_logo_footer.png
0
21246
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
0
17849
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
0
17729
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
0
17637
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
0
17613
https://www.senate.gov/resources/images/usFlag.png
0
17592
https://www.senate.gov/resources/images/right-arrow.png
0
16053
https://www.senate.gov/resources/images/left-arrow.png
0
16037
https://www.senate.gov/resources/images/bkgnd_stripe_c.png
0
15777
https://www.senate.gov/resources/images/senate_logo.png
0
11125
https://www.senate.gov/resources/images/senate_logo_black.png
0
10559
https://www.senate.gov/resources/styles/main.css
0
7713
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
0
7028
https://www.senate.gov/resources/styles/nav_menu.css
0
4223
https://www.senate.gov/resources/styles/boilerplate.css
0
3600
https://www.senate.gov/resources/scripts/respond.min.js
0
2080
https://www.senate.gov/resources/scripts/skdslider.min.js
0
2040
https://www.senate.gov/resources/styles/skdslider.css
0
1969
https://www.senate.gov/resources/scripts/main.js
0
1323
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
0
1145
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
0
1145
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
0
1145
https://www.senate.gov/resources/styles/print.css
0
1059
https://www.senate.gov/wt_sdc/central_webtrends.load.js
0
961
https://www.senate.gov/wt_sdc/webtrends.getcg.js
0
826
https://www.senate.gov/resources/scripts/floor_status.js
0
790
https://www.senate.gov/resources/images/slide-bg-active.png
0
569
https://www.senate.gov/resources/images/slide-bg.png
0
569
https://floor.senate.gov/ViewPublisher.php?view_id=18&callback=jsonCallback&_=1623949187886
0
462
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
84.357000014279
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
222.34599996591
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
185.32200000482
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
88.854999979958
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
246.33600004017
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
img
https://www.senate.gov/resources/images/col2_senatefloor.jpg
img
https://www.senate.gov/resources/images/33_00019.jpg
img
https://www.senate.gov/resources/graphic/history_lbj.jpg
img
https://www.senate.gov/resources/images/senate_logo_footer.png
https://www.senate.gov/resources/images/usFlag.png
https://www.senate.gov/resources/images/senate_logo.png
61

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of senate.gov. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Senate.gov may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that senate.gov should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
https://www.senate.gov/resources/scripts/jquery.min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://senate.gov/
Allowed
http://www.senate.gov/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
55

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for senate.gov. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of senate.gov on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 2 links found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 523 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
2
<!-- [if lt IE 7]> <html class="ie6 oldie"> <![endif] -->
Syntax not understood
3
<!-- [if IE 7]> <html class="ie7 oldie"> <![endif] -->
Syntax not understood
4
<!-- [if IE 8]> <html class="ie8 oldie"> <![endif] -->
Syntax not understood
5
<!-- [if gt IE 8]> <! --><html class="">
Syntax not understood
6
<!-- <![endif] -->
Syntax not understood
7
<head>
Syntax not understood
8
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
Syntax not understood
9
<meta charset="UTF-8">
Syntax not understood
10
<meta content="width=device-width, initial-scale=1" name="viewport">
Syntax not understood
11
<meta name="object" content="file_not_found">
Syntax not understood
12
<meta name="version" content="7.1">
Syntax not understood
13
<meta name="path" content="/Senate.gov/pagelayout/general/one_item_and_teasers">
Syntax not understood
14
<meta name="date" content="Thursday, January 19, 2017">
Syntax not understood
15
<meta name="time" content="9:56:09 AM EST">
Unknown directive
16
<meta name="keywords" content="">
Syntax not understood
17
<meta name="bucket" content="art">
Syntax not understood
18
<meta name="description" content="404 Error Page">
Syntax not understood
19
<title>U.S. Senate: 404 Error Page</title>
Unknown directive
20
<link type="image/x-icon" href="/resources/images/us_sen.ico" rel="shortcut icon">
Syntax not understood
21
<link type="text/css" rel="stylesheet" href="/resources/styles/boilerplate.css">
Syntax not understood
22
<link type="text/css" rel="stylesheet" href="/resources/styles/main.css">
Syntax not understood
23
<link type="text/css" rel="stylesheet" href="/resources/styles/nav_menu.css">
Syntax not understood
24
<link type="text/css" rel="stylesheet" href="/resources/styles/skdslider.css">
Syntax not understood
25
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic">
Unknown directive
26
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700">
Unknown directive
27
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700">
Unknown directive
28
<link href="/resources/fonts/css/font-awesome.min.css" rel="stylesheet">
Syntax not understood
29
<link type="text/css" rel="stylesheet" href="/resources/styles/print.css">
Syntax not understood
30
<link type="text/css" rel="stylesheet" href="/resources/styles/content.css">
Syntax not understood
31
<!-- [if lt IE 9]> <script src="/resources/scripts/html5shiv.js"></script> <![endif] -->
Syntax not understood
33
<script type="text/javascript">
Syntax not understood
35
function MM_goToURL() { //v3.0
Syntax not understood
36
var i, args=MM_goToURL.arguments; document.MM_returnValue = false;
Syntax not understood
37
for (i=0; i<(args.length-1); i+=2) eval(args[i]+".location='"+args[i+1]+"'");
Syntax not understood
38
}
Syntax not understood
40
</script>
Syntax not understood
41
<script type="text/javascript">
Syntax not understood
42
function MM_jumpMenu(targ,selObj,restore){ //v3.0
Syntax not understood
43
eval(targ+".location='"+selObj.options[selObj.selectedIndex].value+"'");
Syntax not understood
44
if (restore) selObj.selectedIndex=0;
Syntax not understood
45
}
Syntax not understood
46
</script><script src="/resources/scripts/jquery-1.11.3.min.js"></script><script src="/resources/scripts/skdslider.min.js"></script><script src="/resources/scripts/main.js"></script><script type="text/javascript">
Syntax not understood
47
jQuery(document).ready(function(){
Syntax not understood
48
jQuery('#slider').skdslider({delay:5000, animationSpeed: 2000,showNextPrev:true,showPlayButton:true,autoSlide:true,animationType:'fading'});
Syntax not understood
50
jQuery('#responsive').change(function(){
Syntax not understood
51
$('#responsive_wrapper').width(jQuery(this).val());
Syntax not understood
52
$(window).trigger('resize');
Syntax not understood
53
});
Syntax not understood
55
});
Syntax not understood
56
</script><script src="/resources/scripts/floor_status.js"></script>
Syntax not understood
57
</head>
Syntax not understood
58
<body onload="myFunction()">
Syntax not understood
59
<header class="mobilehead clearfix">
Syntax not understood
60
<div id="top-header">
Syntax not understood
61
<CFPARAM NAME="URL.q" DEFAULT="">
Syntax not understood
62
<div id="find-sen" class="row">
Syntax not understood
63
<div id="flag" class="fluid "><img src="/resources/images/usFlag.png" alt="U.S. Flag" /></div>
Syntax not understood
64
<div id="sen-dropdown-container" class="fluid ">
Syntax not understood
65
<form name="findSenators" method="post">
Syntax not understood
66
<label for="findsenator" />
Syntax not understood
67
<select name="stateName" class="arrow" id="findsenator" onChange="MM_jumpMenu('parent',this,0)">
Syntax not understood
68
<option value="/states/">Find Your Senators</option>
Syntax not understood
69
<option value="/states/AL/intro.htm">Alabama</option>
Syntax not understood
70
<option value="/states/AK/intro.htm">Alaska</option>
Syntax not understood
71
<option value="/states/AZ/intro.htm">Arizona</option>
Syntax not understood
72
<option value="/states/AR/intro.htm">Arkansas</option>
Syntax not understood
73
<option value="/states/CA/intro.htm">California</option>
Syntax not understood
74
<option value="/states/CO/intro.htm">Colorado</option>
Syntax not understood
75
<option value="/states/CT/intro.htm">Connecticut</option>
Syntax not understood
76
<option value="/states/DE/intro.htm">Delaware</option>
Syntax not understood
77
<option value="/states/FL/intro.htm">Florida</option>
Syntax not understood
78
<option value="/states/GA/intro.htm">Georgia</option>
Syntax not understood
79
<option value="/states/HI/intro.htm">Hawaii</option>
Syntax not understood
80
<option value="/states/ID/intro.htm">Idaho</option>
Syntax not understood
81
<option value="/states/IL/intro.htm">Illinois</option>
Syntax not understood
82
<option value="/states/IN/intro.htm">Indiana</option>
Syntax not understood
83
<option value="/states/IA/intro.htm">Iowa</option>
Syntax not understood
84
<option value="/states/KS/intro.htm">Kansas</option>
Syntax not understood
85
<option value="/states/KY/intro.htm">Kentucky</option>
Syntax not understood
86
<option value="/states/LA/intro.htm">Louisiana</option>
Syntax not understood
87
<option value="/states/ME/intro.htm">Maine</option>
Syntax not understood
88
<option value="/states/MD/intro.htm">Maryland</option>
Syntax not understood
89
<option value="/states/MA/intro.htm">Massachusetts</option>
Syntax not understood
90
<option value="/states/MI/intro.htm">Michigan</option>
Syntax not understood
91
<option value="/states/MN/intro.htm">Minnesota</option>
Syntax not understood
92
<option value="/states/MS/intro.htm">Mississippi</option>
Syntax not understood
93
<option value="/states/MO/intro.htm">Missouri</option>
Syntax not understood
94
<option value="/states/MT/intro.htm">Montana</option>
Syntax not understood
95
<option value="/states/NE/intro.htm">Nebraska</option>
Syntax not understood
96
<option value="/states/NV/intro.htm">Nevada</option>
Syntax not understood
97
<option value="/states/NH/intro.htm">New Hampshire</option>
Syntax not understood
98
<option value="/states/NJ/intro.htm">New Jersey</option>
Syntax not understood
99
<option value="/states/NM/intro.htm">New Mexico</option>
Syntax not understood
100
<option value="/states/NY/intro.htm">New York</option>
Syntax not understood
101
<option value="/states/NC/intro.htm">North Carolina</option>
Syntax not understood
102
<option value="/states/ND/intro.htm">North Dakota</option>
Syntax not understood
103
<option value="/states/OH/intro.htm">Ohio</option>
Syntax not understood
104
<option value="/states/OK/intro.htm">Oklahoma</option>
Syntax not understood
105
<option value="/states/OR/intro.htm">Oregon</option>
Syntax not understood
106
<option value="/states/PA/intro.htm">Pennsylvania</option>
Syntax not understood
107
<option value="/states/RI/intro.htm">Rhode Island</option>
Syntax not understood
108
<option value="/states/SC/intro.htm">South Carolina</option>
Syntax not understood
109
<option value="/states/SD/intro.htm">South Dakota</option>
Syntax not understood
110
<option value="/states/TN/intro.htm">Tennessee</option>
Syntax not understood
111
<option value="/states/TX/intro.htm">Texas</option>
Syntax not understood
112
<option value="/states/UT/intro.htm">Utah</option>
Syntax not understood
113
<option value="/states/VT/intro.htm">Vermont</option>
Syntax not understood
114
<option value="/states/VA/intro.htm">Virginia</option>
Syntax not understood
115
<option value="/states/WA/intro.htm">Washington</option>
Syntax not understood
116
<option value="/states/WV/intro.htm">West Virginia</option>
Syntax not understood
117
<option value="/states/WI/intro.htm">Wisconsin</option>
Syntax not understood
118
<option value="/states/WY/intro.htm">Wyoming</option>
Syntax not understood
119
</select>
Syntax not understood
120
</form>
Syntax not understood
121
</div>
Syntax not understood
122
<div id="watch" class="fluid">
Syntax not understood
123
<div class="fluid watch_text"><span class="fa fa-video-camera"></span>&nbsp;&nbsp;<a id="floorlink" target="_blank"><span id="contentdata"></span></a></div>
Syntax not understood
124
</div>
Syntax not understood
125
</div>
Syntax not understood
126
</div>
Syntax not understood
127
</div>
Syntax not understood
129
<div id="main-header">
Syntax not understood
130
<div class="row">
Syntax not understood
132
<div id="logo">
Syntax not understood
133
<a href="/index.htm"><img src="/resources/images/senate_logo.png" alt="United States Senate Logo" border="0"/></a>
Syntax not understood
134
</div>
Syntax not understood
136
<div id="search-elements" class="fluid ">
Syntax not understood
137
<form name="search" id="search" action="/general/search/search_central_solr.cfm" method="GET">
Syntax not understood
138
<label for="search"><span class="fa fa-search" onClick="document.getElementById('search').submit();"></span></label>
Syntax not understood
139
<input type="text" name="q" value="Search" id="search3" onfocus="this.value=''" />
Syntax not understood
140
<!--commented out by betty<input type="hidden" value="1" name="col" />
Syntax not understood
141
<INPUT type="hidden" name="xsl" value="xml" />-->
Syntax not understood
142
<!--<input type="text" name="q" value="Search" id="search" onfocus="this.value=''" />
Syntax not understood
143
<input type="hidden" name="site" value="default_collection" />
Syntax not understood
144
<input type="hidden" name="num" value="10" />
Syntax not understood
145
<INPUT type="hidden" name="filter" value="0" />-->
Syntax not understood
146
</form>
Syntax not understood
149
<!--solr search section starts
Syntax not understood
150
<form method="GET" action="/general/search/search_central_solr.cfm" name="search" style="display: inline;">
Unknown directive
151
<input type="text" onFocus="this.value=&apos;&apos;" class="searchBox" id="search3" value="<CFOUTPUT>#URL.q#</CFOUTPUT>" name="q"/>
Syntax not understood
152
<input type="image" align="absmiddle" alt="GO" src="/resources/images/uss_button_go.gif"/>
Syntax not understood
153
</form>
Syntax not understood
154
solr search section ends-->
Syntax not understood
155
</div>
Syntax not understood
157
</div>
Syntax not understood
158
</div>
Syntax not understood
160
<div class="nav">
Syntax not understood
161
<div id="nav-head-bg"></div>
Syntax not understood
162
<div class="row">
Syntax not understood
163
<nav class="fluid " id="main-nav">
Syntax not understood
164
<label class="toggle" for="drop">MENU<span class="fa fa-bars"></span></label><input id="drop" type="checkbox">
Syntax not understood
165
<ul class="menu">
Syntax not understood
166
<li class="senatorsmenu">
Syntax not understood
167
<label class="plus-minus mobile-plus" for="drop-1"></label><a href="/senators/contact/">
Syntax not understood
168
SENATORS</a>
Syntax not understood
169
<input type="checkbox" id="drop-1"/>
Syntax not understood
170
<ul class="senatorsmenusub">
Syntax not understood
171
<li><a href="/senators/senators-contact.htm">Contact</a></li>
Syntax not understood
172
<li><a href="/senators/leadership.htm">Leadership</a></li>
Syntax not understood
173
<li><a href="/senators/former_senators.htm">Former Senators</a></li>
Syntax not understood
174
<li><a href="/senators/qualifications_termsofservice.htm">Qualifications &amp; Terms of Service</a></li>
Syntax not understood
175
<li><a href="/senators/facts_milestones.htm">Facts &amp; Milestones</a></li>
Syntax not understood
177
<li><a href="/states/statesmap.htm">States</a></li>
Syntax not understood
178
</ul>
Syntax not understood
179
</li>
Syntax not understood
180
<li class="committeesmenu">
Syntax not understood
181
<label class="plus-minus mobile-plus" for="drop-2"></label><a href="/committees/committees_home.htm">
Syntax not understood
182
COMMITTEES</a>
Syntax not understood
183
<input type="checkbox" id="drop-2"/>
Syntax not understood
184
<ul class="committeesmenusub">
Syntax not understood
185
<li><a href="/committees/membership_assignments.htm">Membership &amp; Assignments </a></li>
Syntax not understood
186
<li><a href="/committees/hearings_meetings.htm">Hearings &amp; Meetings</a></li>
Syntax not understood
187
<li><a href="/committees/history.htm">History</a></li>
Syntax not understood
188
</ul>
Syntax not understood
189
</li>
Syntax not understood
190
<li class="legislationmenu">
Syntax not understood
191
<label class="plus-minus mobile-plus" for="drop-3"></label><a href="/legislative/legislative_home.htm">
Syntax not understood
192
LEGISLATION &amp; RECORDS</a>
Syntax not understood
193
<input type="checkbox" id="drop-3"/>
Syntax not understood
194
<ul class="legislationmenusub">
Syntax not understood
195
<li><a href="/legislative/bills_acts_laws.htm">Bills, Acts, &amp; Laws</a></li>
Syntax not understood
196
<li><a href="/legislative/nominations_new.htm">Nominations</a></li>
Syntax not understood
197
<li><a href="/legislative/treaties_new.htm">Treaties</a></li>
Syntax not understood
198
<li><a href="/legislative/votes_new.htm">Votes</a></li>
Syntax not understood
199
<li><a href="/legislative/floor_activity_pail.htm">Floor Proceedings</a></li>
Syntax not understood
200
<li><a href="/legislative/rules_procedure.htm">Rules &amp; Procedure</a></li>
Syntax not understood
201
<li><a href="/legislative/landmark_legislation.htm">Landmark Legislation</a></li>
Syntax not understood
202
<li><a href="/legislative/sessions_of_congress.htm">Sessions of Congress</a></li>
Syntax not understood
204
<li><a href="/legislative/lobbyingdisc.htm#lobbyingdisc=lda">Public Disclosure</a></li>
Syntax not understood
205
</ul>
Syntax not understood
206
</li>
Syntax not understood
207
<li class="artmenu">
Syntax not understood
208
<label class="plus-minus mobile-plus" for="drop-4"></label><a href="/art/art_hist_home.htm">
Syntax not understood
209
ART &amp; HISTORY</a>
Syntax not understood
210
<input type="checkbox" id="drop-4"/>
Syntax not understood
211
<ul class="artmenusub">
Syntax not understood
212
<li>
Syntax not understood
213
<label for="drop-44" class="plus-minus mobile-plus"> </label>
Syntax not understood
214
<a class="drop-link" href="/history/people.htm">People</a>
Syntax not understood
215
<input type="checkbox" id="drop-44"/>
Syntax not understood
216
<ul class="tertiary-menu">
Syntax not understood
217
<li><a href="/history/officers.htm">Officers &amp; Staff</a></li>
Syntax not understood
218
<li><a href="/history/leader.htm">Party Leadership</a></li>
Syntax not understood
219
<li><a href="/history/senators.htm">Senators</a></li>
Syntax not understood
220
<li><a href="/history/featured_biographies.htm">Featured Biographies</a></li>
Syntax not understood
221
</ul>
Syntax not understood
223
</li>
Syntax not understood
224
<li>
Syntax not understood
225
<label for="drop-45" class="plus-minus mobile-plus"> </label>
Syntax not understood
226
<a class="drop-link" href="/about/powers-procedures.htm">Powers &amp; Procedures</a>
Syntax not understood
227
<input type="checkbox" id="drop-45"/>
Syntax not understood
228
<ul class="tertiary-menu">
Syntax not understood
229
<li><a href="/about/powers-procedures/censure.htm">Censure</a></li>
Syntax not understood
230
<li><a href="/about/powers-procedures/declarations-of-war.htm">Declarations of War</a></li>
Syntax not understood
231
<li><a href="/about/powers-procedures/expulsion.htm">Expulsion</a></li>
Syntax not understood
232
<li><a href="/about/powers-procedures/filibusters-cloture.htm">Filibusters &amp; Cloture</a></li>
Syntax not understood
233
<li><a href="/about/powers-procedures/impeachment.htm">Impeachment</a></li>
Syntax not understood
234
<li><a href="/about/powers-procedures/investigations.htm">Investigations</a></li>
Syntax not understood
235
<li><a href="/about/powers-procedures/nominations.htm">Nominations</a></li>
Syntax not understood
236
<li><a href="/about/powers-procedures/rules.htm">Rules</a></li>
Syntax not understood
237
<li><a href="/about/powers-procedures/treaties.htm">Treaties</a></li>
Syntax not understood
238
<li><a href="/about/powers-procedures/voting.htm">Voting</a></li>
Syntax not understood
239
</ul>
Syntax not understood
241
</li>
Syntax not understood
242
<li>
Syntax not understood
243
<label for="drop-46" class="plus-minus mobile-plus"> </label>
Syntax not understood
244
<a class="drop-link" href="/history/origins.htm">Institution</a>
Syntax not understood
245
<input type="checkbox" id="drop-46"/>
Syntax not understood
246
<ul class="tertiary-menu">
Syntax not understood
247
<li><a href="/history/instdev.htm">Origins &amp; Development</a></li>
Syntax not understood
248
<!-- <li><a href="/history/powers.htm">Powers &amp; Procedures</a></li>-->
Syntax not understood
249
<li><a href="/history/chronology.htm#chronology=y1787_1800">Chronology</a></li>
Syntax not understood
250
<li><a href="/history/partydiv.htm">Party Division</a></li>
Syntax not understood
251
</ul>
Syntax not understood
253
</li>
Syntax not understood
254
<li>
Syntax not understood
255
<label for="drop-47" class="plus-minus mobile-plus"> </label>
Syntax not understood
256
<a class="drop-link" href="/history/essays.htm">Historical Highlights</a>
Syntax not understood
257
<input type="checkbox" id="drop-47"/>
Syntax not understood
258
<ul class="tertiary-menu">
Syntax not understood
259
<li><a href="/history/1787.htm">1787-1800</a></li>
Syntax not understood
260
<li><a href="/history/1801.htm">1801-1850</a></li>
Syntax not understood
261
<li><a href="/history/1851.htm">1851-1877</a></li>
Syntax not understood
262
<li><a href="/history/1878.htm">1878-1920</a></li>
Syntax not understood
263
<li><a href="/history/1921.htm">1921-1940</a></li>
Syntax not understood
264
<li><a href="/history/1941.htm">1941-1963</a></li>
Syntax not understood
265
<li><a href="/history/1964.htm">1964-present</a></li>
Syntax not understood
266
</ul>
Syntax not understood
267
</li>
Syntax not understood
268
<li><a class="drop-link" href="/history/oralhistory.htm">Oral History Project</a> </li>
Syntax not understood
269
<li><a href="/art/exhibits.htm">Special Features</a></li>
Syntax not understood
270
<!-- <li><a href="/art/paintings.htm">Paintings</a></li>
Syntax not understood
271
<li><a href="/art/sculpture.htm">Sculpture</a></li>
Syntax not understood
272
<li><a href="/art/graphicarts.htm">Prints, Drawings &amp; Photographs</a></li>
Syntax not understood
273
<li><a href="/art/collections.htm">Furniture & Decorative Art</a></li>
Syntax not understood
274
<li><a href="/art/ephemera.htm">Ephemera & Historical Objects</a></li>-->
Syntax not understood
275
<li><a href="/art-artifacts/art-artifacts.htm">Art &amp; Artifacts</a></li>
Syntax not understood
278
</ul>
Syntax not understood
279
</li>
Syntax not understood
280
<li class="referencemenu">
Syntax not understood
281
<label class="plus-minus mobile-plus" for="drop-5"></label><a href="/reference/reference_home.htm">
Syntax not understood
282
REFERENCE</a>
Syntax not understood
283
<input type="checkbox" id="drop-5"/>
Syntax not understood
284
<ul class="referencemenusub">
Syntax not understood
285
<li><a href="/reference/virtual.htm">Virtual Reference Desk</a></li>
Syntax not understood
286
<li><a href="/reference/stats_and_lists.htm">Statistics &amp; Lists</a></li>
Syntax not understood
287
<li><a href="/reference/biblio.htm">Bibliographies</a></li>
Syntax not understood
288
<li><a href="/reference/howto.htm">How To...</a></li>
Syntax not understood
289
<li><a href="/reference/glossary.htm">Glossary</a></li>
Syntax not understood
290
<li><a href="/reference/org_chart.htm">Senate Organization</a></li>
Syntax not understood
291
<li><a href="/civics/constitution_item/constitution.htm">The Constitution</a></li>
Syntax not understood
292
<li><a href="/visiting/procurement.htm">Procurement</a></li>
Syntax not understood
293
<li>
Syntax not understood
294
<label for="drop-55" class="plus-minus mobile-plus"> </label>
Syntax not understood
295
<a class="drop-link" href="/visiting/employment.htm">Employment &amp; Internships</a>
Syntax not understood
296
<input type="checkbox" id="drop-55"/>
Syntax not understood
297
<ul class="tertiary-menu">
Syntax not understood
298
<li><a href="/visiting/po.htm">Placement Office</a></li>
Syntax not understood
299
<li><a href="/employment/saa/positions.htm">Sergeant at Arms</a></li>
Syntax not understood
300
<li><a href="/employment/SOS_HR/positions_sos.htm">Secretary of the Senate</a></li>
Syntax not understood
301
</ul>
Syntax not understood
302
</li>
Syntax not understood
303
<li><a href="/visiting/index.htm">Visiting</a></li>
Syntax not understood
304
</ul>
Syntax not understood
305
</li>
Syntax not understood
306
</ul>
Syntax not understood
307
</nav>
Syntax not understood
308
</div>
Syntax not understood
309
</div>
Syntax not understood
310
</header>
Syntax not understood
311
<div id="watch_mobile" class="fluid watch_text"><span class="fa fa-video-camera"></span>&nbsp;&nbsp;<a id="floorlink_mobile" target="_blank"><span id="contentdata_mobile"></span></a></div>
Syntax not understood
312
<main class="gridContainer clearfix">
Syntax not understood
313
<div class="fluid" id="secondary_col2">
Syntax not understood
314
<section class="fluid " id="art_history_header">
Syntax not understood
315
<h1>404 Error Page</h1>
Syntax not understood
316
<div id="h1_action_icons" class="fluid"><a href="javascript:if(window.print)window.print()"><i class="fa fa-print"></i></a>
Unknown directive
317
<!--<a href="index.html"><i class="fa fa-share"></i></a>-->
Syntax not understood
318
</div>
Syntax not understood
319
<hr class="fluid">
Syntax not understood
320
</section>
Syntax not understood
321
<!--
Syntax not understood
322
BEGIN MAIN
Syntax not understood
323
-->
Syntax not understood
324
<P align="center" class="contenttitle"><FONT size="+1">Requested Page Not Found (404).</FONT>
Syntax not understood
325
<hr />
Syntax not understood
328
<ul class="contenttext" style="margin-top: 0px; margin-left: 0px; padding-top: 0px; padding-left: 0 px;">
Unknown directive
329
<p>&#160;</p>
Syntax not understood
330
<li><strong><label for="searchMain">Search Senate.gov:</label></strong> &#160;&#160;&#160;&#160;<form style="display: inline;" action="/general/search/search_central_solr.cfm" method="GET">
Unknown directive
331
<label for="search"><span class="fa fa-search" onClick="document.getElementById('search').submit();"></span></label>
Syntax not understood
332
<input type="text" name="q" id="search3" onfocus="this.value=''" value="Enter Search Term(s)" width="120"/>
Syntax not understood
333
<input style="vertical-align: middle; margin-bottom: .25em;" alt="GO" src="http://www.senate.gov/resources/images/uss_button_go.gif" type="image">
Unknown directive
334
</form>
Syntax not understood
337
<!--<form style="display: inline;" method="GET" action="http://www.senate.gov/general/search/search_cfm.cfm" name="searchMain">
Unknown directive
338
<input onfocus="this.value=''" style="width: 140px;" class="searchBox" id="search3" value="Enter Search Term(s)" name="q" type="text" width="120">
Unknown directive
339
<input style="vertical-align: middle; margin-bottom: .25em;" alt="GO" src="http://www.senate.gov/resources/images/uss_button_go.gif" type="image">
Unknown directive
340
<input value="default_collection" name="site" type="hidden">
Syntax not understood
341
<input value="10" name="num" type="hidden">
Syntax not understood
342
<INPUT value="0" name="filter" type="hidden">
Syntax not understood
343
</form>-->
Syntax not understood
344
</li>
Syntax not understood
345
<p>&#160;</p>
Syntax not understood
346
<li><strong><label for="findsenatorbystate">Find Senators by State:</label></strong> &#160;&#160;&#160;&#160;
Unknown directive
348
<form style="display: inline;" method="post" name="findSenatorsSearch">
Unknown directive
350
<label for="findsenator" />
Syntax not understood
352
<select style="width: 160px;" id="findsenatorbystate" name="stateName"><option value="/states/">--Select State--</option>
Unknown directive
353
<!--<option value="/states/">Find Your Senators</option>-->
Syntax not understood
354
<option value="/states/AL/intro.htm">Alabama</option>
Syntax not understood
355
<option value="/states/AK/intro.htm">Alaska</option>
Syntax not understood
356
<option value="/states/AZ/intro.htm">Arizona</option>
Syntax not understood
357
<option value="/states/AR/intro.htm">Arkansas</option>
Syntax not understood
358
<option value="/states/CA/intro.htm">California</option>
Syntax not understood
359
<option value="/states/CO/intro.htm">Colorado</option>
Syntax not understood
360
<option value="/states/CT/intro.htm">Connecticut</option>
Syntax not understood
361
<option value="/states/DE/intro.htm">Delaware</option>
Syntax not understood
362
<option value="/states/FL/intro.htm">Florida</option>
Syntax not understood
363
<option value="/states/GA/intro.htm">Georgia</option>
Syntax not understood
364
<option value="/states/HI/intro.htm">Hawaii</option>
Syntax not understood
365
<option value="/states/ID/intro.htm">Idaho</option>
Syntax not understood
366
<option value="/states/IL/intro.htm">Illinois</option>
Syntax not understood
367
<option value="/states/IN/intro.htm">Indiana</option>
Syntax not understood
368
<option value="/states/IA/intro.htm">Iowa</option>
Syntax not understood
369
<option value="/states/KS/intro.htm">Kansas</option>
Syntax not understood
370
<option value="/states/KY/intro.htm">Kentucky</option>
Syntax not understood
371
<option value="/states/LA/intro.htm">Louisiana</option>
Syntax not understood
372
<option value="/states/ME/intro.htm">Maine</option>
Syntax not understood
373
<option value="/states/MD/intro.htm">Maryland</option>
Syntax not understood
374
<option value="/states/MA/intro.htm">Massachusetts</option>
Syntax not understood
375
<option value="/states/MI/intro.htm">Michigan</option>
Syntax not understood
376
<option value="/states/MN/intro.htm">Minnesota</option>
Syntax not understood
377
<option value="/states/MS/intro.htm">Mississippi</option>
Syntax not understood
378
<option value="/states/MO/intro.htm">Missouri</option>
Syntax not understood
379
<option value="/states/MT/intro.htm">Montana</option>
Syntax not understood
380
<option value="/states/NE/intro.htm">Nebraska</option>
Syntax not understood
381
<option value="/states/NV/intro.htm">Nevada</option>
Syntax not understood
382
<option value="/states/NH/intro.htm">New Hampshire</option>
Syntax not understood
383
<option value="/states/NJ/intro.htm">New Jersey</option>
Syntax not understood
384
<option value="/states/NM/intro.htm">New Mexico</option>
Syntax not understood
385
<option value="/states/NY/intro.htm">New York</option>
Syntax not understood
386
<option value="/states/NC/intro.htm">North Carolina</option>
Syntax not understood
387
<option value="/states/ND/intro.htm">North Dakota</option>
Syntax not understood
388
<option value="/states/OH/intro.htm">Ohio</option>
Syntax not understood
389
<option value="/states/OK/intro.htm">Oklahoma</option>
Syntax not understood
390
<option value="/states/OR/intro.htm">Oregon</option>
Syntax not understood
391
<option value="/states/PA/intro.htm">Pennsylvania</option>
Syntax not understood
392
<option value="/states/RI/intro.htm">Rhode Island</option>
Syntax not understood
393
<option value="/states/SC/intro.htm">South Carolina</option>
Syntax not understood
394
<option value="/states/SD/intro.htm">South Dakota</option>
Syntax not understood
395
<option value="/states/TN/intro.htm">Tennessee</option>
Syntax not understood
396
<option value="/states/TX/intro.htm">Texas</option>
Syntax not understood
397
<option value="/states/UT/intro.htm">Utah</option>
Syntax not understood
398
<option value="/states/VT/intro.htm">Vermont</option>
Syntax not understood
399
<option value="/states/VA/intro.htm">Virginia</option>
Syntax not understood
400
<option value="/states/WA/intro.htm">Washington</option>
Syntax not understood
401
<option value="/states/WV/intro.htm">West Virginia</option>
Syntax not understood
402
<option value="/states/WI/intro.htm">Wisconsin</option>
Syntax not understood
403
<option value="/states/WY/intro.htm">Wyoming</option>
Syntax not understood
404
</select>
Syntax not understood
405
<a href="#"><img alt="GO" align="absmiddle" src="/resources/images/uss_button_go.gif" onClick="location=findSenators.findsenator.options[findSenatorsSearch.findsenatorbystate.selectedIndex].value" style="vertical-align: middle; margin-bottom: .25em; border-style: none; link-style: none; border-thickness: 0px;"></a>
Syntax not understood
406
</form>
Syntax not understood
411
<!-- <form style="display: inline;" method="post" name="findSenatorsSearch">
Unknown directive
412
<select style="width: 160px;" class="searchBox" id="findsenatorbystate" name="stateName"><option value="/general/contact_information/senators_cfm.cfm">--Select State--</option><option value="/general/contact_information/senators_cfm.cfm?State=AL">Alabama</option><option value="/general/contact_information/senators_cfm.cfm?State=AK">Alaska</option><option value="/general/contact_information/senators_cfm.cfm?State=AZ">Arizona</option><option value="/general/contact_information/senators_cfm.cfm?State=AR">Arkansas</option><option value="/general/contact_information/senators_cfm.cfm?State=CA">California</option><option value="/general/contact_information/senators_cfm.cfm?State=CO">Colorado</option><option value="/general/contact_information/senators_cfm.cfm?State=CT">Connecticut</option><option value="/general/contact_information/senators_cfm.cfm?State=DE">Delaware</option><option value="/general/contact_information/senators_cfm.cfm?State=FL">Florida</option><option value="/general/contact_information/senators_cfm.cfm?State=GA">Georgia</option><option value="/general/contact_information/senators_cfm.cfm?State=HI">Hawaii</option><option value="/general/contact_information/senators_cfm.cfm?State=ID">Idaho</option><option value="/general/contact_information/senators_cfm.cfm?State=IL">Illinois</option><option value="/general/contact_information/senators_cfm.cfm?State=IN">Indiana</option><option value="/general/contact_information/senators_cfm.cfm?State=IA">Iowa</option><option value="/general/contact_information/senators_cfm.cfm?State=KS">Kansas</option><option value="/general/contact_information/senators_cfm.cfm?State=KY">Kentucky</option><option value="/general/contact_information/senators_cfm.cfm?State=LA">Louisiana</option><option value="/general/contact_information/senators_cfm.cfm?State=ME">Maine</option><option value="/general/contact_information/senators_cfm.cfm?State=MD">Maryland</option><option value="/general/contact_information/senators_cfm.cfm?State=MA">Massachusetts</option><option value="/general/contact_information/senators_cfm.cfm?State=MI">Michigan</option><option value="/general/contact_information/senators_cfm.cfm?State=MN">Minnesota</option><option value="/general/contact_information/senators_cfm.cfm?State=MS">Mississippi</option><option value="/general/contact_information/senators_cfm.cfm?State=MO">Missouri</option><option value="/general/contact_information/senators_cfm.cfm?State=MT">Montana</option><option value="/general/contact_information/senators_cfm.cfm?State=NE">Nebraska</option><option value="/general/contact_information/senators_cfm.cfm?State=NV">Nevada</option><option value="/general/contact_information/senators_cfm.cfm?State=NH">New Hampshire</option><option value="/general/contact_information/senators_cfm.cfm?State=NJ">New Jersey</option><option value="/general/contact_information/senators_cfm.cfm?State=NM">New Mexico</option><option value="/general/contact_information/senators_cfm.cfm?State=NY">New York</option><option value="/general/contact_information/senators_cfm.cfm?State=NC">North Carolina</option><option value="/general/contact_information/senators_cfm.cfm?State=ND">North Dakota</option><option value="/general/contact_information/senators_cfm.cfm?State=OH">Ohio</option><option value="/general/contact_information/senators_cfm.cfm?State=OK">Oklahoma</option><option value="/general/contact_information/senators_cfm.cfm?State=OR">Oregon</option><option value="/general/contact_information/senators_cfm.cfm?State=PA">Pennsylvania</option><option value="/general/contact_information/senators_cfm.cfm?State=RI">Rhode Island</option><option value="/general/contact_information/senators_cfm.cfm?State=SC">South Carolina</option><option value="/general/contact_information/senators_cfm.cfm?State=SD">South Dakota</option><option value="/general/contact_information/senators_cfm.cfm?State=TN">Tennessee</option><option value="/general/contact_information/senators_cfm.cfm?State=TX">Texas</option><option value="/general/contact_information/senators_cfm.cfm?State=UT">Utah</option><option value="/general/contact_information/senators_cfm.cfm?State=VT">Vermont</option><option value="/general/contact_information/senators_cfm.cfm?State=VA">Virginia</option><option value="/general/contact_information/senators_cfm.cfm?State=WA">Washington</option><option value="/general/contact_information/senators_cfm.cfm?State=WV">West Virginia</option><option value="/general/contact_information/senators_cfm.cfm?State=WI">Wisconsin</option><option value="/general/contact_information/senators_cfm.cfm?State=WY">Wyoming</option></select> <a href="#"><img alt="GO" align="absmiddle" src="/resources/images/uss_button_go.gif" onClick="location=findSenators.findsenator.options[findSenatorsSearch.findsenatorbystate.selectedIndex].value" style="vertical-align: middle; margin-bottom: .25em; border-style: none; link-style: none; border-thickness: 0px;"></a>
Unknown directive
413
</form> -->
Syntax not understood
414
</li>
Syntax not understood
415
<p>&#160;</p>
Syntax not understood
416
<li><strong>Contact:</strong> E-mail <a href="mailto:webmaster@sec.senate.gov">webmaster@sec.senate.gov</a> to report a broken link, ask technical questions, or provide feedback on <a href="www.senate.gov">www.senate.gov</a>. For all other correspondence <a href="http://www.senate.gov/pagelayout/general/one_item_and_teasers/contacting.htm">contact your senators</a>.
Unknown directive
417
<br />
Syntax not understood
418
<br />
Syntax not understood
419
<span class="caption"><strong>*NOTE:</strong> Please do not ask the webmaster to forward mail to senators' offices.</li>
Unknown directive
420
</ul>
Syntax not understood
424
<table width="100%">
Syntax not understood
425
<tr>
Syntax not understood
426
<td>&nbsp;</td>
Syntax not understood
427
</tr>
Syntax not understood
428
</table>
Syntax not understood
429
<!--
Syntax not understood
430
END MAIN
Syntax not understood
431
-->
Syntax not understood
432
</div>
Syntax not understood
433
<div class="fluid" id="secondary_col1">
Syntax not understood
434
<!DOCTYPE noindex PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
435
<noindex />
Syntax not understood
437
<!--
Syntax not understood
438
BEGIN TEASERS
Syntax not understood
439
-->
Syntax not understood
440
<!--****** VRD_SiteMap Version: 4.1 was generated at: Friday, March 3, 2017: 2:45 PM EST in folder: /Senate.gov/general/common/teaser **--><aside class="fluid sidebar_link_container">
Unknown directive
441
<div class="fluid content_column_container">
Syntax not understood
442
<h3>Virtual Reference Desk </h3>
Syntax not understood
443
<span style="padding-top:5px" class="teasertext">
Unknown directive
444
<p>Browse the site by topic with the <A href="/pagelayout/reference/b_three_sections_with_teasers/virtual.htm">Virtual Reference Desk</A>.</p>
Syntax not understood
445
<p>&nbsp;</p>
Syntax not understood
446
</span>
Syntax not understood
447
</div>
Syntax not understood
448
</aside>
Syntax not understood
450
<br>
Syntax not understood
451
<!--****** FAQs.xml Version: 14.1 was generated at: Wednesday, June 27, 2018: 2:37 PM EDT in folder: /Company Home/Sites/senategov/documentLibrary/Senate.gov/general/common/teaser **--><aside class="fluid sidebar_link_container">
Unknown directive
452
<div class="fluid content_column_container">
Syntax not understood
453
<h3>Related Links </h3>
Syntax not understood
454
<span style="padding-top:5px" class="teasertext">
Unknown directive
455
<p>Frequently Asked Questions</p>
Syntax not understood
456
<p>
Syntax not understood
457
<a href="/committees/committees_faq.htm">Committees</a>
Syntax not understood
458
</p>
Syntax not understood
459
<p>
Syntax not understood
460
<a href="/pagelayout/reference/b_three_sections_with_teasers/howto.htm">Congressional Research</a>
Syntax not understood
461
</p>
Syntax not understood
462
<p>
Syntax not understood
463
<a href="/general/common/generic/NewCongress_faq.htm">New Congress</a>
Syntax not understood
464
</p>
Syntax not understood
465
<p>&nbsp;</p>
Syntax not understood
466
</span>
Syntax not understood
467
</div>
Syntax not understood
468
</aside>
Syntax not understood
470
<br>
Syntax not understood
471
<!--
Syntax not understood
472
END TEASERS
Syntax not understood
473
-->
Syntax not understood
474
</div>
Syntax not understood
475
<div id="social_background_white" class="fluid ">
Syntax not understood
476
<div id="logo_social_footer_center" class="fluid ">
Syntax not understood
477
<div id="footer_logo" class="fluid "><a href="/index.htm"><img src="/resources/images/senate_logo_footer.png" alt="Senate Logo"/></a></div>
Syntax not understood
478
</div>
Syntax not understood
479
</div>
Syntax not understood
480
</main>
Syntax not understood
481
<footer id="footer" class="fluid gridContainer clearfix">
Syntax not understood
482
<div id="footer_menu_center">
Syntax not understood
484
<div id="footer_menu_senators" >
Syntax not understood
485
<h3><a href="/senators/contact/">SENATORS</a></h3>
Syntax not understood
486
<ul class="fluid fluidList footer_links">
Syntax not understood
487
<li><a href="/senators/senators-contact.htm">Contact</a></li>
Syntax not understood
488
<li><a href="/senators/leadership.htm">Leadership &amp; Officers</a></li>
Syntax not understood
489
<li><a href="/senators/former_senators.htm">Former Senators</a></li>
Syntax not understood
490
<li><a href="/senators/qualifications_termsofservice.htm">Qualifications &amp; Terms of Service</a></li>
Syntax not understood
491
<li><a href="/senators/facts_milestones.htm">Facts &amp; Milestones</a></li>
Syntax not understood
492
<li><a href="/senators/statesmap.htm">States</a></li>
Syntax not understood
494
</ul>
Syntax not understood
496
<div id="footer_menu_committees" >
Syntax not understood
497
<h3 style="padding-top: 75px;"><a href="/committees/committees_home.htm">COMMITTEES</a></h3>
Unknown directive
498
<ul class="fluid fluidList footer_links">
Syntax not understood
499
<li><a href="/committees/membership_assignments.htm">Membership &amp; Assignments</a></li>
Syntax not understood
500
<li><a href="/committees/hearings_meetings.htm">Hearings &amp; Meetings</a></li>
Syntax not understood
501
<li><a href="/committees/history.htm">History</a></li>
Syntax not understood
502
</ul></div>
Syntax not understood
503
</div>
Syntax not understood
505
<div id="footer_menu_legislation" >
Syntax not understood
506
<h3><a href="/legislative/legislative_home.htm">LEGISLATION &amp; <br>
Syntax not understood
507
RECORDS</a></h3>
Syntax not understood
508
<ul class="fluid fluidList footer_links">
Syntax not understood
509
<li><a href="/legislative/bills_acts_laws.htm">Bills, Acts, & Laws</a></li>
Syntax not understood
510
<li><a href="/legislative/nominations_new.htm">Nominations</a></li>
Syntax not understood
511
<li><a href="/legislative/treaties_new.htm">Treaties</a></li>
Syntax not understood
512
<li><a href="/legislative/votes_new.htm">Votes</a></li>
Syntax not understood
513
<li><a href="/legislative/floor_activity_pail.htm">Floor Proceedings</a></li>
Syntax not understood
514
<li><a href="/legislative/rules_procedure.htm">Rules &amp; Procedure</a></li>
Syntax not understood
515
<li><a href="/legislative/landmark_legislation.htm">Landmark Legislation</a></li>
Syntax not understood
516
<li><a href="/legislative/sessions_of_congress.htm">Sessions of Congress</a></li>
Syntax not understood
517
<li><a href="/legislative/lobbyingdisc.htm#lobbyingdisc=lda">Public Disclosure</a></li>
Syntax not understood
519
</ul></div>
Syntax not understood
521
<div id="footer_menu_art" >
Syntax not understood
522
<h3><a href="/art/art_hist_home.htm">ART &amp; HISTORY</a></h3>
Syntax not understood
523
<ul class="fluid fluidList footer_links">
Syntax not understood
524
<li><a href="/history/people.htm">People</a></li>
Syntax not understood
525
<li><a href="/about/powers-procedures.htm">Powers &amp; Procedures</a></li>
Syntax not understood
526
<li><a href="/history/origins.htm">Institution</a></li>
Syntax not understood
527
<li><a href="/history/essays.htm">Historical Highlights</a></li>
Syntax not understood
528
<li><a href="/history/oralhistory.htm">Oral History Project</a></li>
Syntax not understood
529
<li><a href="/art-artifacts/art-artifacts.htm">Art &amp; Artifacts</a></li>
Syntax not understood
530
<li><a href="/artandhistory/senate-stories/menu.htm">Senate Stories Blog</a></li>
Syntax not understood
531
</ul></div>
Syntax not understood
533
<div id="footer_menu_reference" >
Syntax not understood
534
<h3><a href="/reference/reference_home.htm">REFERENCE</a></h3>
Syntax not understood
535
<ul class="fluid fluidList footer_links">
Syntax not understood
536
<li><a href="/reference/virtual.htm">Virtual Reference Desk</a></li>
Syntax not understood
537
<li><a href="/reference/stats_and_lists.htm">Statistics &amp; Lists</a></li>
Syntax not understood
538
<li><a href="/reference/biblio.htm">Bibliographies</a></li>
Syntax not understood
539
<li><a href="/reference/howto.htm">How To...</a></li>
Syntax not understood
540
<li><a href="/reference/glossary.htm">Glossary</a></li>
Syntax not understood
541
<li><a href="/reference/org_chart.htm">Senate Organization</a></li>
Syntax not understood
542
<li><a href="/civics/constitution_item/constitution.htm">The Constitution</a></li>
Syntax not understood
543
<li><a href="/visiting/procurement.htm">Procurement</a></li>
Syntax not understood
544
<li><a href="/visiting/employment.htm">Employment &amp; Internships</a></li>
Syntax not understood
545
<li><a href="/visiting/index.htm">Visiting</a></li>
Syntax not understood
546
</ul></div>
Syntax not understood
547
</div>
Syntax not understood
549
<div id="footer_legal" class="fluid " >
Syntax not understood
550
<p><!--<span class="speaker legal"><a href="/general/common/generic/browsealoud.htm">BrowseAloud</a></span> &nbsp; | &nbsp; -->
Syntax not understood
551
<a href="/general/contacting.htm">Contact</a> &nbsp; | &nbsp;
Syntax not understood
552
<a href="/general/content_responsibility.htm">Content Responsibility</a> &nbsp; | &nbsp;
Syntax not understood
553
<a href="/usage/internetpolicy.htm">Usage Policy</a> &nbsp; | &nbsp;
Syntax not understood
554
<a href="/general/pdf_help.htm">PDF Help</a> &nbsp; | &nbsp;
Syntax not understood
555
<a href="/general/privacy.htm">Privacy Policy</a> &nbsp; | &nbsp;
Syntax not understood
556
<a href="/index.htm">www.senate.gov</a>
Syntax not understood
557
</p>
Syntax not understood
558
</div>
Syntax not understood
559
</footer>
Syntax not understood
564
<!-- START OF SmartSource Data Collector TAG -->
Syntax not understood
565
<script src="/wt_sdc/central_webtrends.load.js" type="text/javascript"></script>
Syntax not understood
567
<noscript>
Syntax not understood
568
<div><img alt="DCSIMG" id="DCSIMG" width="1" height="1" src="//statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=10.4.0&amp;dcssip=www.senate.gov"/></div>
Syntax not understood
569
</noscript>
Syntax not understood
570
<!-- END OF SmartSource Data Collector TAG -->
Syntax not understood
573
</body>
Syntax not understood
574
</html>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
36

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of senate.gov. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of senate.gov on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 52
Performance 11
Accessibility 73
Best Practices 73
SEO 69
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.senate.gov/
Updated: 17th June, 2021

1.37 seconds
First Contentful Paint (FCP)
84%
10%
6%

0.02 seconds
First Input Delay (FID)
80%
19%
1%

Simulate loading on mobile
11

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for senate.gov. This includes details about optimizing page load times which can result in a better user experience.

Opportunities

Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Senate.gov should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/styles/boilerplate.css
3600
2216
Minify JavaScript — Potential savings of 14 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Senate.gov should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.webtrends.com/js/advancedLinkTracking.js
33546
14629
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Senate.gov should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 300 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.senate.gov/
299.143
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.senate.gov/resources/images/banner-bg.png
0

Diagnostics

Avoids enormous network payloads — Total size was 2,102 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618696
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
197028
https://www.senate.gov/resources/images/col2_senatefloor.jpg
172099
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
171482
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
165210
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
136492
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
121237
https://www.senate.gov/resources/images/33_00019.jpg
86825
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
72246
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
65115
Avoids an excessive DOM size — 559 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
559
Maximum DOM Depth
12
Maximum Child Elements
51
Avoid chaining critical requests — 18 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Senate.gov should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 46 requests • 2,102 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
46
2152227
Image
17
1869245
Font
5
143074
Script
11
100779
Stylesheet
9
29027
Document
1
8570
Other
3
1532
Media
0
0
Third-party
5
60155
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.526640625
0.27263497580522
0.069871948227866
0.04607235995857
0.045000909726975
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 15 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.senate.gov/
2382
786
https://www.senate.gov/wt_sdc/central_webtrends.load.js
10410
583
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
4380
413
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/wtid.js?callback=Webtrends.dcss.dcsobj_0.dcsGetIdCallback
13087
394
https://s.webtrends.com/js/webtrends.min.js
11923
384
Unattributable
959
365
Unattributable
3375
359
https://www.senate.gov/wt_sdc/webtrends.getcg.js
18750
353
Unattributable
1660
341
Unattributable
1324
336
https://www.senate.gov/
2053
329
Unattributable
630
329
https://www.senate.gov/
3168
207
https://www.senate.gov/
3734
194
https://www.senate.gov/
2001
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://senate.gov/
http/1.1
0
787.21599999699
222
0
301
http://www.senate.gov/
http/1.1
788.04099999252
887.33999998658
275
0
301
text/html
https://www.senate.gov/
http/1.1
888.14599998295
1186.2919999985
8570
37206
200
text/html
Document
https://www.senate.gov/resources/styles/boilerplate.css
http/1.1
1210.414000001
1588.6829999799
3600
10239
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/main.css
http/1.1
1210.6609999901
1389.3969999917
7713
46582
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/nav_menu.css
http/1.1
1210.9639999981
1388.7549999927
4223
27812
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/skdslider.css
http/1.1
1211.3379999937
1386.9039999845
1969
7476
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
http/1.1
1211.6449999739
1597.2320000001
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
http/1.1
1211.9399999792
1588.2289999863
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
http/1.1
1212.274999998
1372.9489999823
1145
3369
200
text/css
Stylesheet
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
http/1.1
1212.6209999842
1587.3519999732
7028
29067
200
text/css
Stylesheet
https://www.senate.gov/resources/styles/print.css
http/1.1
1213.0239999969
1397.8399999905
1059
2262
200
text/css
Stylesheet
https://www.senate.gov/resources/scripts/respond.min.js
http/1.1
1213.1899999804
1587.864000001
2080
3216
200
text/javascript
Script
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
http/1.1
1286.7719999922
1687.368999992
33724
95997
200
text/javascript
Script
https://www.senate.gov/resources/scripts/skdslider.min.js
http/1.1
1287.193999975
1387.7609999909
2040
5720
200
text/javascript
Script
https://www.senate.gov/resources/scripts/main.js
http/1.1
1287.5589999894
1586.5899999917
1323
2393
200
text/javascript
Script
https://www.senate.gov/resources/scripts/floor_status.js
http/1.1
1287.9189999949
1785.9139999782
790
862
200
text/javascript
Script
https://www.senate.gov/resources/images/usFlag.png
http/1.1
1804.0110000002
1905.098999996
17592
17276
200
image/png
Image
https://www.senate.gov/resources/images/senate_logo.png
http/1.1
1805.1099999866
1986.3409999816
11125
10809
200
image/png
Image
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
http/1.1
1805.554999999
2388.7819999945
197028
196709
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
http/1.1
1805.8789999923
1998.802999995
121237
120918
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
http/1.1
1806.1539999908
2110.891999997
165210
164891
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
http/1.1
1886.3079999865
2290.9499999951
136492
136173
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
http/1.1
1886.7999999784
2386.8139999977
65115
64798
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
http/1.1
1886.9739999936
2086.632999999
171482
171163
200
image/jpeg
Image
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
http/1.1
1887.2199999751
2093.7379999959
618696
618377
200
image/jpeg
Image
https://www.senate.gov/resources/images/33_00019.jpg
http/1.1
1887.4549999891
2088.3109999995
86825
86507
200
image/jpeg
Image
https://www.senate.gov/resources/images/col2_senatefloor.jpg
http/1.1
1887.6269999892
2089.6799999755
172099
171780
200
image/jpeg
Image
https://www.senate.gov/resources/graphic/history_lbj.jpg
http/1.1
1887.8529999929
2089.0749999962
33646
33329
200
image/jpeg
Image
https://www.senate.gov/resources/images/senate_logo_footer.png
http/1.1
1888.065999985
2289.3169999879
21246
20930
200
image/png
Image
https://www.senate.gov/wt_sdc/central_webtrends.load.js
http/1.1
1697.4239999836
1987.3799999768
961
1138
200
text/javascript
Script
https://www.senate.gov/resources/images/bkgnd_stripe_b.png
http/1.1
1890.7409999811
2091.4509999857
15756
15440
200
image/png
Image
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
http/1.1
1896.6429999855
2288.6339999968
17849
17500
200
text/plain
Font
https://www.senate.gov/resources/images/banner-bg.png
http/1.1
1899.1879999812
2095.4399999755
24590
24274
200
image/png
Image
https://www.senate.gov/resources/images/senate_logo_black.png
http/1.1
1901.6409999749
2090.4039999878
10559
10243
200
image/png
Image
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
http/1.1
1987.0699999738
2287.5530000019
72246
71896
200
text/plain
Font
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
http/1.1
1988.3229999978
2090.899999981
17729
17380
200
text/plain
Font
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
http/1.1
1990.4419999802
2286.540000001
17613
17264
200
text/plain
Font
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
http/1.1
1992.1689999755
2498.8739999826
17637
17288
200
text/plain
Font
https://s.webtrends.com/js/webtrends.min.js
h2
2486.745000002
2985.9579999757
24613
24140
200
application/javascript
Script
https://www.senate.gov/wt_sdc/webtrends.getcg.js
http/1.1
3098.862999992
3197.6480000012
826
1140
200
text/javascript
Script
https://s.webtrends.com/js/advancedLinkTracking.js
h2
3099.5959999855
3188.9809999848
33546
33073
200
application/javascript
Script
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/wtid.js?callback=Webtrends.dcss.dcsobj_0.dcsGetIdCallback
h2
3189.6339999803
3287.0859999966
414
201
200
application/x-javascript
Script
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/dcs.gif?&dcsdat=1623949221108&dcssip=www.senate.gov&dcsuri=/&WT.tz=-7&WT.bh=10&WT.ul=en-US&WT.cd=24&WT.sr=360x640&WT.jo=No&WT.ti=U.S.%20Senate&WT.js=Yes&WT.jv=1.5&WT.ct=unknown&WT.bs=367x653&WT.fv=Not%20enabled&WT.slv=Not%20enabled&WT.tv=10.4.14&WT.dl=0&WT.ssl=1&WT.es=www.senate.gov/&WT.ce=2&WT.vt_f_tlv=0&WT.vt_f_tlh=0&WT.vt_f_d=1&WT.vt_f_s=1&WT.vt_f_a=1&WT.vt_f=1&WT.vtvs=1623949221110&WT.vtid=dcdec176-b151-42f9-a951-f2b37e5eacd8&WT.co_f=dcdec176-b151-42f9-a951-f2b37e5eacd8
http/1.1
3391.472999996
3491.6199999861
1035
0
303
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/dcs.gif?dcsredirect=126&dcstlh=0&dcstlv=0&dcsdat=1623949221108&dcssip=www.senate.gov&dcsuri=/&WT.tz=-7&WT.bh=10&WT.ul=en-US&WT.cd=24&WT.sr=360x640&WT.jo=No&WT.ti=U.S.%20Senate&WT.js=Yes&WT.jv=1.5&WT.ct=unknown&WT.bs=367x653&WT.fv=Not%20enabled&WT.slv=Not%20enabled&WT.tv=10.4.14&WT.dl=0&WT.ssl=1&WT.es=www.senate.gov/&WT.ce=2&WT.vt_f_tlv=0&WT.vt_f_tlh=0&WT.vt_f_d=1&WT.vt_f_s=1&WT.vt_f_a=1&WT.vt_f=1&WT.vtvs=1623949221110&WT.vtid=dcdec176-b151-42f9-a951-f2b37e5eacd8&WT.co_f=dcdec176-b151-42f9-a951-f2b37e5eacd8
h2
3492.1079999767
3586.1369999766
547
67
200
image/gif
Image
https://floor.senate.gov/ViewPublisher.php?view_id=18&callback=jsonCallback&_=1623949219608
http/1.1
3591.7629999749
4093.4649999836
462
263
200
text/html
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1281.043
13.054
1298.558
82.219
1787.308
103.19
1891.841
6.99
1898.851
392.838
2294.337
82.249
2387.155
103.668
2491.924
291.283
2788.166
89.829
2889.113
97.171
2988.528
91.171
3082.103
10.267
3092.389
83.96
3181.705
96.053
3289.315
88.234
3382.5
98.569
4191.431
85.347
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images — Potential savings of 64 KiB
Images can slow down the page's load time. Senate.gov should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
38845
https://www.senate.gov/resources/images/33_00019.jpg
86507
19562
https://www.senate.gov/resources/graphic/history_lbj.jpg
33329
7537
Enable text compression — Potential savings of 41 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.webtrends.com/js/advancedLinkTracking.js
33073
26253
https://s.webtrends.com/js/webtrends.min.js
24140
15520
Preload key requests — Potential savings of 780 ms
Key requests can be preloaded by using '<link rel=preload>'. Senate.gov should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
780

Diagnostics

Reduce JavaScript execution time — 2.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.senate.gov/
2888.972
29.092
8.8
Unattributable
1974.776
17.196
1.44
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
1551.924
1160.5
9.12
https://statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/wtid.js?callback=Webtrends.dcss.dcsobj_0.dcsGetIdCallback
394.276
392.528
0.808
https://s.webtrends.com/js/webtrends.min.js
387.808
373.588
9.664
https://www.senate.gov/wt_sdc/webtrends.getcg.js
352.936
2.628
349.348

Metrics

First Contentful Paint — 4.6 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 7.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 9.4 s
The timing of the largest text or image that is painted.
Time to Interactive — 13.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,280 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 1.016
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 580 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 9105 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,730 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Senate.gov should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.senate.gov/resources/styles/boilerplate.css
3600
180
https://www.senate.gov/resources/styles/main.css
7713
630
https://www.senate.gov/resources/styles/nav_menu.css
4223
480
https://www.senate.gov/resources/styles/skdslider.css
1969
480
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
1145
480
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
1145
480
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
1145
180
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
7028
330
https://www.senate.gov/resources/styles/print.css
1059
180
https://www.senate.gov/resources/scripts/respond.min.js
2080
180
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
33724
1080
https://www.senate.gov/resources/scripts/skdslider.min.js
2040
180
https://www.senate.gov/resources/scripts/main.js
1323
180
https://www.senate.gov/resources/scripts/floor_status.js
790
180
Defer offscreen images — Potential savings of 1,439 KiB
Time to Interactive can be slowed down by resources on the page. Senate.gov should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618377
618377
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
196709
196709
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
171163
171163
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
164891
164891
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
136173
136173
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
120918
120918
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
64798
64798
Efficiently encode images — Potential savings of 703 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618377
615597
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
196709
95787
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
8768
Serve images in next-gen formats — Potential savings of 938 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
618377
617559
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
196709
148409
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
171163
34667
https://www.senate.gov/resources/images/col2_senatefloor.jpg
171780
33852
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
136173
29593
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
164891
28125
https://www.senate.gov/resources/images/senate_logo_footer.png
20930
18897
https://www.senate.gov/resources/images/usFlag.png
17276
17074
https://www.senate.gov/resources/images/33_00019.jpg
86507
17071
https://www.senate.gov/resources/images/bkgnd_stripe_b.png
15440
15420
Avoid multiple page redirects — Potential savings of 1,260 ms
Redirects can cause additional delays before the page can begin loading. Senate.gov should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://senate.gov/
630
http://www.senate.gov/
630
https://www.senate.gov/
0

Diagnostics

Serve static assets with an efficient cache policy — 40 resources found
Senate.gov can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.senate.gov/resources/images/sliderphotos/image-bg.jpg
0
618696
https://www.senate.gov/resources/images/sliderphotos/women-of-the-senate-rotator-front-page.jpg
0
197028
https://www.senate.gov/resources/images/col2_senatefloor.jpg
0
172099
https://www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg
0
171482
https://www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg
0
165210
https://www.senate.gov/resources/images/sliderphotos/Desks_homepageRotator.jpg
0
136492
https://www.senate.gov/resources/images/sliderphotos/L_IllustrationRevelsOath1870.jpg
0
121237
https://www.senate.gov/resources/images/33_00019.jpg
0
86825
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
0
72246
https://www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg
0
65115
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
0
33724
https://www.senate.gov/resources/graphic/history_lbj.jpg
0
33646
https://s.webtrends.com/js/advancedLinkTracking.js
0
33546
https://s.webtrends.com/js/webtrends.min.js
0
24613
https://www.senate.gov/resources/images/banner-bg.png
0
24590
https://www.senate.gov/resources/images/senate_logo_footer.png
0
21246
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
0
17849
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
0
17729
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
0
17637
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
0
17613
https://www.senate.gov/resources/images/usFlag.png
0
17592
https://www.senate.gov/resources/images/bkgnd_stripe_b.png
0
15756
https://www.senate.gov/resources/images/senate_logo.png
0
11125
https://www.senate.gov/resources/images/senate_logo_black.png
0
10559
https://www.senate.gov/resources/styles/main.css
0
7713
https://www.senate.gov/resources/fonts/css/font-awesome.min.css
0
7028
https://www.senate.gov/resources/styles/nav_menu.css
0
4223
https://www.senate.gov/resources/styles/boilerplate.css
0
3600
https://www.senate.gov/resources/scripts/respond.min.js
0
2080
https://www.senate.gov/resources/scripts/skdslider.min.js
0
2040
https://www.senate.gov/resources/styles/skdslider.css
0
1969
https://www.senate.gov/resources/scripts/main.js
0
1323
https://www.senate.gov/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700
0
1145
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic
0
1145
https://www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700
0
1145
https://www.senate.gov/resources/styles/print.css
0
1059
https://www.senate.gov/wt_sdc/central_webtrends.load.js
0
961
https://www.senate.gov/wt_sdc/webtrends.getcg.js
0
826
https://www.senate.gov/resources/scripts/floor_status.js
0
790
https://floor.senate.gov/ViewPublisher.php?view_id=18&callback=jsonCallback&_=1623949219608
0
462
Minimize main-thread work — 7.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
2687.648
Other
2067.94
Script Evaluation
1994.772
Script Parsing & Compilation
405.288
Parse HTML & CSS
394.132
Rendering
114.052
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
391.99100001133
https://www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3
300.48300002818
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
102.57699998328
https://www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
296.09800002072
https://www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
506.70500000706
Reduce the impact of third-party code — Third-party code blocked the main thread for 660 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
60155
659.644
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.senate.gov/resources/images/col2_senatefloor.jpg
img
https://www.senate.gov/resources/images/33_00019.jpg
img
https://www.senate.gov/resources/graphic/history_lbj.jpg
img
https://www.senate.gov/resources/images/senate_logo_footer.png
https://www.senate.gov/resources/images/usFlag.png
https://www.senate.gov/resources/images/senate_logo.png
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of senate.gov. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Senate.gov may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that senate.gov should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js
https://www.senate.gov/resources/scripts/jquery.min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://senate.gov/
Allowed
http://www.senate.gov/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.senate.gov/resources/images/senate_logo.png
317 x 94
350 x 104
634 x 188
https://www.senate.gov/resources/images/usFlag.png
44 x 23
44 x 23
88 x 46

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
69

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for senate.gov. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of senate.gov on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 2 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid — 523 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
2
<!-- [if lt IE 7]> <html class="ie6 oldie"> <![endif] -->
Syntax not understood
3
<!-- [if IE 7]> <html class="ie7 oldie"> <![endif] -->
Syntax not understood
4
<!-- [if IE 8]> <html class="ie8 oldie"> <![endif] -->
Syntax not understood
5
<!-- [if gt IE 8]> <! --><html class="">
Syntax not understood
6
<!-- <![endif] -->
Syntax not understood
7
<head>
Syntax not understood
8
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
Syntax not understood
9
<meta charset="UTF-8">
Syntax not understood
10
<meta content="width=device-width, initial-scale=1" name="viewport">
Syntax not understood
11
<meta name="object" content="file_not_found">
Syntax not understood
12
<meta name="version" content="7.1">
Syntax not understood
13
<meta name="path" content="/Senate.gov/pagelayout/general/one_item_and_teasers">
Syntax not understood
14
<meta name="date" content="Thursday, January 19, 2017">
Syntax not understood
15
<meta name="time" content="9:56:09 AM EST">
Unknown directive
16
<meta name="keywords" content="">
Syntax not understood
17
<meta name="bucket" content="art">
Syntax not understood
18
<meta name="description" content="404 Error Page">
Syntax not understood
19
<title>U.S. Senate: 404 Error Page</title>
Unknown directive
20
<link type="image/x-icon" href="/resources/images/us_sen.ico" rel="shortcut icon">
Syntax not understood
21
<link type="text/css" rel="stylesheet" href="/resources/styles/boilerplate.css">
Syntax not understood
22
<link type="text/css" rel="stylesheet" href="/resources/styles/main.css">
Syntax not understood
23
<link type="text/css" rel="stylesheet" href="/resources/styles/nav_menu.css">
Syntax not understood
24
<link type="text/css" rel="stylesheet" href="/resources/styles/skdslider.css">
Syntax not understood
25
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,300,600,700,300italic,400italic,600italic,700italic">
Unknown directive
26
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700">
Unknown directive
27
<link type="text/css" rel="stylesheet" href="/resources/fonts/gFonts.css?family=Libre+Baskerville:400,400italic,700">
Unknown directive
28
<link href="/resources/fonts/css/font-awesome.min.css" rel="stylesheet">
Syntax not understood
29
<link type="text/css" rel="stylesheet" href="/resources/styles/print.css">
Syntax not understood
30
<link type="text/css" rel="stylesheet" href="/resources/styles/content.css">
Syntax not understood
31
<!-- [if lt IE 9]> <script src="/resources/scripts/html5shiv.js"></script> <![endif] -->
Syntax not understood
33
<script type="text/javascript">
Syntax not understood
35
function MM_goToURL() { //v3.0
Syntax not understood
36
var i, args=MM_goToURL.arguments; document.MM_returnValue = false;
Syntax not understood
37
for (i=0; i<(args.length-1); i+=2) eval(args[i]+".location='"+args[i+1]+"'");
Syntax not understood
38
}
Syntax not understood
40
</script>
Syntax not understood
41
<script type="text/javascript">
Syntax not understood
42
function MM_jumpMenu(targ,selObj,restore){ //v3.0
Syntax not understood
43
eval(targ+".location='"+selObj.options[selObj.selectedIndex].value+"'");
Syntax not understood
44
if (restore) selObj.selectedIndex=0;
Syntax not understood
45
}
Syntax not understood
46
</script><script src="/resources/scripts/jquery-1.11.3.min.js"></script><script src="/resources/scripts/skdslider.min.js"></script><script src="/resources/scripts/main.js"></script><script type="text/javascript">
Syntax not understood
47
jQuery(document).ready(function(){
Syntax not understood
48
jQuery('#slider').skdslider({delay:5000, animationSpeed: 2000,showNextPrev:true,showPlayButton:true,autoSlide:true,animationType:'fading'});
Syntax not understood
50
jQuery('#responsive').change(function(){
Syntax not understood
51
$('#responsive_wrapper').width(jQuery(this).val());
Syntax not understood
52
$(window).trigger('resize');
Syntax not understood
53
});
Syntax not understood
55
});
Syntax not understood
56
</script><script src="/resources/scripts/floor_status.js"></script>
Syntax not understood
57
</head>
Syntax not understood
58
<body onload="myFunction()">
Syntax not understood
59
<header class="mobilehead clearfix">
Syntax not understood
60
<div id="top-header">
Syntax not understood
61
<CFPARAM NAME="URL.q" DEFAULT="">
Syntax not understood
62
<div id="find-sen" class="row">
Syntax not understood
63
<div id="flag" class="fluid "><img src="/resources/images/usFlag.png" alt="U.S. Flag" /></div>
Syntax not understood
64
<div id="sen-dropdown-container" class="fluid ">
Syntax not understood
65
<form name="findSenators" method="post">
Syntax not understood
66
<label for="findsenator" />
Syntax not understood
67
<select name="stateName" class="arrow" id="findsenator" onChange="MM_jumpMenu('parent',this,0)">
Syntax not understood
68
<option value="/states/">Find Your Senators</option>
Syntax not understood
69
<option value="/states/AL/intro.htm">Alabama</option>
Syntax not understood
70
<option value="/states/AK/intro.htm">Alaska</option>
Syntax not understood
71
<option value="/states/AZ/intro.htm">Arizona</option>
Syntax not understood
72
<option value="/states/AR/intro.htm">Arkansas</option>
Syntax not understood
73
<option value="/states/CA/intro.htm">California</option>
Syntax not understood
74
<option value="/states/CO/intro.htm">Colorado</option>
Syntax not understood
75
<option value="/states/CT/intro.htm">Connecticut</option>
Syntax not understood
76
<option value="/states/DE/intro.htm">Delaware</option>
Syntax not understood
77
<option value="/states/FL/intro.htm">Florida</option>
Syntax not understood
78
<option value="/states/GA/intro.htm">Georgia</option>
Syntax not understood
79
<option value="/states/HI/intro.htm">Hawaii</option>
Syntax not understood
80
<option value="/states/ID/intro.htm">Idaho</option>
Syntax not understood
81
<option value="/states/IL/intro.htm">Illinois</option>
Syntax not understood
82
<option value="/states/IN/intro.htm">Indiana</option>
Syntax not understood
83
<option value="/states/IA/intro.htm">Iowa</option>
Syntax not understood
84
<option value="/states/KS/intro.htm">Kansas</option>
Syntax not understood
85
<option value="/states/KY/intro.htm">Kentucky</option>
Syntax not understood
86
<option value="/states/LA/intro.htm">Louisiana</option>
Syntax not understood
87
<option value="/states/ME/intro.htm">Maine</option>
Syntax not understood
88
<option value="/states/MD/intro.htm">Maryland</option>
Syntax not understood
89
<option value="/states/MA/intro.htm">Massachusetts</option>
Syntax not understood
90
<option value="/states/MI/intro.htm">Michigan</option>
Syntax not understood
91
<option value="/states/MN/intro.htm">Minnesota</option>
Syntax not understood
92
<option value="/states/MS/intro.htm">Mississippi</option>
Syntax not understood
93
<option value="/states/MO/intro.htm">Missouri</option>
Syntax not understood
94
<option value="/states/MT/intro.htm">Montana</option>
Syntax not understood
95
<option value="/states/NE/intro.htm">Nebraska</option>
Syntax not understood
96
<option value="/states/NV/intro.htm">Nevada</option>
Syntax not understood
97
<option value="/states/NH/intro.htm">New Hampshire</option>
Syntax not understood
98
<option value="/states/NJ/intro.htm">New Jersey</option>
Syntax not understood
99
<option value="/states/NM/intro.htm">New Mexico</option>
Syntax not understood
100
<option value="/states/NY/intro.htm">New York</option>
Syntax not understood
101
<option value="/states/NC/intro.htm">North Carolina</option>
Syntax not understood
102
<option value="/states/ND/intro.htm">North Dakota</option>
Syntax not understood
103
<option value="/states/OH/intro.htm">Ohio</option>
Syntax not understood
104
<option value="/states/OK/intro.htm">Oklahoma</option>
Syntax not understood
105
<option value="/states/OR/intro.htm">Oregon</option>
Syntax not understood
106
<option value="/states/PA/intro.htm">Pennsylvania</option>
Syntax not understood
107
<option value="/states/RI/intro.htm">Rhode Island</option>
Syntax not understood
108
<option value="/states/SC/intro.htm">South Carolina</option>
Syntax not understood
109
<option value="/states/SD/intro.htm">South Dakota</option>
Syntax not understood
110
<option value="/states/TN/intro.htm">Tennessee</option>
Syntax not understood
111
<option value="/states/TX/intro.htm">Texas</option>
Syntax not understood
112
<option value="/states/UT/intro.htm">Utah</option>
Syntax not understood
113
<option value="/states/VT/intro.htm">Vermont</option>
Syntax not understood
114
<option value="/states/VA/intro.htm">Virginia</option>
Syntax not understood
115
<option value="/states/WA/intro.htm">Washington</option>
Syntax not understood
116
<option value="/states/WV/intro.htm">West Virginia</option>
Syntax not understood
117
<option value="/states/WI/intro.htm">Wisconsin</option>
Syntax not understood
118
<option value="/states/WY/intro.htm">Wyoming</option>
Syntax not understood
119
</select>
Syntax not understood
120
</form>
Syntax not understood
121
</div>
Syntax not understood
122
<div id="watch" class="fluid">
Syntax not understood
123
<div class="fluid watch_text"><span class="fa fa-video-camera"></span>&nbsp;&nbsp;<a id="floorlink" target="_blank"><span id="contentdata"></span></a></div>
Syntax not understood
124
</div>
Syntax not understood
125
</div>
Syntax not understood
126
</div>
Syntax not understood
127
</div>
Syntax not understood
129
<div id="main-header">
Syntax not understood
130
<div class="row">
Syntax not understood
132
<div id="logo">
Syntax not understood
133
<a href="/index.htm"><img src="/resources/images/senate_logo.png" alt="United States Senate Logo" border="0"/></a>
Syntax not understood
134
</div>
Syntax not understood
136
<div id="search-elements" class="fluid ">
Syntax not understood
137
<form name="search" id="search" action="/general/search/search_central_solr.cfm" method="GET">
Syntax not understood
138
<label for="search"><span class="fa fa-search" onClick="document.getElementById('search').submit();"></span></label>
Syntax not understood
139
<input type="text" name="q" value="Search" id="search3" onfocus="this.value=''" />
Syntax not understood
140
<!--commented out by betty<input type="hidden" value="1" name="col" />
Syntax not understood
141
<INPUT type="hidden" name="xsl" value="xml" />-->
Syntax not understood
142
<!--<input type="text" name="q" value="Search" id="search" onfocus="this.value=''" />
Syntax not understood
143
<input type="hidden" name="site" value="default_collection" />
Syntax not understood
144
<input type="hidden" name="num" value="10" />
Syntax not understood
145
<INPUT type="hidden" name="filter" value="0" />-->
Syntax not understood
146
</form>
Syntax not understood
149
<!--solr search section starts
Syntax not understood
150
<form method="GET" action="/general/search/search_central_solr.cfm" name="search" style="display: inline;">
Unknown directive
151
<input type="text" onFocus="this.value=&apos;&apos;" class="searchBox" id="search3" value="<CFOUTPUT>#URL.q#</CFOUTPUT>" name="q"/>
Syntax not understood
152
<input type="image" align="absmiddle" alt="GO" src="/resources/images/uss_button_go.gif"/>
Syntax not understood
153
</form>
Syntax not understood
154
solr search section ends-->
Syntax not understood
155
</div>
Syntax not understood
157
</div>
Syntax not understood
158
</div>
Syntax not understood
160
<div class="nav">
Syntax not understood
161
<div id="nav-head-bg"></div>
Syntax not understood
162
<div class="row">
Syntax not understood
163
<nav class="fluid " id="main-nav">
Syntax not understood
164
<label class="toggle" for="drop">MENU<span class="fa fa-bars"></span></label><input id="drop" type="checkbox">
Syntax not understood
165
<ul class="menu">
Syntax not understood
166
<li class="senatorsmenu">
Syntax not understood
167
<label class="plus-minus mobile-plus" for="drop-1"></label><a href="/senators/contact/">
Syntax not understood
168
SENATORS</a>
Syntax not understood
169
<input type="checkbox" id="drop-1"/>
Syntax not understood
170
<ul class="senatorsmenusub">
Syntax not understood
171
<li><a href="/senators/senators-contact.htm">Contact</a></li>
Syntax not understood
172
<li><a href="/senators/leadership.htm">Leadership</a></li>
Syntax not understood
173
<li><a href="/senators/former_senators.htm">Former Senators</a></li>
Syntax not understood
174
<li><a href="/senators/qualifications_termsofservice.htm">Qualifications &amp; Terms of Service</a></li>
Syntax not understood
175
<li><a href="/senators/facts_milestones.htm">Facts &amp; Milestones</a></li>
Syntax not understood
177
<li><a href="/states/statesmap.htm">States</a></li>
Syntax not understood
178
</ul>
Syntax not understood
179
</li>
Syntax not understood
180
<li class="committeesmenu">
Syntax not understood
181
<label class="plus-minus mobile-plus" for="drop-2"></label><a href="/committees/committees_home.htm">
Syntax not understood
182
COMMITTEES</a>
Syntax not understood
183
<input type="checkbox" id="drop-2"/>
Syntax not understood
184
<ul class="committeesmenusub">
Syntax not understood
185
<li><a href="/committees/membership_assignments.htm">Membership &amp; Assignments </a></li>
Syntax not understood
186
<li><a href="/committees/hearings_meetings.htm">Hearings &amp; Meetings</a></li>
Syntax not understood
187
<li><a href="/committees/history.htm">History</a></li>
Syntax not understood
188
</ul>
Syntax not understood
189
</li>
Syntax not understood
190
<li class="legislationmenu">
Syntax not understood
191
<label class="plus-minus mobile-plus" for="drop-3"></label><a href="/legislative/legislative_home.htm">
Syntax not understood
192
LEGISLATION &amp; RECORDS</a>
Syntax not understood
193
<input type="checkbox" id="drop-3"/>
Syntax not understood
194
<ul class="legislationmenusub">
Syntax not understood
195
<li><a href="/legislative/bills_acts_laws.htm">Bills, Acts, &amp; Laws</a></li>
Syntax not understood
196
<li><a href="/legislative/nominations_new.htm">Nominations</a></li>
Syntax not understood
197
<li><a href="/legislative/treaties_new.htm">Treaties</a></li>
Syntax not understood
198
<li><a href="/legislative/votes_new.htm">Votes</a></li>
Syntax not understood
199
<li><a href="/legislative/floor_activity_pail.htm">Floor Proceedings</a></li>
Syntax not understood
200
<li><a href="/legislative/rules_procedure.htm">Rules &amp; Procedure</a></li>
Syntax not understood
201
<li><a href="/legislative/landmark_legislation.htm">Landmark Legislation</a></li>
Syntax not understood
202
<li><a href="/legislative/sessions_of_congress.htm">Sessions of Congress</a></li>
Syntax not understood
204
<li><a href="/legislative/lobbyingdisc.htm#lobbyingdisc=lda">Public Disclosure</a></li>
Syntax not understood
205
</ul>
Syntax not understood
206
</li>
Syntax not understood
207
<li class="artmenu">
Syntax not understood
208
<label class="plus-minus mobile-plus" for="drop-4"></label><a href="/art/art_hist_home.htm">
Syntax not understood
209
ART &amp; HISTORY</a>
Syntax not understood
210
<input type="checkbox" id="drop-4"/>
Syntax not understood
211
<ul class="artmenusub">
Syntax not understood
212
<li>
Syntax not understood
213
<label for="drop-44" class="plus-minus mobile-plus"> </label>
Syntax not understood
214
<a class="drop-link" href="/history/people.htm">People</a>
Syntax not understood
215
<input type="checkbox" id="drop-44"/>
Syntax not understood
216
<ul class="tertiary-menu">
Syntax not understood
217
<li><a href="/history/officers.htm">Officers &amp; Staff</a></li>
Syntax not understood
218
<li><a href="/history/leader.htm">Party Leadership</a></li>
Syntax not understood
219
<li><a href="/history/senators.htm">Senators</a></li>
Syntax not understood
220
<li><a href="/history/featured_biographies.htm">Featured Biographies</a></li>
Syntax not understood
221
</ul>
Syntax not understood
223
</li>
Syntax not understood
224
<li>
Syntax not understood
225
<label for="drop-45" class="plus-minus mobile-plus"> </label>
Syntax not understood
226
<a class="drop-link" href="/about/powers-procedures.htm">Powers &amp; Procedures</a>
Syntax not understood
227
<input type="checkbox" id="drop-45"/>
Syntax not understood
228
<ul class="tertiary-menu">
Syntax not understood
229
<li><a href="/about/powers-procedures/censure.htm">Censure</a></li>
Syntax not understood
230
<li><a href="/about/powers-procedures/declarations-of-war.htm">Declarations of War</a></li>
Syntax not understood
231
<li><a href="/about/powers-procedures/expulsion.htm">Expulsion</a></li>
Syntax not understood
232
<li><a href="/about/powers-procedures/filibusters-cloture.htm">Filibusters &amp; Cloture</a></li>
Syntax not understood
233
<li><a href="/about/powers-procedures/impeachment.htm">Impeachment</a></li>
Syntax not understood
234
<li><a href="/about/powers-procedures/investigations.htm">Investigations</a></li>
Syntax not understood
235
<li><a href="/about/powers-procedures/nominations.htm">Nominations</a></li>
Syntax not understood
236
<li><a href="/about/powers-procedures/rules.htm">Rules</a></li>
Syntax not understood
237
<li><a href="/about/powers-procedures/treaties.htm">Treaties</a></li>
Syntax not understood
238
<li><a href="/about/powers-procedures/voting.htm">Voting</a></li>
Syntax not understood
239
</ul>
Syntax not understood
241
</li>
Syntax not understood
242
<li>
Syntax not understood
243
<label for="drop-46" class="plus-minus mobile-plus"> </label>
Syntax not understood
244
<a class="drop-link" href="/history/origins.htm">Institution</a>
Syntax not understood
245
<input type="checkbox" id="drop-46"/>
Syntax not understood
246
<ul class="tertiary-menu">
Syntax not understood
247
<li><a href="/history/instdev.htm">Origins &amp; Development</a></li>
Syntax not understood
248
<!-- <li><a href="/history/powers.htm">Powers &amp; Procedures</a></li>-->
Syntax not understood
249
<li><a href="/history/chronology.htm#chronology=y1787_1800">Chronology</a></li>
Syntax not understood
250
<li><a href="/history/partydiv.htm">Party Division</a></li>
Syntax not understood
251
</ul>
Syntax not understood
253
</li>
Syntax not understood
254
<li>
Syntax not understood
255
<label for="drop-47" class="plus-minus mobile-plus"> </label>
Syntax not understood
256
<a class="drop-link" href="/history/essays.htm">Historical Highlights</a>
Syntax not understood
257
<input type="checkbox" id="drop-47"/>
Syntax not understood
258
<ul class="tertiary-menu">
Syntax not understood
259
<li><a href="/history/1787.htm">1787-1800</a></li>
Syntax not understood
260
<li><a href="/history/1801.htm">1801-1850</a></li>
Syntax not understood
261
<li><a href="/history/1851.htm">1851-1877</a></li>
Syntax not understood
262
<li><a href="/history/1878.htm">1878-1920</a></li>
Syntax not understood
263
<li><a href="/history/1921.htm">1921-1940</a></li>
Syntax not understood
264
<li><a href="/history/1941.htm">1941-1963</a></li>
Syntax not understood
265
<li><a href="/history/1964.htm">1964-present</a></li>
Syntax not understood
266
</ul>
Syntax not understood
267
</li>
Syntax not understood
268
<li><a class="drop-link" href="/history/oralhistory.htm">Oral History Project</a> </li>
Syntax not understood
269
<li><a href="/art/exhibits.htm">Special Features</a></li>
Syntax not understood
270
<!-- <li><a href="/art/paintings.htm">Paintings</a></li>
Syntax not understood
271
<li><a href="/art/sculpture.htm">Sculpture</a></li>
Syntax not understood
272
<li><a href="/art/graphicarts.htm">Prints, Drawings &amp; Photographs</a></li>
Syntax not understood
273
<li><a href="/art/collections.htm">Furniture & Decorative Art</a></li>
Syntax not understood
274
<li><a href="/art/ephemera.htm">Ephemera & Historical Objects</a></li>-->
Syntax not understood
275
<li><a href="/art-artifacts/art-artifacts.htm">Art &amp; Artifacts</a></li>
Syntax not understood
278
</ul>
Syntax not understood
279
</li>
Syntax not understood
280
<li class="referencemenu">
Syntax not understood
281
<label class="plus-minus mobile-plus" for="drop-5"></label><a href="/reference/reference_home.htm">
Syntax not understood
282
REFERENCE</a>
Syntax not understood
283
<input type="checkbox" id="drop-5"/>
Syntax not understood
284
<ul class="referencemenusub">
Syntax not understood
285
<li><a href="/reference/virtual.htm">Virtual Reference Desk</a></li>
Syntax not understood
286
<li><a href="/reference/stats_and_lists.htm">Statistics &amp; Lists</a></li>
Syntax not understood
287
<li><a href="/reference/biblio.htm">Bibliographies</a></li>
Syntax not understood
288
<li><a href="/reference/howto.htm">How To...</a></li>
Syntax not understood
289
<li><a href="/reference/glossary.htm">Glossary</a></li>
Syntax not understood
290
<li><a href="/reference/org_chart.htm">Senate Organization</a></li>
Syntax not understood
291
<li><a href="/civics/constitution_item/constitution.htm">The Constitution</a></li>
Syntax not understood
292
<li><a href="/visiting/procurement.htm">Procurement</a></li>
Syntax not understood
293
<li>
Syntax not understood
294
<label for="drop-55" class="plus-minus mobile-plus"> </label>
Syntax not understood
295
<a class="drop-link" href="/visiting/employment.htm">Employment &amp; Internships</a>
Syntax not understood
296
<input type="checkbox" id="drop-55"/>
Syntax not understood
297
<ul class="tertiary-menu">
Syntax not understood
298
<li><a href="/visiting/po.htm">Placement Office</a></li>
Syntax not understood
299
<li><a href="/employment/saa/positions.htm">Sergeant at Arms</a></li>
Syntax not understood
300
<li><a href="/employment/SOS_HR/positions_sos.htm">Secretary of the Senate</a></li>
Syntax not understood
301
</ul>
Syntax not understood
302
</li>
Syntax not understood
303
<li><a href="/visiting/index.htm">Visiting</a></li>
Syntax not understood
304
</ul>
Syntax not understood
305
</li>
Syntax not understood
306
</ul>
Syntax not understood
307
</nav>
Syntax not understood
308
</div>
Syntax not understood
309
</div>
Syntax not understood
310
</header>
Syntax not understood
311
<div id="watch_mobile" class="fluid watch_text"><span class="fa fa-video-camera"></span>&nbsp;&nbsp;<a id="floorlink_mobile" target="_blank"><span id="contentdata_mobile"></span></a></div>
Syntax not understood
312
<main class="gridContainer clearfix">
Syntax not understood
313
<div class="fluid" id="secondary_col2">
Syntax not understood
314
<section class="fluid " id="art_history_header">
Syntax not understood
315
<h1>404 Error Page</h1>
Syntax not understood
316
<div id="h1_action_icons" class="fluid"><a href="javascript:if(window.print)window.print()"><i class="fa fa-print"></i></a>
Unknown directive
317
<!--<a href="index.html"><i class="fa fa-share"></i></a>-->
Syntax not understood
318
</div>
Syntax not understood
319
<hr class="fluid">
Syntax not understood
320
</section>
Syntax not understood
321
<!--
Syntax not understood
322
BEGIN MAIN
Syntax not understood
323
-->
Syntax not understood
324
<P align="center" class="contenttitle"><FONT size="+1">Requested Page Not Found (404).</FONT>
Syntax not understood
325
<hr />
Syntax not understood
328
<ul class="contenttext" style="margin-top: 0px; margin-left: 0px; padding-top: 0px; padding-left: 0 px;">
Unknown directive
329
<p>&#160;</p>
Syntax not understood
330
<li><strong><label for="searchMain">Search Senate.gov:</label></strong> &#160;&#160;&#160;&#160;<form style="display: inline;" action="/general/search/search_central_solr.cfm" method="GET">
Unknown directive
331
<label for="search"><span class="fa fa-search" onClick="document.getElementById('search').submit();"></span></label>
Syntax not understood
332
<input type="text" name="q" id="search3" onfocus="this.value=''" value="Enter Search Term(s)" width="120"/>
Syntax not understood
333
<input style="vertical-align: middle; margin-bottom: .25em;" alt="GO" src="http://www.senate.gov/resources/images/uss_button_go.gif" type="image">
Unknown directive
334
</form>
Syntax not understood
337
<!--<form style="display: inline;" method="GET" action="http://www.senate.gov/general/search/search_cfm.cfm" name="searchMain">
Unknown directive
338
<input onfocus="this.value=''" style="width: 140px;" class="searchBox" id="search3" value="Enter Search Term(s)" name="q" type="text" width="120">
Unknown directive
339
<input style="vertical-align: middle; margin-bottom: .25em;" alt="GO" src="http://www.senate.gov/resources/images/uss_button_go.gif" type="image">
Unknown directive
340
<input value="default_collection" name="site" type="hidden">
Syntax not understood
341
<input value="10" name="num" type="hidden">
Syntax not understood
342
<INPUT value="0" name="filter" type="hidden">
Syntax not understood
343
</form>-->
Syntax not understood
344
</li>
Syntax not understood
345
<p>&#160;</p>
Syntax not understood
346
<li><strong><label for="findsenatorbystate">Find Senators by State:</label></strong> &#160;&#160;&#160;&#160;
Unknown directive
348
<form style="display: inline;" method="post" name="findSenatorsSearch">
Unknown directive
350
<label for="findsenator" />
Syntax not understood
352
<select style="width: 160px;" id="findsenatorbystate" name="stateName"><option value="/states/">--Select State--</option>
Unknown directive
353
<!--<option value="/states/">Find Your Senators</option>-->
Syntax not understood
354
<option value="/states/AL/intro.htm">Alabama</option>
Syntax not understood
355
<option value="/states/AK/intro.htm">Alaska</option>
Syntax not understood
356
<option value="/states/AZ/intro.htm">Arizona</option>
Syntax not understood
357
<option value="/states/AR/intro.htm">Arkansas</option>
Syntax not understood
358
<option value="/states/CA/intro.htm">California</option>
Syntax not understood
359
<option value="/states/CO/intro.htm">Colorado</option>
Syntax not understood
360
<option value="/states/CT/intro.htm">Connecticut</option>
Syntax not understood
361
<option value="/states/DE/intro.htm">Delaware</option>
Syntax not understood
362
<option value="/states/FL/intro.htm">Florida</option>
Syntax not understood
363
<option value="/states/GA/intro.htm">Georgia</option>
Syntax not understood
364
<option value="/states/HI/intro.htm">Hawaii</option>
Syntax not understood
365
<option value="/states/ID/intro.htm">Idaho</option>
Syntax not understood
366
<option value="/states/IL/intro.htm">Illinois</option>
Syntax not understood
367
<option value="/states/IN/intro.htm">Indiana</option>
Syntax not understood
368
<option value="/states/IA/intro.htm">Iowa</option>
Syntax not understood
369
<option value="/states/KS/intro.htm">Kansas</option>
Syntax not understood
370
<option value="/states/KY/intro.htm">Kentucky</option>
Syntax not understood
371
<option value="/states/LA/intro.htm">Louisiana</option>
Syntax not understood
372
<option value="/states/ME/intro.htm">Maine</option>
Syntax not understood
373
<option value="/states/MD/intro.htm">Maryland</option>
Syntax not understood
374
<option value="/states/MA/intro.htm">Massachusetts</option>
Syntax not understood
375
<option value="/states/MI/intro.htm">Michigan</option>
Syntax not understood
376
<option value="/states/MN/intro.htm">Minnesota</option>
Syntax not understood
377
<option value="/states/MS/intro.htm">Mississippi</option>
Syntax not understood
378
<option value="/states/MO/intro.htm">Missouri</option>
Syntax not understood
379
<option value="/states/MT/intro.htm">Montana</option>
Syntax not understood
380
<option value="/states/NE/intro.htm">Nebraska</option>
Syntax not understood
381
<option value="/states/NV/intro.htm">Nevada</option>
Syntax not understood
382
<option value="/states/NH/intro.htm">New Hampshire</option>
Syntax not understood
383
<option value="/states/NJ/intro.htm">New Jersey</option>
Syntax not understood
384
<option value="/states/NM/intro.htm">New Mexico</option>
Syntax not understood
385
<option value="/states/NY/intro.htm">New York</option>
Syntax not understood
386
<option value="/states/NC/intro.htm">North Carolina</option>
Syntax not understood
387
<option value="/states/ND/intro.htm">North Dakota</option>
Syntax not understood
388
<option value="/states/OH/intro.htm">Ohio</option>
Syntax not understood
389
<option value="/states/OK/intro.htm">Oklahoma</option>
Syntax not understood
390
<option value="/states/OR/intro.htm">Oregon</option>
Syntax not understood
391
<option value="/states/PA/intro.htm">Pennsylvania</option>
Syntax not understood
392
<option value="/states/RI/intro.htm">Rhode Island</option>
Syntax not understood
393
<option value="/states/SC/intro.htm">South Carolina</option>
Syntax not understood
394
<option value="/states/SD/intro.htm">South Dakota</option>
Syntax not understood
395
<option value="/states/TN/intro.htm">Tennessee</option>
Syntax not understood
396
<option value="/states/TX/intro.htm">Texas</option>
Syntax not understood
397
<option value="/states/UT/intro.htm">Utah</option>
Syntax not understood
398
<option value="/states/VT/intro.htm">Vermont</option>
Syntax not understood
399
<option value="/states/VA/intro.htm">Virginia</option>
Syntax not understood
400
<option value="/states/WA/intro.htm">Washington</option>
Syntax not understood
401
<option value="/states/WV/intro.htm">West Virginia</option>
Syntax not understood
402
<option value="/states/WI/intro.htm">Wisconsin</option>
Syntax not understood
403
<option value="/states/WY/intro.htm">Wyoming</option>
Syntax not understood
404
</select>
Syntax not understood
405
<a href="#"><img alt="GO" align="absmiddle" src="/resources/images/uss_button_go.gif" onClick="location=findSenators.findsenator.options[findSenatorsSearch.findsenatorbystate.selectedIndex].value" style="vertical-align: middle; margin-bottom: .25em; border-style: none; link-style: none; border-thickness: 0px;"></a>
Syntax not understood
406
</form>
Syntax not understood
411
<!-- <form style="display: inline;" method="post" name="findSenatorsSearch">
Unknown directive
412
<select style="width: 160px;" class="searchBox" id="findsenatorbystate" name="stateName"><option value="/general/contact_information/senators_cfm.cfm">--Select State--</option><option value="/general/contact_information/senators_cfm.cfm?State=AL">Alabama</option><option value="/general/contact_information/senators_cfm.cfm?State=AK">Alaska</option><option value="/general/contact_information/senators_cfm.cfm?State=AZ">Arizona</option><option value="/general/contact_information/senators_cfm.cfm?State=AR">Arkansas</option><option value="/general/contact_information/senators_cfm.cfm?State=CA">California</option><option value="/general/contact_information/senators_cfm.cfm?State=CO">Colorado</option><option value="/general/contact_information/senators_cfm.cfm?State=CT">Connecticut</option><option value="/general/contact_information/senators_cfm.cfm?State=DE">Delaware</option><option value="/general/contact_information/senators_cfm.cfm?State=FL">Florida</option><option value="/general/contact_information/senators_cfm.cfm?State=GA">Georgia</option><option value="/general/contact_information/senators_cfm.cfm?State=HI">Hawaii</option><option value="/general/contact_information/senators_cfm.cfm?State=ID">Idaho</option><option value="/general/contact_information/senators_cfm.cfm?State=IL">Illinois</option><option value="/general/contact_information/senators_cfm.cfm?State=IN">Indiana</option><option value="/general/contact_information/senators_cfm.cfm?State=IA">Iowa</option><option value="/general/contact_information/senators_cfm.cfm?State=KS">Kansas</option><option value="/general/contact_information/senators_cfm.cfm?State=KY">Kentucky</option><option value="/general/contact_information/senators_cfm.cfm?State=LA">Louisiana</option><option value="/general/contact_information/senators_cfm.cfm?State=ME">Maine</option><option value="/general/contact_information/senators_cfm.cfm?State=MD">Maryland</option><option value="/general/contact_information/senators_cfm.cfm?State=MA">Massachusetts</option><option value="/general/contact_information/senators_cfm.cfm?State=MI">Michigan</option><option value="/general/contact_information/senators_cfm.cfm?State=MN">Minnesota</option><option value="/general/contact_information/senators_cfm.cfm?State=MS">Mississippi</option><option value="/general/contact_information/senators_cfm.cfm?State=MO">Missouri</option><option value="/general/contact_information/senators_cfm.cfm?State=MT">Montana</option><option value="/general/contact_information/senators_cfm.cfm?State=NE">Nebraska</option><option value="/general/contact_information/senators_cfm.cfm?State=NV">Nevada</option><option value="/general/contact_information/senators_cfm.cfm?State=NH">New Hampshire</option><option value="/general/contact_information/senators_cfm.cfm?State=NJ">New Jersey</option><option value="/general/contact_information/senators_cfm.cfm?State=NM">New Mexico</option><option value="/general/contact_information/senators_cfm.cfm?State=NY">New York</option><option value="/general/contact_information/senators_cfm.cfm?State=NC">North Carolina</option><option value="/general/contact_information/senators_cfm.cfm?State=ND">North Dakota</option><option value="/general/contact_information/senators_cfm.cfm?State=OH">Ohio</option><option value="/general/contact_information/senators_cfm.cfm?State=OK">Oklahoma</option><option value="/general/contact_information/senators_cfm.cfm?State=OR">Oregon</option><option value="/general/contact_information/senators_cfm.cfm?State=PA">Pennsylvania</option><option value="/general/contact_information/senators_cfm.cfm?State=RI">Rhode Island</option><option value="/general/contact_information/senators_cfm.cfm?State=SC">South Carolina</option><option value="/general/contact_information/senators_cfm.cfm?State=SD">South Dakota</option><option value="/general/contact_information/senators_cfm.cfm?State=TN">Tennessee</option><option value="/general/contact_information/senators_cfm.cfm?State=TX">Texas</option><option value="/general/contact_information/senators_cfm.cfm?State=UT">Utah</option><option value="/general/contact_information/senators_cfm.cfm?State=VT">Vermont</option><option value="/general/contact_information/senators_cfm.cfm?State=VA">Virginia</option><option value="/general/contact_information/senators_cfm.cfm?State=WA">Washington</option><option value="/general/contact_information/senators_cfm.cfm?State=WV">West Virginia</option><option value="/general/contact_information/senators_cfm.cfm?State=WI">Wisconsin</option><option value="/general/contact_information/senators_cfm.cfm?State=WY">Wyoming</option></select> <a href="#"><img alt="GO" align="absmiddle" src="/resources/images/uss_button_go.gif" onClick="location=findSenators.findsenator.options[findSenatorsSearch.findsenatorbystate.selectedIndex].value" style="vertical-align: middle; margin-bottom: .25em; border-style: none; link-style: none; border-thickness: 0px;"></a>
Unknown directive
413
</form> -->
Syntax not understood
414
</li>
Syntax not understood
415
<p>&#160;</p>
Syntax not understood
416
<li><strong>Contact:</strong> E-mail <a href="mailto:webmaster@sec.senate.gov">webmaster@sec.senate.gov</a> to report a broken link, ask technical questions, or provide feedback on <a href="www.senate.gov">www.senate.gov</a>. For all other correspondence <a href="http://www.senate.gov/pagelayout/general/one_item_and_teasers/contacting.htm">contact your senators</a>.
Unknown directive
417
<br />
Syntax not understood
418
<br />
Syntax not understood
419
<span class="caption"><strong>*NOTE:</strong> Please do not ask the webmaster to forward mail to senators' offices.</li>
Unknown directive
420
</ul>
Syntax not understood
424
<table width="100%">
Syntax not understood
425
<tr>
Syntax not understood
426
<td>&nbsp;</td>
Syntax not understood
427
</tr>
Syntax not understood
428
</table>
Syntax not understood
429
<!--
Syntax not understood
430
END MAIN
Syntax not understood
431
-->
Syntax not understood
432
</div>
Syntax not understood
433
<div class="fluid" id="secondary_col1">
Syntax not understood
434
<!DOCTYPE noindex PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
435
<noindex />
Syntax not understood
437
<!--
Syntax not understood
438
BEGIN TEASERS
Syntax not understood
439
-->
Syntax not understood
440
<!--****** VRD_SiteMap Version: 4.1 was generated at: Friday, March 3, 2017: 2:45 PM EST in folder: /Senate.gov/general/common/teaser **--><aside class="fluid sidebar_link_container">
Unknown directive
441
<div class="fluid content_column_container">
Syntax not understood
442
<h3>Virtual Reference Desk </h3>
Syntax not understood
443
<span style="padding-top:5px" class="teasertext">
Unknown directive
444
<p>Browse the site by topic with the <A href="/pagelayout/reference/b_three_sections_with_teasers/virtual.htm">Virtual Reference Desk</A>.</p>
Syntax not understood
445
<p>&nbsp;</p>
Syntax not understood
446
</span>
Syntax not understood
447
</div>
Syntax not understood
448
</aside>
Syntax not understood
450
<br>
Syntax not understood
451
<!--****** FAQs.xml Version: 14.1 was generated at: Wednesday, June 27, 2018: 2:37 PM EDT in folder: /Company Home/Sites/senategov/documentLibrary/Senate.gov/general/common/teaser **--><aside class="fluid sidebar_link_container">
Unknown directive
452
<div class="fluid content_column_container">
Syntax not understood
453
<h3>Related Links </h3>
Syntax not understood
454
<span style="padding-top:5px" class="teasertext">
Unknown directive
455
<p>Frequently Asked Questions</p>
Syntax not understood
456
<p>
Syntax not understood
457
<a href="/committees/committees_faq.htm">Committees</a>
Syntax not understood
458
</p>
Syntax not understood
459
<p>
Syntax not understood
460
<a href="/pagelayout/reference/b_three_sections_with_teasers/howto.htm">Congressional Research</a>
Syntax not understood
461
</p>
Syntax not understood
462
<p>
Syntax not understood
463
<a href="/general/common/generic/NewCongress_faq.htm">New Congress</a>
Syntax not understood
464
</p>
Syntax not understood
465
<p>&nbsp;</p>
Syntax not understood
466
</span>
Syntax not understood
467
</div>
Syntax not understood
468
</aside>
Syntax not understood
470
<br>
Syntax not understood
471
<!--
Syntax not understood
472
END TEASERS
Syntax not understood
473
-->
Syntax not understood
474
</div>
Syntax not understood
475
<div id="social_background_white" class="fluid ">
Syntax not understood
476
<div id="logo_social_footer_center" class="fluid ">
Syntax not understood
477
<div id="footer_logo" class="fluid "><a href="/index.htm"><img src="/resources/images/senate_logo_footer.png" alt="Senate Logo"/></a></div>
Syntax not understood
478
</div>
Syntax not understood
479
</div>
Syntax not understood
480
</main>
Syntax not understood
481
<footer id="footer" class="fluid gridContainer clearfix">
Syntax not understood
482
<div id="footer_menu_center">
Syntax not understood
484
<div id="footer_menu_senators" >
Syntax not understood
485
<h3><a href="/senators/contact/">SENATORS</a></h3>
Syntax not understood
486
<ul class="fluid fluidList footer_links">
Syntax not understood
487
<li><a href="/senators/senators-contact.htm">Contact</a></li>
Syntax not understood
488
<li><a href="/senators/leadership.htm">Leadership &amp; Officers</a></li>
Syntax not understood
489
<li><a href="/senators/former_senators.htm">Former Senators</a></li>
Syntax not understood
490
<li><a href="/senators/qualifications_termsofservice.htm">Qualifications &amp; Terms of Service</a></li>
Syntax not understood
491
<li><a href="/senators/facts_milestones.htm">Facts &amp; Milestones</a></li>
Syntax not understood
492
<li><a href="/senators/statesmap.htm">States</a></li>
Syntax not understood
494
</ul>
Syntax not understood
496
<div id="footer_menu_committees" >
Syntax not understood
497
<h3 style="padding-top: 75px;"><a href="/committees/committees_home.htm">COMMITTEES</a></h3>
Unknown directive
498
<ul class="fluid fluidList footer_links">
Syntax not understood
499
<li><a href="/committees/membership_assignments.htm">Membership &amp; Assignments</a></li>
Syntax not understood
500
<li><a href="/committees/hearings_meetings.htm">Hearings &amp; Meetings</a></li>
Syntax not understood
501
<li><a href="/committees/history.htm">History</a></li>
Syntax not understood
502
</ul></div>
Syntax not understood
503
</div>
Syntax not understood
505
<div id="footer_menu_legislation" >
Syntax not understood
506
<h3><a href="/legislative/legislative_home.htm">LEGISLATION &amp; <br>
Syntax not understood
507
RECORDS</a></h3>
Syntax not understood
508
<ul class="fluid fluidList footer_links">
Syntax not understood
509
<li><a href="/legislative/bills_acts_laws.htm">Bills, Acts, & Laws</a></li>
Syntax not understood
510
<li><a href="/legislative/nominations_new.htm">Nominations</a></li>
Syntax not understood
511
<li><a href="/legislative/treaties_new.htm">Treaties</a></li>
Syntax not understood
512
<li><a href="/legislative/votes_new.htm">Votes</a></li>
Syntax not understood
513
<li><a href="/legislative/floor_activity_pail.htm">Floor Proceedings</a></li>
Syntax not understood
514
<li><a href="/legislative/rules_procedure.htm">Rules &amp; Procedure</a></li>
Syntax not understood
515
<li><a href="/legislative/landmark_legislation.htm">Landmark Legislation</a></li>
Syntax not understood
516
<li><a href="/legislative/sessions_of_congress.htm">Sessions of Congress</a></li>
Syntax not understood
517
<li><a href="/legislative/lobbyingdisc.htm#lobbyingdisc=lda">Public Disclosure</a></li>
Syntax not understood
519
</ul></div>
Syntax not understood
521
<div id="footer_menu_art" >
Syntax not understood
522
<h3><a href="/art/art_hist_home.htm">ART &amp; HISTORY</a></h3>
Syntax not understood
523
<ul class="fluid fluidList footer_links">
Syntax not understood
524
<li><a href="/history/people.htm">People</a></li>
Syntax not understood
525
<li><a href="/about/powers-procedures.htm">Powers &amp; Procedures</a></li>
Syntax not understood
526
<li><a href="/history/origins.htm">Institution</a></li>
Syntax not understood
527
<li><a href="/history/essays.htm">Historical Highlights</a></li>
Syntax not understood
528
<li><a href="/history/oralhistory.htm">Oral History Project</a></li>
Syntax not understood
529
<li><a href="/art-artifacts/art-artifacts.htm">Art &amp; Artifacts</a></li>
Syntax not understood
530
<li><a href="/artandhistory/senate-stories/menu.htm">Senate Stories Blog</a></li>
Syntax not understood
531
</ul></div>
Syntax not understood
533
<div id="footer_menu_reference" >
Syntax not understood
534
<h3><a href="/reference/reference_home.htm">REFERENCE</a></h3>
Syntax not understood
535
<ul class="fluid fluidList footer_links">
Syntax not understood
536
<li><a href="/reference/virtual.htm">Virtual Reference Desk</a></li>
Syntax not understood
537
<li><a href="/reference/stats_and_lists.htm">Statistics &amp; Lists</a></li>
Syntax not understood
538
<li><a href="/reference/biblio.htm">Bibliographies</a></li>
Syntax not understood
539
<li><a href="/reference/howto.htm">How To...</a></li>
Syntax not understood
540
<li><a href="/reference/glossary.htm">Glossary</a></li>
Syntax not understood
541
<li><a href="/reference/org_chart.htm">Senate Organization</a></li>
Syntax not understood
542
<li><a href="/civics/constitution_item/constitution.htm">The Constitution</a></li>
Syntax not understood
543
<li><a href="/visiting/procurement.htm">Procurement</a></li>
Syntax not understood
544
<li><a href="/visiting/employment.htm">Employment &amp; Internships</a></li>
Syntax not understood
545
<li><a href="/visiting/index.htm">Visiting</a></li>
Syntax not understood
546
</ul></div>
Syntax not understood
547
</div>
Syntax not understood
549
<div id="footer_legal" class="fluid " >
Syntax not understood
550
<p><!--<span class="speaker legal"><a href="/general/common/generic/browsealoud.htm">BrowseAloud</a></span> &nbsp; | &nbsp; -->
Syntax not understood
551
<a href="/general/contacting.htm">Contact</a> &nbsp; | &nbsp;
Syntax not understood
552
<a href="/general/content_responsibility.htm">Content Responsibility</a> &nbsp; | &nbsp;
Syntax not understood
553
<a href="/usage/internetpolicy.htm">Usage Policy</a> &nbsp; | &nbsp;
Syntax not understood
554
<a href="/general/pdf_help.htm">PDF Help</a> &nbsp; | &nbsp;
Syntax not understood
555
<a href="/general/privacy.htm">Privacy Policy</a> &nbsp; | &nbsp;
Syntax not understood
556
<a href="/index.htm">www.senate.gov</a>
Syntax not understood
557
</p>
Syntax not understood
558
</div>
Syntax not understood
559
</footer>
Syntax not understood
564
<!-- START OF SmartSource Data Collector TAG -->
Syntax not understood
565
<script src="/wt_sdc/central_webtrends.load.js" type="text/javascript"></script>
Syntax not understood
567
<noscript>
Syntax not understood
568
<div><img alt="DCSIMG" id="DCSIMG" width="1" height="1" src="//statse.webtrendslive.com/dcs222dj3ow9ji0ne9ojbcbng_3b8p/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=10.4.0&amp;dcssip=www.senate.gov"/></div>
Syntax not understood
569
</noscript>
Syntax not understood
570
<!-- END OF SmartSource Data Collector TAG -->
Syntax not understood
573
</body>
Syntax not understood
574
</html>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of senate.gov. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of senate.gov on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 23.5.234.215
Continent: North America
Country: United States
United States Flag
Region: New York
City: New York
Longitude: -74.0066
Latitude: 40.7126
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Akamai Technologies, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: U.S. Senate
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 92/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.senate.gov
Issued By: DigiCert SHA2 Extended Validation Server CA
Valid From: 12th January, 2021
Valid To: 15th November, 2021
Subject: CN = www.senate.gov
O = U.S. Senate
L = Washington
S = US
Hash: 7c73a323
Issuer: CN = DigiCert SHA2 Extended Validation Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 6819613327754029622471552448173253221
Serial Number (Hex): 052168E57CE25EA55D24F158BD6D2265
Valid From: 12th January, 2024
Valid To: 15th November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:3D:D3:50:A5:D6:A0:AD:EE:F3:4A:60:0A:65:D3:21:D4:F8:F8:D6:0F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/sha2-ev-server-g3.crl

Full Name:
URI:http://crl4.digicert.com/sha2-ev-server-g3.crl

Certificate Policies: Policy: 2.23.140.1.1
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2ExtendedValidationServerCA.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Jan 12 20:48:04.100 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C7:A9:AA:A7:8B:25:13:20:0B:CF:FC:
CB:20:8E:FD:B9:88:D9:00:78:AE:7A:FA:76:28:D6:BC:
3F:29:1B:18:17:02:21:00:BD:8D:D9:98:D7:77:D9:23:
2F:0D:1D:66:18:D3:03:ED:E7:95:0E:1E:D7:D1:54:0D:
14:02:38:B2:4E:23:0A:01
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Jan 12 20:48:04.184 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B8:CC:3C:52:BA:4B:F6:1C:E8:38:29:
81:82:13:48:1C:A3:4E:13:A7:19:03:21:E5:9D:E9:13:
1F:4D:86:ED:DA:02:20:6B:91:F9:A8:03:FB:43:7E:90:
DA:58:F1:67:4B:AE:F3:A2:4A:B4:34:76:E7:92:EA:1D:
CC:9A:E5:77:3C:CE:82
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:efd.senate.gov
DNS:efdsearch.senate.gov
DNS:go.senate.gov
DNS:placementoffice.senate.gov
DNS:sen.gov
DNS:senate.gov
DNS:soprweb.senate.gov
DNS:soprweb2.senate.gov
DNS:www.ag.senate.gov
DNS:www.aging.senate.gov
DNS:www.agriculture.senate.gov
DNS:www.appropriations.senate.gov
DNS:www.armed-services.senate.gov
DNS:www.banking.senate.gov
DNS:www.blackburn.senate.gov
DNS:www.braun.senate.gov
DNS:www.budget.senate.gov
DNS:www.commerce.senate.gov
DNS:www.cop.senate.gov
DNS:www.cramer.senate.gov
DNS:www.dailypress.senate.gov
DNS:www.democraticleader.senate.gov
DNS:www.democrats.senate.gov
DNS:www.disclosure.senate.gov
DNS:www.dpc.senate.gov
DNS:www.dpcc.senate.gov
DNS:www.drugcaucus.senate.gov
DNS:www.dsoc.senate.gov
DNS:www.energy.senate.gov
DNS:www.epw.senate.gov
DNS:www.ethics.senate.gov
DNS:www.finance.senate.gov
DNS:www.foreign.senate.gov
DNS:www.hawley.senate.gov
DNS:www.help.senate.gov
DNS:www.hsgac.senate.gov
DNS:www.inaugural.senate.gov
DNS:www.indian.senate.gov
DNS:www.intelligence.senate.gov
DNS:www.jec.senate.gov
DNS:www.judiciary.senate.gov
DNS:www.kyl.senate.gov
DNS:www.maps.senate.gov
DNS:www.mcsally.senate.gov
DNS:www.ossoff.senate.gov
DNS:www.pensions.senate.gov
DNS:www.periodicalpress.senate.gov
DNS:www.pressphotographers.senate.gov
DNS:www.radiotv.senate.gov
DNS:www.republican.senate.gov
DNS:www.republicanleader.senate.gov
DNS:www.republicans.senate.gov
DNS:www.rickscott.senate.gov
DNS:www.romney.senate.gov
DNS:www.rosen.senate.gov
DNS:www.rpc.senate.gov
DNS:www.rules.senate.gov
DNS:www.sbc.senate.gov
DNS:www.seccc.senate.gov
DNS:www.sinema.senate.gov
DNS:www.slc.senate.gov
DNS:www.src.senate.gov
DNS:www.veterans.senate.gov
DNS:www.warnock.senate.gov
DNS:www.senate.gov
Technical

DNS Lookup

A Records

Host IP Address Class TTL
senate.gov. 23.62.125.21 IN 19

NS Records

Host Nameserver Class TTL
senate.gov. usw2.akam.net. IN 10799
senate.gov. ns1-139.akam.net. IN 10799
senate.gov. use4.akam.net. IN 10799
senate.gov. use1.akam.net. IN 10799
senate.gov. ns1-201.akam.net. IN 10799
senate.gov. use5.akam.net. IN 10799

CAA Records

Domain Flags Tag Class TTL
digicert.com 0 issue IN 3599
symantec.com 0 issue IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
senate.gov. sen-dmzp.senate.gov. saanoc.saa.senate.gov. 10799

TXT Records

Host Value Class TTL
senate.gov. t20jdz1f1spnv2yr0ss3n58kk50mz5mp IN 10799
senate.gov. v=spf1 IN 10799
senate.gov. MS=ms88689177 IN 10799

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: Apache
Content-Type: text/html
Date: 17th June, 2021
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Connection: keep-alive

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1-139.akam.net
ns1-201.akam.net
use1.akam.net
use4.akam.net
use5.akam.net
usw2.akam.net
Full Whois: % DOTGOV WHOIS Server ready
Domain Name: SENATE.GOV
Status: ACTIVE
Security Contact Email: saanoc2@saa.senate.gov

>>> Last update of whois database: 2021-06-17T16:58:13Z <<<

Please be advised that this whois server only contains information pertaining
to the .GOV domain. For information for other domains please use the whois
server at RS.INTERNIC.NET.

Nameservers

Name IP Address
ns1-139.akam.net 193.108.91.139
ns1-201.akam.net 193.108.91.201
use1.akam.net 72.246.46.64
use4.akam.net 23.211.133.65
use5.akam.net 2.16.40.64
usw2.akam.net 184.26.161.64
Related

Similar Sites

Domain Valuation Snoop Score
$997,715 USD 3/5
0/5
$12,708,881 USD 5/5
$31,487,661 USD 5/5
$3,784,233 USD 4/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$228 USD

Sites hosted on the same IP address