Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

pelosi.house.gov

Representative Nancy Pelosi |

Page Load Speed

687 ms in total

First Response

31 ms

Resources Loaded

378 ms

Page Rendered

278 ms

pelosi.house.gov screenshot

About Website

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

Key Findings

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

Performance Metrics

pelosi.house.gov performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.437

21/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 524.2 kB (31%)

Content Size

1.7 MB

After Optimization

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.

HTML Optimization

-77%

Potential reduce by 57.8 kB

  • Original 74.9 kB
  • After minification 72.8 kB
  • After compression 17.0 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.

Image Optimization

-4%

Potential reduce by 42.0 kB

  • Original 1.0 MB
  • After minification 1.0 MB

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.

JavaScript Optimization

-73%

Potential reduce by 277.2 kB

  • Original 379.7 kB
  • After minification 318.5 kB
  • After compression 102.5 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.

CSS Optimization

-85%

Potential reduce by 147.1 kB

  • Original 173.3 kB
  • After minification 169.6 kB
  • After compression 26.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.

Requests Breakdown

Number of requests can be reduced by 24 (38%)

Requests Now

63

After Optimization

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.

Accessibility Review

pelosi.house.gov accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pelosi.house.gov best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pelosi.house.gov SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: