Skip to content
Audit Complete

Results for https://senate.gov

Visit site
Spain Spain · Madrid Completed: Apr 21, 2026 19:07 UTC
Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C71

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Apple · 822 peers
You 71
·
Avg 73
At average
0 50 100
Better than 22% of Apple sites See full Apple benchmark →
Google Search Console · 2306 peers
You 71
·
Avg 73
At average
0 50 100
Better than 23% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
4

No favicon or icon links detected

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Favicon & Branding
5

49 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fsenate.gov)](https://beavercheck.com/results/61fc1ee6-7b14-4044-a77f-20019e818315)
<a href="https://beavercheck.com/results/61fc1ee6-7b14-4044-a77f-20019e818315"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsenate.gov" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsenate.gov

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 12.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 12.8s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~36%.

Speed (1)

Page takes 12.8s to load

+12% bounce

Users abandon at ~3s — you're 10.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (4)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$600 investment → $2,383/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +4666%

Investment

$600

6h · 5 findings

Monthly returns

$2,383 /mo

~$28,596 / year

  • Conversions recovered $2,382
  • Bandwidth savings $0.75

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,509 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$0.75 /mo

9405.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~941 KB per page load
    Saves $0.75/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

64
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
64
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
73
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.58 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

12.77 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

15 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.005

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.58 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

12.82 s

Detailed Report

Audit breakdown by category with detailed findings.

64

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
www.senate.gov/resources/images/sliderphotos/image-bg.jpg0.0 ms604.2 KiB
/resources/images/sliderphotos/Slider_inauguration_38_001...0.0 ms472.6 KiB
www.senate.gov/resources/images/sliderphotos/1800_Capitol_Wing.jpg0.0 ms377.1 KiB
www.senate.gov/resources/images/sliderphotos/Desks_slider_66_00019.jpg0.0 ms274.7 KiB
/resources/images/sliderphotos/women-of-the-senate-rotato...0.0 ms192.4 KiB
www.senate.gov/resources/images/col2_senatefloor.jpg0.0 ms168.0 KiB
www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg0.0 ms167.4 KiB
www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg0.0 ms161.3 KiB
/resources/images/sliderphotos/bingham-modificationists-p...0.0 ms85.3 KiB
www.senate.gov/resources/images/33_00019.jpg0.0 ms84.8 KiB
www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.30.0 ms70.5 KiB
www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg0.0 ms63.6 KiB
www.senate.gov/resources/scripts/jquery-1.11.3.min.js0.0 ms32.9 KiB
www.senate.gov/resources/graphic/history_lbj.jpg0.0 ms32.8 KiB
assets.adobedtm.com/566dc2d26e4f/843d2f589d53/launch-01bbfeb2a9a5.min.js3600.0 s40.5 KiB
www.senate.gov/resources/images/banner-bg.png0.0 ms24.0 KiB
www.senate.gov/resources/images/senate_logo_footer.png0.0 ms20.7 KiB
www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff0.0 ms17.4 KiB
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff0.0 ms17.3 KiB
www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff0.0 ms17.2 KiB
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff0.0 ms17.2 KiB
www.senate.gov/resources/images/usFlag.png0.0 ms17.1 KiB
www.senate.gov/resources/images/bkgnd_stripe_b.png0.0 ms15.4 KiB
www.senate.gov/resources/images/senate_logo.png0.0 ms10.8 KiB
www.senate.gov/resources/images/senate_logo_black.png0.0 ms10.3 KiB
www.senate.gov/resources/styles/main.css0.0 ms7.6 KiB
www.senate.gov/resources/fonts/css/font-awesome.min.css0.0 ms6.8 KiB
www.senate.gov/resources/styles/nav_menu.css0.0 ms4.1 KiB
www.senate.gov/resources/styles/boilerplate.css0.0 ms3.5 KiB
www.senate.gov/resources/scripts/respond.min.js0.0 ms2.0 KiB
www.senate.gov/resources/scripts/skdslider.min.js0.0 ms2.0 KiB
www.senate.gov/resources/styles/skdslider.css0.0 ms1.9 KiB
www.senate.gov/resources/scripts/main.js0.0 ms1.3 KiB
/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,30...0.0 ms1.1 KiB
www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,7000.0 ms1.1 KiB
/resources/fonts/gFonts.css?family=Libre+Baskerville:400,...0.0 ms1.1 KiB
www.senate.gov/resources/styles/print.css0.0 ms1.0 KiB
www.senate.gov/resources/scripts/floor_status.js0.0 ms875 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:31.013 source:map[column:30242 line:2 type:source-location url:https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:28.519 source:map[column:31266 line:1 type:source-location url:https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js urlProvider:network]] map[reflowTime:0.636 source:map[column:29825 line:4 type:source-location url:https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js urlProvider:network]] map[reflowTime:0.309 source:map[column:552 line:0 type:source-location url:https://www.senate.gov/resources/scripts/skdslider.min.js urlProvider:network]] map[reflowTime:0.051 source:map[column:659 line:0 type:source-location url:https://www.senate.gov/resources/scripts/skdslider.min.js urlProvider:network]] map[reflowTime:1.166 source:map[column:28964 line:3 type:source-location url:https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js urlProvider:network]] map[reflowTime:0.271 source:map[column:2323 line:0 type:source-location url:https://www.senate.gov/resources/scripts/skdslider.min.js urlProvider:network]] map[reflowTime:0.061 source:map[column:24862 line:3 type:source-location url:https://www.senate.gov/resources/scripts/jquery-1.11.3.min.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img
www.senate.gov/resources/images/col2_senatefloor.jpg167.8 KiB142.3 KiB
main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img
www.senate.gov/resources/images/33_00019.jpg84.5 KiB59.0 KiB
Senate Logo div#logo_social_footer_center > div#footer_logo > a > img
www.senate.gov/resources/images/senate_logo_footer.png20.4 KiB18.8 KiB
main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img
www.senate.gov/resources/graphic/history_lbj.jpg32.5 KiB17.9 KiB
U.S. Flag cfparam > div#find-sen > div#flag > img
www.senate.gov/resources/images/usFlag.png16.9 KiB16.7 KiB
www.senate.gov/resources/images/bkgnd_stripe_b.png15.1 KiB15.1 KiB
United States Senate Logo div.row > div#logo > a > img
www.senate.gov/resources/images/senate_logo.png10.6 KiB4.6 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-6-DIV
nodeLabel: United States Senate Logo
path: 5,HTML,2,BODY,1,HEADER,1,DIV
selector: body > header.mobilehead > div#main-header
snippet: <div id="main-header">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.senate.gov/http/1.1
www.senate.gov/resources/styles/boilerplate.csshttp/1.1
www.senate.gov/resources/styles/main.csshttp/1.1
www.senate.gov/resources/styles/nav_menu.csshttp/1.1
www.senate.gov/resources/styles/skdslider.csshttp/1.1
/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,30...http/1.1
www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700http/1.1
/resources/fonts/gFonts.css?family=Libre+Baskerville:400,...http/1.1
www.senate.gov/resources/fonts/css/font-awesome.min.csshttp/1.1
www.senate.gov/resources/styles/print.csshttp/1.1
www.senate.gov/resources/scripts/respond.min.jshttp/1.1
www.senate.gov/resources/scripts/jquery-1.11.3.min.jshttp/1.1
www.senate.gov/resources/scripts/skdslider.min.jshttp/1.1
www.senate.gov/resources/scripts/main.jshttp/1.1
www.senate.gov/resources/scripts/floor_status.jshttp/1.1
www.senate.gov/resources/images/usFlag.pnghttp/1.1
www.senate.gov/resources/images/senate_logo.pnghttp/1.1
www.senate.gov/resources/images/sliderphotos/1800_Capitol_Wing.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpghttp/1.1
/resources/images/sliderphotos/bingham-modificationists-p...http/1.1
www.senate.gov/resources/images/sliderphotos/Desks_slider_66_00019.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpghttp/1.1
/resources/images/sliderphotos/women-of-the-senate-rotato...http/1.1
/resources/images/sliderphotos/Slider_inauguration_38_001...http/1.1
www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/image-bg.jpghttp/1.1
www.senate.gov/resources/images/33_00019.jpghttp/1.1
www.senate.gov/resources/images/col2_senatefloor.jpghttp/1.1
www.senate.gov/resources/graphic/history_lbj.jpghttp/1.1
www.senate.gov/resources/images/senate_logo_footer.pnghttp/1.1
www.senate.gov/resources/images/bkgnd_stripe_b.pnghttp/1.1
www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woffhttp/1.1
www.senate.gov/resources/images/banner-bg.pnghttp/1.1
www.senate.gov/resources/images/senate_logo_black.pnghttp/1.1
www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3http/1.1
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woffhttp/1.1
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woffhttp/1.1
www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woffhttp/1.1
www.senate.gov/legislative/schedule/floor_schedule.jsonhttp/1.1
www.senate.gov/resources/images/us_sen.icohttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 832 ms
URLTime Spent
senate.gov/832 ms
www.senate.gov/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.1 KiB
URLTransfer SizeEst Savings
www.senate.gov/resources/styles/boilerplate.css3.5 KiB2.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img
www.senate.gov/resources/images/33_00019.jpg
main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img
www.senate.gov/resources/images/col2_senatefloor.jpg
main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img
www.senate.gov/resources/graphic/history_lbj.jpg
United States Senate Logo div.row > div#logo > a > img
www.senate.gov/resources/images/senate_logo.png
Senate Logo div#logo_social_footer_center > div#footer_logo > a > img
www.senate.gov/resources/images/senate_logo_footer.png
U.S. Flag cfparam > div#find-sen > div#flag > img
www.senate.gov/resources/images/usFlag.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 70 ms
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
JavaScript execution time 0.3 s
Minimizes main-thread work 0.8 s
Avoid long main-thread tasks 3 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 100 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
64

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WATCH LIVE SENATE FLOOR PROCEEDINGS body > div#watch_mobile > a#floorlink_mobile > span#contentdata_mobile
Floor Webcast article#proceedings_schedule > ul > li.fluid > a
Senate Calendar article#proceedings_schedule > ul > li.fluid > a
Executive Calendar article#proceedings_schedule > ul > li.fluid > a
Tentative Floor Schedule article#proceedings_schedule > ul > li.fluid > a
Floor Activity article#proceedings_schedule_2 > ul > li.fluid > a
Daily Digest article#proceedings_schedule_2 > ul > li.fluid > a
Congressional Record article#proceedings_schedule_2 > ul > li.fluid > a
Senate Floor Proceedings, 2014 to Present article#proceedings_schedule_2 > ul > li.fluid > a
Recent Roll Call Votes article#proceedings_schedule_2 > ul > li.fluid > a
Armed Services section#hearings > ul.floor-schedule > li.fluid > a
Energy and Natural Resources section#hearings > ul.floor-schedule > li.fluid > a
Banking, Housing, and Urban Affairs section#hearings > ul.floor-schedule > li.fluid > a
More section#hearings > ul.floor-schedule > li.fluid > a
Research Tools div.fluid > ul > li.fluid > a
Commonly Searched for Legislation div.fluid > ul > li.fluid > a
86 (47-46) ul > li.fluid > span.vote-list > a
PN787-1 ul > li.fluid > span.vote-list > a
85 (49-48) ul > li.fluid > span.vote-list > a
PN787-1 ul > li.fluid > span.vote-list > a
84 (50-49) ul > li.fluid > span.vote-list > a
H.J.Res. 140 ul > li.fluid > span.vote-list > a
All Current Session Roll Call Votes ul > ul > li.fluid > a
Financial Disclosure div.fluid > ul > li.fluid > a
Gift Rule/Travel div.fluid > ul > li.fluid > a
Lobby Disclosure Act div.fluid > ul > li.fluid > a
Women of the Senate div.fluid > ul > li.fluid > a
Senate Stories Blog div.fluid > ul > li.fluid > a
Plan Your Visit div.fluid > ul > li.fluid > a
Capitol Visitor Center div.fluid > ul > li.fluid > a
Capitol Camera div.fluid > ul > li.fluid > a
Employment div.fluid > ul > li.fluid > a
Procurement div.fluid > ul > li.fluid > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tuesday, Apr 21, 2026 div#proceedings_hearings > section#proceedings > article#proceedings_schedule > h3
Tuesday, Apr. 21, 2026 main.gridContainer > div#proceedings_hearings > section#hearings > h3

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div#search-elements > form#search > input#search3 div.row > div#search-elements > form#search > input#search3

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find Your Senators Alabama Alaska Arizona Arkansas California Colorado Connecti… div#sen-dropdown-container > form > label > select#findsenator

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apr 20 | 86 (47-46) | Confirmed | PN787-1 Apr 16 | 85 (49-48) | Agreed to | P… div#content_1 > section#content_container_col2 > div.fluid > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Links are distinguishable without relying on color.
Links have a discernible name
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
United States Senate Logo div.row > div#logo > a > img
www.senate.gov/resources/images/senate_logo.png350 x 104350 x 104525 x 156
U.S. Flag cfparam > div#find-sen > div#flag > img
www.senate.gov/resources/images/usFlag.png44 x 2344 x 2366 x 35

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
73

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
body > main.gridContainer > div.skdslider > a.prev body > main.gridContainer > div.skdslider > a.prev
body > main.gridContainer > div.skdslider > a.next body > main.gridContainer > div.skdslider > a.next
body > main.gridContainer > div.skdslider > a.play-control body > main.gridContainer > div.skdslider > a.play-control

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Image elements have `[alt]` attributes
Document has a valid `hreflang`
robots.txt is valid
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
50
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
64
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.43 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.43 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.162

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.54 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.43 s

Detailed Report

Audit breakdown by category with detailed findings.

65

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
www.senate.gov/resources/images/sliderphotos/image-bg.jpg0.0 ms604.2 KiB
/resources/images/sliderphotos/Slider_inauguration_38_001...0.0 ms472.6 KiB
www.senate.gov/resources/images/sliderphotos/1800_Capitol_Wing.jpg0.0 ms377.1 KiB
www.senate.gov/resources/images/sliderphotos/Desks_slider_66_00019.jpg0.0 ms274.7 KiB
/resources/images/sliderphotos/women-of-the-senate-rotato...0.0 ms192.4 KiB
www.senate.gov/resources/images/col2_senatefloor.jpg0.0 ms168.0 KiB
www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpg0.0 ms167.4 KiB
www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpg0.0 ms161.3 KiB
/resources/images/sliderphotos/bingham-modificationists-p...0.0 ms85.3 KiB
www.senate.gov/resources/images/33_00019.jpg0.0 ms84.8 KiB
www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.30.0 ms70.5 KiB
www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpg0.0 ms63.6 KiB
www.senate.gov/resources/scripts/jquery-1.11.3.min.js0.0 ms32.9 KiB
www.senate.gov/resources/graphic/history_lbj.jpg0.0 ms32.8 KiB
assets.adobedtm.com/566dc2d26e4f/843d2f589d53/launch-01bbfeb2a9a5.min.js3600.0 s40.5 KiB
www.senate.gov/resources/images/banner-bg.png0.0 ms24.0 KiB
www.senate.gov/resources/images/senate_logo_footer.png0.0 ms20.7 KiB
www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff0.0 ms17.4 KiB
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff0.0 ms17.3 KiB
www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff0.0 ms17.2 KiB
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff0.0 ms17.2 KiB
www.senate.gov/resources/images/usFlag.png0.0 ms17.1 KiB
www.senate.gov/resources/images/right-arrow.png0.0 ms15.6 KiB
www.senate.gov/resources/images/left-arrow.png0.0 ms15.6 KiB
www.senate.gov/resources/images/bkgnd_stripe_c.png0.0 ms15.4 KiB
www.senate.gov/resources/images/senate_logo.png0.0 ms10.8 KiB
www.senate.gov/resources/images/senate_logo_black.png0.0 ms10.3 KiB
www.senate.gov/resources/styles/main.css0.0 ms7.6 KiB
www.senate.gov/resources/fonts/css/font-awesome.min.css0.0 ms6.8 KiB
www.senate.gov/resources/styles/nav_menu.css0.0 ms4.1 KiB
www.senate.gov/resources/styles/boilerplate.css0.0 ms3.5 KiB
www.senate.gov/resources/scripts/respond.min.js0.0 ms2.0 KiB
www.senate.gov/resources/scripts/skdslider.min.js0.0 ms2.0 KiB
www.senate.gov/resources/styles/skdslider.css0.0 ms1.9 KiB
www.senate.gov/resources/scripts/main.js0.0 ms1.3 KiB
/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,30...0.0 ms1.1 KiB
www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,7000.0 ms1.1 KiB
/resources/fonts/gFonts.css?family=Libre+Baskerville:400,...0.0 ms1.1 KiB
www.senate.gov/resources/styles/print.css0.0 ms1.0 KiB
www.senate.gov/resources/scripts/floor_status.js0.0 ms875 B
www.senate.gov/resources/images/slide-bg-active.png0.0 ms538 B
www.senate.gov/resources/images/slide-bg.png0.0 ms538 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.162448] map[node:map[boundingRect:map[bottom:938 height:284 left:74 right:1276 top:654 width:1202] lhId:page-10-DIV nodeLabel:Floor Proceedings Tuesday, Apr 21, 2026 Convene at 10:00 a.m. Floor Webcast … path:5,HTML,2,BODY,3,MAIN,2,DIV selector:body > main.gridContainer > div#proceedings_hearings snippet:<div id="proceedings_hearings" class="fluid "> type:node] score:0.092413] map[node:map[boundingRect:map[bottom:1621 height:1376 left:54 right:1296 top:245 width:1242] lhId:page-12-MAIN nodeLabel:Learn About the Senate Explore the Senate's Constitutional foundations, its un… path:5,HTML,2,BODY,3,MAIN selector:body > main.gridContainer snippet:<main class="gridContainer clearfix"> type:node] score:0.030968 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:746 height:499 left:74 right:1276 top:247 width:1202] lhId:page-1-IMG nodeLabel:Captiol 1800 path:5,HTML,2,BODY,3,MAIN,1,DIV,0,UL,0,LI,0,IMG selector:div.skdslider > ul#slider > li > img snippet:<img src="/resources/images/sliderphotos/1800_Capitol_Wing.jpg" alt="Captiol 1800"> type:node]] map[cause:Web font extra:map[type:url value:https://www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff]]] type:subitems]] map[node:map[boundingRect:map[bottom:938 height:284 left:74 right:1276 top:654 width:1202] lhId:page-10-DIV nodeLabel:Floor Proceedings Tuesday, Apr 21, 2026 Convene at 10:00 a.m. Floor Webcast … path:5,HTML,2,BODY,3,MAIN,2,DIV selector:body > main.gridContainer > div#proceedings_hearings snippet:<div id="proceedings_hearings" class="fluid "> type:node] score:0.019033 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:746 height:499 left:74 right:1276 top:247 width:1202] lhId:page-1-IMG nodeLabel:Captiol 1800 path:5,HTML,2,BODY,3,MAIN,1,DIV,0,UL,0,LI,0,IMG selector:div.skdslider > ul#slider > li > img snippet:<img src="/resources/images/sliderphotos/1800_Capitol_Wing.jpg" alt="Captiol 1800"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1268 height:144 left:480 right:830 top:1124 width:350] lhId:page-22-DIV nodeLabel:Recent Senate Roll Call Votes Apr 20 | 86 (47-46) | Confirmed | PN787-1 Apr 1… path:5,HTML,2,BODY,3,MAIN,3,DIV,1,SECTION,1,DIV selector:main.gridContainer > div#content_1 > section#content_container_col2 > div.fluid snippet:<div class="fluid content_column_container"> type:node] score:0.008069 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1124 height:166 left:480 right:868 top:958 width:389] lhId:page-2-IMG nodeLabel:main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img path:5,HTML,2,BODY,3,MAIN,3,DIV,1,SECTION,0,IMG selector:main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img snippet:<img src="/resources/images/col2_senatefloor.jpg" alt="" class="content_container_img"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1245 height:121 left:74 right:424 top:1124 width:350] lhId:page-23-DIV nodeLabel:Research Tools Research Tools Commonly Searched for Legislation path:5,HTML,2,BODY,3,MAIN,3,DIV,0,SECTION,1,DIV selector:main.gridContainer > div#content_1 > section#content_container_col1 > div.fluid snippet:<div class="fluid content_column_container"> type:node] score:0.004961 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1124 height:166 left:74 right:463 top:958 width:389] lhId:page-3-IMG nodeLabel:main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img path:5,HTML,2,BODY,3,MAIN,3,DIV,0,SECTION,0,IMG selector:main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img snippet:<img src="/resources/images/33_00019.jpg" alt="" class="content_container_img"> type:node]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
main.gridContainer > div.skdslider > ul#slider > img main.gridContainer > div.skdslider > ul#slider > img
www.senate.gov/resources/images/sliderphotos/image-bg.jpg603.9 KiB536.6 KiB
Captiol 1800 div.skdslider > ul#slider > li > img
www.senate.gov/resources/images/sliderphotos/1800_Capitol_Wing.jpg376.8 KiB306.0 KiB
main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img
www.senate.gov/resources/images/col2_senatefloor.jpg167.8 KiB158.2 KiB
main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img
www.senate.gov/resources/images/33_00019.jpg84.5 KiB74.9 KiB
main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img
www.senate.gov/resources/graphic/history_lbj.jpg32.5 KiB27.1 KiB
Senate Logo div#logo_social_footer_center > div#footer_logo > a > img
www.senate.gov/resources/images/senate_logo_footer.png20.4 KiB18.8 KiB
U.S. Flag cfparam > div#find-sen > div#flag > img
www.senate.gov/resources/images/usFlag.png16.9 KiB16.7 KiB
body > main.gridContainer > div.skdslider > a.next body > main.gridContainer > div.skdslider > a.next
www.senate.gov/resources/images/right-arrow.png15.4 KiB15.2 KiB
body > main.gridContainer > div.skdslider > a.prev body > main.gridContainer > div.skdslider > a.prev
www.senate.gov/resources/images/left-arrow.png15.4 KiB15.2 KiB
www.senate.gov/resources/images/bkgnd_stripe_c.png15.1 KiB15.1 KiB
United States Senate Logo div.row > div#logo > a > img
www.senate.gov/resources/images/senate_logo.png10.6 KiB5.3 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: main.gridContainer > div.skdslider > ul#slider > img
path: 5,HTML,2,BODY,3,MAIN,1,DIV,0,UL,8,IMG
selector: main.gridContainer > div.skdslider > ul#slider > img
snippet: <img src="/resources/images/sliderphotos/image-bg.jpg">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.senate.gov/http/1.1
www.senate.gov/resources/styles/boilerplate.csshttp/1.1
www.senate.gov/resources/styles/main.csshttp/1.1
www.senate.gov/resources/styles/nav_menu.csshttp/1.1
www.senate.gov/resources/styles/skdslider.csshttp/1.1
/resources/fonts/gFonts.css?family=Source+Sans+Pro:400,30...http/1.1
www.senate.gov/resources/fonts/gFonts.css?family=Source+Serif+Pro:400,600,700http/1.1
/resources/fonts/gFonts.css?family=Libre+Baskerville:400,...http/1.1
www.senate.gov/resources/fonts/css/font-awesome.min.csshttp/1.1
www.senate.gov/resources/styles/print.csshttp/1.1
www.senate.gov/resources/scripts/respond.min.jshttp/1.1
www.senate.gov/resources/scripts/jquery-1.11.3.min.jshttp/1.1
www.senate.gov/resources/scripts/skdslider.min.jshttp/1.1
www.senate.gov/resources/scripts/main.jshttp/1.1
www.senate.gov/resources/scripts/floor_status.jshttp/1.1
www.senate.gov/resources/images/usFlag.pnghttp/1.1
www.senate.gov/resources/images/senate_logo.pnghttp/1.1
www.senate.gov/resources/images/sliderphotos/1800_Capitol_Wing.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/OldSenateChamber_bannerimage.jpghttp/1.1
/resources/images/sliderphotos/bingham-modificationists-p...http/1.1
www.senate.gov/resources/images/sliderphotos/Desks_slider_66_00019.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/States_homepageRotator.jpghttp/1.1
/resources/images/sliderphotos/women-of-the-senate-rotato...http/1.1
/resources/images/sliderphotos/Slider_inauguration_38_001...http/1.1
www.senate.gov/resources/images/sliderphotos/capitol_wide_home.jpghttp/1.1
www.senate.gov/resources/images/sliderphotos/image-bg.jpghttp/1.1
www.senate.gov/resources/images/33_00019.jpghttp/1.1
www.senate.gov/resources/images/col2_senatefloor.jpghttp/1.1
www.senate.gov/resources/graphic/history_lbj.jpghttp/1.1
www.senate.gov/resources/images/senate_logo_footer.pnghttp/1.1
www.senate.gov/resources/images/bkgnd_stripe_c.pnghttp/1.1
www.senate.gov/resources/fonts/ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woffhttp/1.1
www.senate.gov/resources/images/banner-bg.pnghttp/1.1
www.senate.gov/resources/images/senate_logo_black.pnghttp/1.1
www.senate.gov/resources/fonts/fonts/fontawesome-webfont.woff2?v=4.6.3http/1.1
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woffhttp/1.1
www.senate.gov/resources/fonts/toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woffhttp/1.1
www.senate.gov/resources/fonts/M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woffhttp/1.1
www.senate.gov/resources/images/slide-bg-active.pnghttp/1.1
www.senate.gov/resources/images/slide-bg.pnghttp/1.1
www.senate.gov/resources/images/left-arrow.pnghttp/1.1
www.senate.gov/resources/images/right-arrow.pnghttp/1.1
www.senate.gov/legislative/schedule/floor_schedule.jsonhttp/1.1
www.senate.gov/resources/images/us_sen.icohttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 253 ms
URLTime Spent
senate.gov/253 ms
www.senate.gov/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Floor Proceedings Tuesday, Apr 21, 2026 Convene at 10:00 a.m. Floor Webcast … body > main.gridContainer > div#proceedings_hearings
0.092
Learn About the Senate Explore the Senate's Constitutional foundations, its un… body > main.gridContainer
0.031
Floor Proceedings Tuesday, Apr 21, 2026 Convene at 10:00 a.m. Floor Webcast … body > main.gridContainer > div#proceedings_hearings
0.019
Recent Senate Roll Call Votes Apr 20 | 86 (47-46) | Confirmed | PN787-1 Apr 1… main.gridContainer > div#content_1 > section#content_container_col2 > div.fluid
0.008
Research Tools Research Tools Commonly Searched for Legislation main.gridContainer > div#content_1 > section#content_container_col1 > div.fluid
0.005
Public Disclosure Financial Disclosure Gift Rule/Travel Lobby Disclosure Act main.gridContainer > div#content_1 > section#content_container_col3 > div.fluid
0.005
  WATCH LIVE SENATE FLOOR PROCEEDINGS div#top-header > cfparam > div#find-sen > div#watch
0.002
Floor Activity article#proceedings_schedule_2 > ul > li.fluid > a
0.001

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.1 KiB
URLTransfer SizeEst Savings
www.senate.gov/resources/styles/boilerplate.css3.5 KiB2.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
main.gridContainer > div.skdslider > ul#slider > img main.gridContainer > div.skdslider > ul#slider > img
www.senate.gov/resources/images/sliderphotos/image-bg.jpg
main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col1 > img.content_container_img
www.senate.gov/resources/images/33_00019.jpg
main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col2 > img.content_container_img
www.senate.gov/resources/images/col2_senatefloor.jpg
main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img main.gridContainer > div#content_1 > section#content_container_col3 > img.content_container_img
www.senate.gov/resources/graphic/history_lbj.jpg
United States Senate Logo div.row > div#logo > a > img
www.senate.gov/resources/images/senate_logo.png
Senate Logo div#logo_social_footer_center > div#footer_logo > a > img
www.senate.gov/resources/images/senate_logo_footer.png
U.S. Flag cfparam > div#find-sen > div#flag > img
www.senate.gov/resources/images/usFlag.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Optimize DOM size
Forced reflow
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 30 ms
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
JavaScript execution time 0.1 s
Minimizes main-thread work 0.3 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 110 ms
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
50

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Floor Webcast article#proceedings_schedule > ul > li.fluid > a
Senate Calendar article#proceedings_schedule > ul > li.fluid > a
Executive Calendar article#proceedings_schedule > ul > li.fluid > a
Tentative Floor Schedule article#proceedings_schedule > ul > li.fluid > a
Floor Activity article#proceedings_schedule_2 > ul > li.fluid > a
Daily Digest article#proceedings_schedule_2 > ul > li.fluid > a
Congressional Record article#proceedings_schedule_2 > ul > li.fluid > a
Senate Floor Proceedings, 2014 to Present article#proceedings_schedule_2 > ul > li.fluid > a
Recent Roll Call Votes article#proceedings_schedule_2 > ul > li.fluid > a
Armed Services section#hearings > ul.floor-schedule > li.fluid > a
Energy and Natural Resources section#hearings > ul.floor-schedule > li.fluid > a
Banking, Housing, and Urban Affairs section#hearings > ul.floor-schedule > li.fluid > a
More section#hearings > ul.floor-schedule > li.fluid > a
Research Tools div.fluid > ul > li.fluid > a
Commonly Searched for Legislation div.fluid > ul > li.fluid > a
86 (47-46) ul > li.fluid > span.vote-list > a
PN787-1 ul > li.fluid > span.vote-list > a
85 (49-48) ul > li.fluid > span.vote-list > a
PN787-1 ul > li.fluid > span.vote-list > a
84 (50-49) ul > li.fluid > span.vote-list > a
H.J.Res. 140 ul > li.fluid > span.vote-list > a
All Current Session Roll Call Votes ul > ul > li.fluid > a
Financial Disclosure div.fluid > ul > li.fluid > a
Gift Rule/Travel div.fluid > ul > li.fluid > a
Lobby Disclosure Act div.fluid > ul > li.fluid > a
Women of the Senate div.fluid > ul > li.fluid > a
Senate Stories Blog div.fluid > ul > li.fluid > a
Plan Your Visit div.fluid > ul > li.fluid > a
Capitol Visitor Center div.fluid > ul > li.fluid > a
Capitol Camera div.fluid > ul > li.fluid > a
Employment div.fluid > ul > li.fluid > a
Procurement div.fluid > ul > li.fluid > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tuesday, Apr 21, 2026 div#proceedings_hearings > section#proceedings > article#proceedings_schedule > h3
Tuesday, Apr. 21, 2026 main.gridContainer > div#proceedings_hearings > section#hearings > h3

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.gridContainer > div.skdslider > ul#slider > img main.gridContainer > div.skdslider > ul#slider > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div#search-elements > form#search > input#search3 div.row > div#search-elements > form#search > input#search3

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find Your Senators Alabama Alaska Arizona Arkansas California Colorado Connecti… div#sen-dropdown-container > form > label > select#findsenator

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > div.slide-desc > h2 > a li > div.slide-desc > h2 > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn About the Senate Explore the Senate's Constitutional foundations, its un… body > main.gridContainer > div.skdslider > ul#slider
Apr 20 | 86 (47-46) | Confirmed | PN787-1 Apr 16 | 85 (49-48) | Agreed to | P… div#content_1 > section#content_container_col2 > div.fluid > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Links are distinguishable without relying on color.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
64

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.gridContainer > div.skdslider > ul#slider > img main.gridContainer > div.skdslider > ul#slider > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
body > main.gridContainer > div.skdslider > a.prev body > main.gridContainer > div.skdslider > a.prev
body > main.gridContainer > div.skdslider > a.next body > main.gridContainer > div.skdslider > a.next
body > main.gridContainer > div.skdslider > a.play-control body > main.gridContainer > div.skdslider > a.play-control

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Document has a valid `hreflang`
robots.txt is valid
Document has a valid `rel=canonical`

Send Feedback