687 ms in total
31 ms
378 ms
278 ms
Click here to check amazing Pelosi House content for United States. Otherwise, check out these important facts you probably never knew about pelosi.house.gov
Representing the 12th District of California
Visit pelosi.house.govWe analyzed Pelosi.house.gov page load time and found that the first response time was 31 ms and then it took 656 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
pelosi.house.gov performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value16.4 s
0/100
25%
Value6.6 s
37/100
10%
Value830 ms
35/100
30%
Value0.437
21/100
15%
Value16.6 s
5/100
10%
31 ms
6 ms
7 ms
18 ms
9 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 94% of them (60 requests) were addressed to the original Pelosi.house.gov, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (152 ms) belongs to the original domain Pelosi.house.gov.
Page size can be reduced by 524.2 kB (31%)
1.7 MB
1.2 MB
In fact, the total size of Pelosi.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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 57.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.8 kB or 77% of the original size.
Potential reduce by 42.0 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. Pelosi House images are well optimized though.
Potential reduce by 277.2 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 277.2 kB or 73% of the original size.
Potential reduce by 147.1 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. Pelosi.house.gov needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 85% of the original size.
Number of requests can be reduced by 24 (38%)
63
39
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pelosi House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pelosi.house.gov
31 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
6 ms
css_zhvx-jY7BKtc5CzwS2ygtUXVBw4l9s4sPkcbfS19KGI.css
7 ms
css_CQ5Mp3bkA9ZMxmmUXOtokUHprfWUsi_whSaziW9WvAk.css
18 ms
css_ixVcbpFmqoJJfQX1pq9o19y1kJe5Nr_Fvbjj85Hoquk.css
9 ms
css_i2nZNq3xVBFhoDeNVeUpBfUFnC1Kc3Z87l2uW--Kba0.css
21 ms
css_76PUPp1QdfO9-DlJGmxuwx7PU7V7pC8dlmRfZf3ZSH0.css
11 ms
js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js
19 ms
js_MGQ_rlJayLEGpg9xuwoO7aXdRkZjjRJGrWorOAprFxE.js
19 ms
js_XHDEsZ5M3UcLWIZoyXipJ3j-DhT-aOua-EOxpFrJRYo.js
46 ms
js_WSyDHMt8M6b-QDVRM_9OiVlUyPsgVZcd1xRmpIupDG0.js
46 ms
js_FZKHtlutSaoSmyEPVs6i_Ve0K3E3hGbUb6u8MEGCidI.js
49 ms
js_uwrfBOJCFVq42muTMjrq2bD-RUh8NNq_fZRTb6dsNb4.js
50 ms
js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js
49 ms
js_rRpJbTj4LGknFR0buzCTOZJr5Roy7tSlsozt8w3J4qw.js
78 ms
analytics.js
118 ms
widgets.js
135 ms
background-body.jpg
107 ms
logo.png
101 ms
button_submit_glass.png
98 ms
healthcare_btn.jpg
98 ms
covered_ca.png
97 ms
background_nav.png
97 ms
menu-leaf.png
101 ms
menu-expanded.png
100 ms
breaking.png
101 ms
background_flexslider.png
101 ms
Tibet%202016%202.jpg
124 ms
transbay%20awning.jpg
144 ms
delta%20days%202016.jpg
123 ms
planet%20lab%203.jpg
125 ms
inno%20agenda3.jpg
143 ms
pelosi-newsletter_0.png
124 ms
services_contact.png
146 ms
services_help.png
145 ms
district-map-home.jpg
146 ms
background_bill.png
144 ms
search.png
148 ms
button_search.png
145 ms
location.png
148 ms
iStock_000011144520Small.jpg
145 ms
welcome-office.jpg
151 ms
social-twitter-sm.png
146 ms
twitter.png
148 ms
social-facebook-sm.png
145 ms
facebook.png
147 ms
social-flickr-sm.png
148 ms
flickr.png
151 ms
social-youtube-sm.png
150 ms
youtube.png
152 ms
social-rss-sm.png
150 ms
rss.png
63 ms
background_footer_nav.png
59 ms
button_open.png
62 ms
bg-popup-scene.jpg
63 ms
subscribe-now-button-sb-white.png
59 ms
twitter.png
59 ms
facebook.png
59 ms
flickr.png
60 ms
youtube.png
60 ms
rss.png
60 ms
background_readmore.png
56 ms
collect
30 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
115 ms
pelosi.house.gov accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pelosi.house.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pelosi.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 Pelosi.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 Pelosi.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.
pelosi.house.gov
Open Graph data is detected on the main page of Pelosi House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: