1.8 sec in total
10 ms
541 ms
1.3 sec
Welcome to house.gov homepage info - get ready to check House best content for United States right away, or after learning these important things about house.gov
Visit house.govWe analyzed House.gov page load time and found that the first response time was 10 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
house.gov performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value8.9 s
1/100
25%
Value4.1 s
79/100
10%
Value820 ms
35/100
30%
Value0.091
92/100
15%
Value7.6 s
46/100
10%
10 ms
156 ms
9 ms
14 ms
94 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 93% of them (28 requests) were addressed to the original House.gov, 7% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (156 ms) belongs to the original domain House.gov.
Page size can be reduced by 538.2 kB (31%)
1.7 MB
1.2 MB
In fact, the total size of House.gov main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 236.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 30.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 236.2 kB or 83% of the original size.
Potential reduce by 88.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. House images are well optimized though.
Potential reduce by 195.9 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 195.9 kB or 70% of the original size.
Potential reduce by 17.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. House.gov needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 36% of the original size.
We found no issues to fix!
28
28
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of House. According to our analytics all requests are already optimized.
house.gov
10 ms
www.house.gov
156 ms
css_v3REz0xurvVTvtUUGPhOdCfHf8hV4t_JmIRihBI3qXY.css
9 ms
css_FseOM1fF17ZrjU9roJ519HLwQ4l_VMe7EFy4f8htLJw.css
14 ms
js_TIeocgxJOAnvzHSzJyzn3gRaJGupSMLBUDT-h3blQ5s.js
94 ms
gtm.js
136 ms
bgHTML.jpg
26 ms
bgBody_lg.jpg
24 ms
houseLogoScreen.gif
33 ms
logo.svg
26 ms
bgFind.jpg
32 ms
Speaker%20Mike%20Johnson%20Sworn%20In.png
33 ms
Capitol%20Dome%20Interior.png
43 ms
dome-night2-480-360.jpg
32 ms
Floor%20Proceedings.png
47 ms
arrows-sprite.png
55 ms
bgSprite.png
39 ms
map-home-states.gif
63 ms
congressional-app-challenge_slider%20800x600_0.jpg
56 ms
home-art-2014-mn07.jpg
49 ms
home-life-cvc.jpg
51 ms
home-life-kids.jpg
66 ms
home-life-usbg.jpg
57 ms
home-life-history.jpg
111 ms
home-life-wwp.jpg
113 ms
home-life-longworth.jpg
69 ms
home-life-baic.jpg
112 ms
home-life-haic.jpg
140 ms
home-life-women.jpg
111 ms
js
79 ms
house.gov accessibility score
house.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
house.gov SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise House.gov can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that House.gov main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
house.gov
Open Graph description is not detected on the main page of House. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: