Skip to content
Audit Complete

Results for https://house.gov

Visit site

URL substituted: You submitted https://house.gov but we scanned https://www.house.gov instead — the HTTPS certificate on the submitted hostname didn't cover that name, so we retried on the www. variant

Singapore Singapore · Singapore Completed: Apr 21, 2026 19:05 UTC
Download JSON 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)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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

Drupal · 362 peers
You 76
·
Avg 73
At average
0 50 100
Better than 73% of Drupal sites See full Drupal benchmark →
Bootstrap · 823 peers
You 76
·
Avg 73
At average
0 50 100
Better than 74% of Bootstrap sites See full Bootstrap benchmark →

Top Priorities (5)

1

1 link(s) with no accessible text

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

Accessibility › Link & Button Quality
2

4 control(s) without accessible label

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

Accessibility › Form Accessibility
3

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers
4

Cross-Origin-Opener-Policy header is missing

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

Security › Security Headers
5

External script from www.googletagmanager.com lacks integrity attribute

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

Security › Subresource Integrity
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Fhouse.gov)](https://beavercheck.com/results/d8d9fef8-97c6-4884-ac15-25f954c8c5eb)
<a href="https://beavercheck.com/results/d8d9fef8-97c6-4884-ac15-25f954c8c5eb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhouse.gov" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhouse.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. 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 audience reach.

2 accessibility issues exclude users who rely on assistive technology.
3 security gaps detected — browsers may warn visitors about your site.

Conversion Barriers

5 critical 6 warning

11 barrier(s) likely increasing bounce by ~39%.

Speed (2)

Page takes 8.2s to load

+12% bounce

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

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

Page feels frozen for 1.8s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (3)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

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 (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

4 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (3)

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, …)

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)

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

$450 investment → $4,949/month returns + USD 157,500 risk avoided

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

Investment

$450

4h · 5 findings

Monthly returns

$4,949 /mo

~$59,382 / year

  • Conversions recovered $4,948
  • Bandwidth savings $0.30

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

$150 — 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

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 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,125 / month at risk

~$157,504 / 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

+3 more

Bandwidth Waste

$0.30 /mo

3790.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~379 KB per page load
    Saves $0.30/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 2 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.

25
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
97
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.
92
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.

2.79 s

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

8.21 s

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

1.84 s

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

0.258

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

6.44 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.

9.71 s

Detailed Report

Audit breakdown by category with detailed findings.

25

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.

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.258097] map[node:map[boundingRect:map[bottom:1122 height:469 left:10 right:402 top:653 width:392] lhId:page-6-DIV nodeLabel:Legislative Activity Committee Schedules Floor Proceedings Recent Votes Bills &… path:1,HTML,1,BODY,4,DIV,0,DIV,1,DIV,0,SECTION,1,DIV,1,DIV,0,DIV,1,DIV selector:div.region > div.home-layout > div.home-layout__row > div.home-layout__top-right snippet:<div class="home-layout__top-right home-layout__section col-xs-16 col-lg-7"> type:node] score:0.22137] map[node:map[boundingRect:map[bottom:5199 height:4921 left:0 right:412 top:278 width:412] lhId:page-7-SECTION nodeLabel:Visiting the House Check out the info you need before coming to the People's H… path:1,HTML,1,BODY,4,DIV,0,DIV,1,DIV,0,SECTION selector:div.dialog-off-canvas-main-canvas > div#main-content-section > div.row > section.col-xs-16 snippet:<section class="col-xs-16"> type:node] score:0.036727]]

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:53.433 source:map[column:156 line:16 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc 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:0.086 source:map[column:368 line:456 type:source-location url:https://www.house.gov/ruxitagentjs_ICA7NQVfqrux_10331260218130851.js urlProvider:network]] map[reflowTime:33.503 source:map[column:15470 line:76 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:8.419 source:map[column:80171 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:3.648 source:map[column:50118 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.61 source:map[column:50843 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.494 source:map[column:50901 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.464 source:map[column:50965 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:1.24 source:map[column:50140 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.59 source:map[column:51910 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:4.465 source:map[column:84729 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc 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
Interior of the U.S. Capitol dome. div.owl-stage > div.owl-item > div.carousel-item > img
/sites/default/files/styles/large/public/2023-10/Capitol ...403.7 KiB375.6 KiB
Home div.row > div.col-xs-16 > div.region > a.logo
www.house.gov/sites/default/themes/housegov/images/houseLogoScreenIn.png28.8 KiB19.5 KiB
section#committee-schedules > div.carousel-controls > a.right > span.icon-next section#committee-schedules > div.carousel-controls > a.right > span.icon-next
www.house.gov/sites/default/themes/housegov/images/arrows-sprite.png16.9 KiB16.2 KiB
House Floor Proceedings div.owl-stage > div.owl-item > div.carousel-item > img
/sites/default/files/styles/large/public/2023-01/Floor Pr...44.1 KiB15.9 KiB
Watch Most Recent House Floor Activity div#carousel-events > div.view-header > div#homepage-committee-schedules-houselive > a.ext
www.house.gov/sites/default/themes/housegov/images/bgSprite.png14.8 KiB7.4 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-5-IMG
nodeLabel: What to Know Before Visiting the House
path: 1,HTML,1,BODY,4,DIV,0,DIV,1,DIV,0,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.owl-stage > div.owl-item > div.carousel-item > img
snippet: <img loading="lazy" src="/sites/default/files/styles/large/public/2024-10/constituent_pic_cap_rotun…" width="480" height="360" alt="What to Know Before Visiting the House">

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.house.gov/http/1.1
www.house.gov/ruxitagentjs_ICA7NQVfqrux_10331260218130851.jshttp/1.1
/sites/default/files/css/css_vKwGOib_wDyOY1O6NucuWZVuQj0p...http/1.1
/sites/default/files/css/css_z0wHwbPsLix_f19iiTkAgbSGcT7P...http/1.1
www.house.gov/sites/default/themes/housegov/logo.svghttp/1.1
www.house.gov/sites/default/themes/housegov/images/map-home-states.gifhttp/1.1
www.house.gov/core/assets/vendor/jquery/jquery.min.js?v=4.0.0http/1.1
/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2T...http/1.1
www.house.gov/sites/default/themes/housegov/images/header_bg_mobile.jpghttp/1.1
www.house.gov/sites/default/themes/housegov/images/houseLogoScreen.gifhttp/1.1
www.house.gov/sites/default/themes/housegov/images/arrows-sprite.pnghttp/1.1
www.house.gov/sites/default/themes/housegov/images/bgSprite.pnghttp/1.1
/sites/default/files/styles/large/public/2024-10/constitu...http/1.1
/sites/default/files/styles/large/public/2023-10/Capitol ...http/1.1
/sites/default/files/styles/large/public/uploads/images-s...http/1.1
/sites/default/files/styles/large/public/2023-01/Floor Pr...http/1.1
www.house.gov/in-session.phphttp/1.1
www.house.gov/sites/default/themes/housegov/images/bgTabsFeatureActive.gifhttp/1.1
www.house.gov/sites/default/themes/housegov/images/houseLogoScreenIn.pnghttp/1.1
/sites/default/themes/housegov/components/house-in-sessio...http/1.1
www.house.gov/sites/default/themes/housegov/favicon.icohttp/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/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
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
www.house.gov/1.4 s

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
Legislative Activity Committee Schedules Floor Proceedings Recent Votes Bills &… div.region > div.home-layout > div.home-layout__row > div.home-layout__top-right
0.221
Visiting the House Check out the info you need before coming to the People's H… div.dialog-off-canvas-main-canvas > div#main-content-section > div.row > section.col-xs-16
0.037

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation3.3 s
Other660 ms
Style & Layout580 ms
Script Parsing & Compilation266 ms
Parse HTML & CSS253 ms
Rendering137 ms
Garbage Collection95 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 22.9 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_z0wHwbPsLix_f19iiTkAgbSGcT7P...27.1 KiB22.9 KiB

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

Optimize DOM size
Font display
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,234 KiB
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 240 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
INP breakdown
Avoid non-composited animations
97

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accessibility section#block-footer-menu > ul.menu > li.expanded > a
Contact Webmaster section#block-footer-menu > ul.menu > li.expanded > a
Feature Stories section#block-footer-menu > ul.menu > li.expanded > a
Privacy Policy section#block-footer-menu > ul.menu > li.expanded > a
Site Map section#block-footer-menu > ul.menu > li.expanded > a
Site Tools section#block-footer-menu > ul.menu > li.expanded > a
Terms of Use section#block-footer-menu > ul.menu > li.expanded > a
Watch live.house.gov section#block-footer-menu > ul.menu > li.expanded > a

These items highlight common accessibility best practices.

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
`<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
Identical links have the same purpose.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
TypeError: $(...).accordion is not a function at Object.attach (https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc:73:1407) at https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc:15:427 at Array.forEach (<anonymous>) at Drupal.attachBehaviors (https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc:15:353) at https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc:16:373 at HTMLDocument.listener (https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc:16:161)
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
Page has the HTML doctype
Properly defines charset
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

87
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
97
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

658 ms

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

1.30 s

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

72 ms

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

0.192

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

696 ms

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

1.90 s

Detailed Report

Audit breakdown by category with detailed findings.

87

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.

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.192331] map[node:map[boundingRect:map[bottom:1235 height:556 left:195 right:1155 top:679 width:960] lhId:page-17-DIV nodeLabel:House Overview Representatives Leadership Committees Officers and Organizations… path:1,HTML,1,BODY,4,DIV,0,DIV,1,DIV,0,SECTION,1,DIV,1,DIV,1,DIV selector:section.col-xs-16 > div.region > div.home-layout > div.row snippet:<div class="row"> type:node] score:0.192331]]

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:80.018 source:map[column:156 line:16 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc 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:27.586 source:map[column:86369 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:6.436 source:map[column:50118 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:1.232 source:map[column:50843 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.501 source:map[column:50901 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.439 source:map[column:50965 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:37.842 source:map[column:80171 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:0.673 source:map[column:51910 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:1.132 source:map[column:50140 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc urlProvider:network]] map[reflowTime:4.177 source:map[column:84729 line:63 type:source-location url:https://www.house.gov/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2TocOq1F97fQZRE.js?scope=footer&delta=1&language=en&theme=housegov&include=eJxtjlESgzAIRC8k5kgORoyZJiED2NbbN-1o04_-LW93Ac9CznOuXKiYjhvvSoHvAB8FsYCSauQyND_aMQmtk-E8rSwZzUgces-ytEhnAz0txXJzi-wV03iOw7XezcymJlihdanzkHjGBGpHy4fON85UMRC00_qLz3c9ylumP9ZV7RY_0rfwAkQKZbc 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
Interior of the U.S. Capitol dome. div.owl-stage > div.owl-item > div.carousel-item > img
/sites/default/files/styles/large/public/2023-10/Capitol ...403.7 KiB375.6 KiB
Image of House Chamber div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...28.2 KiB21.5 KiB
A lighthouse by the ocean div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...27.6 KiB21.0 KiB
Home div.row > div.col-xs-16 > div.region > a.logo
www.house.gov/sites/default/themes/housegov/images/houseLogoScreenIn.png28.8 KiB19.5 KiB
Emancipation Hall in the Capitol Visitor Center div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...23.9 KiB17.8 KiB
Orchid at the United States Botanic Garden div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...23.3 KiB17.3 KiB
Logo of Kids in the House div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...23.0 KiB17.1 KiB
Black and white image of a group of Hispanic American Congressmen div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...22.2 KiB16.5 KiB
section#committee-schedules > div.carousel-controls > a.right > span.icon-next section#committee-schedules > div.carousel-controls > a.right > span.icon-next
www.house.gov/sites/default/themes/housegov/images/arrows-sprite.png16.9 KiB16.2 KiB
House Floor Proceedings div.owl-stage > div.owl-item > div.carousel-item > img
/sites/default/files/styles/large/public/2023-01/Floor Pr...44.1 KiB15.9 KiB
Black and white image of a Congresswoman standing in front of U.S. flag div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...20.1 KiB14.9 KiB
Congressman Joseph Hayne Rainey div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...19.6 KiB14.6 KiB
logo for Wounded Warrior Program div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...16.3 KiB12.1 KiB
Congressional App Challenge div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...15.9 KiB11.8 KiB
Artistic rendering of a former Congressman div.carousel-caption--owl > a > div.carousel-image > img
/sites/default/files/styles/homepage_carousel/public/uplo...10.7 KiB7.9 KiB
Watch Most Recent House Floor Activity div#carousel-events > div.view-header > div#homepage-committee-schedules-houselive > a.ext
www.house.gov/sites/default/themes/housegov/images/bgSprite.png14.8 KiB7.4 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-16-IMG
nodeLabel: What to Know Before Visiting the House
path: 1,HTML,1,BODY,4,DIV,0,DIV,1,DIV,0,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.owl-stage > div.owl-item > div.carousel-item > img
snippet: <img loading="lazy" src="/sites/default/files/styles/large/public/2024-10/constituent_pic_cap_rotun…" width="480" height="360" alt="What to Know Before Visiting the House">

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.house.gov/http/1.1
www.house.gov/ruxitagentjs_ICA7NQVfqrux_10331260218130851.jshttp/1.1
/sites/default/files/css/css_vKwGOib_wDyOY1O6NucuWZVuQj0p...http/1.1
/sites/default/files/css/css_z0wHwbPsLix_f19iiTkAgbSGcT7P...http/1.1
www.house.gov/sites/default/themes/housegov/logo.svghttp/1.1
www.house.gov/sites/default/themes/housegov/images/map-home-states.gifhttp/1.1
www.house.gov/core/assets/vendor/jquery/jquery.min.js?v=4.0.0http/1.1
/sites/default/files/js/js_yLfC_csMovnaXacCikH96zR8H2WU2T...http/1.1
www.house.gov/sites/default/themes/housegov/images/bgHTML.jpghttp/1.1
www.house.gov/sites/default/themes/housegov/images/bgBody_lg.jpghttp/1.1
www.house.gov/sites/default/themes/housegov/images/houseLogoScreen.gifhttp/1.1
www.house.gov/sites/default/themes/housegov/images/bgFind.jpghttp/1.1
www.house.gov/sites/default/themes/housegov/images/arrows-sprite.pnghttp/1.1
www.house.gov/sites/default/themes/housegov/images/bgSprite.pnghttp/1.1
/sites/default/files/styles/large/public/2024-10/constitu...http/1.1
/sites/default/files/styles/large/public/2023-10/Capitol ...http/1.1
/sites/default/files/styles/large/public/uploads/images-s...http/1.1
/sites/default/files/styles/large/public/2023-01/Floor Pr...http/1.1
www.house.gov/in-session.phphttp/1.1
www.house.gov/sites/default/themes/housegov/images/houseLogoScreenIn.pnghttp/1.1
/sites/default/themes/housegov/components/house-in-sessio...http/1.1
www.house.gov/sites/default/themes/housegov/images/bgTabsFeatureActive.gifhttp/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
/sites/default/files/styles/homepage_carousel/public/uplo...http/1.1
www.house.gov/sites/default/themes/housegov/favicon.icohttp/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&sn=v_4_...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&flavor=...http/1.1
/rb_84936baa-290a-41c1-8aba-c50589e8f708?type=js3&flavor=...http/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
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 21.4 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_z0wHwbPsLix_f19iiTkAgbSGcT7P...27.1 KiB21.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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

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
House Overview Representatives Leadership Committees Officers and Organizations… section.col-xs-16 > div.region > div.home-layout > div.row
0.192
Max Potential First Input Delay 100 ms
Time to Interactive 1.9 s
Document request latency
Optimize DOM size
Font display
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,546 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 0.6 s
Minimizes main-thread work 1.1 s
Avoid long main-thread tasks 3 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 10 ms
INP breakdown
Avoid non-composited animations
97

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accessibility section#block-footer-menu > ul.menu > li.expanded > a
Contact Webmaster section#block-footer-menu > ul.menu > li.expanded > a
Feature Stories section#block-footer-menu > ul.menu > li.expanded > a
Privacy Policy section#block-footer-menu > ul.menu > li.expanded > a
Site Map section#block-footer-menu > ul.menu > li.expanded > a
Site Tools section#block-footer-menu > ul.menu > li.expanded > a
Terms of Use section#block-footer-menu > ul.menu > li.expanded > a
Watch live.house.gov section#block-footer-menu > ul.menu > li.expanded > a

These items highlight common accessibility best practices.

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
`<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
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

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
Page has the HTML doctype
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

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

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

Send Feedback