Tools & Wizards About Us
history.house.gov screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

history.house.gov

US House of Representatives: History, Art & Archives

Page Load Speed

954 ms in total

First Response

93 ms

Resources Loaded

544 ms

Page Rendered

317 ms

history.house.gov screenshot

About Website

Click here to check amazing History House content for United States. Otherwise, check out these important facts you probably never knew about history.house.gov

Discover the rich heritage of “the People's House” and its central role in U.S. history since 1789. Explore its unique story and the men and women who have shaped it. Browse its collections. Access hi...

Visit history.house.gov

Key Findings

We analyzed History.house.gov page load time and found that the first response time was 93 ms and then it took 861 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

history.house.gov performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.388

26/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

history.house.gov

93 ms

combined_DE99D2DC98DA2C089B01C9EBF059099B.css

50 ms

combined_4540DDBB53763AE8132D4CBDED9524A1.js

108 ms

addthis_widget.js

11 ms

layout-home.css

31 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 66% of them (37 requests) were addressed to the original History.house.gov, 29% (16 requests) were made to Historycms.house.gov and 4% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (143 ms) relates to the external source Historycms.house.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 462.0 kB (40%)

Content Size

1.1 MB

After Optimization

683.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of History.house.gov main page is 1.1 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. 45% of websites need less resources to load. Images take 581.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 63.7 kB

  • Original 83.9 kB
  • After minification 71.0 kB
  • After compression 20.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 12.9 kB, which is 15% 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 63.7 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 64.4 kB

  • Original 581.5 kB
  • After minification 517.2 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. Obviously, History House needs image optimization as it can save up to 64.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 230.0 kB

  • Original 355.6 kB
  • After minification 353.1 kB
  • After compression 125.7 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 230.0 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 104.0 kB

  • Original 124.7 kB
  • After minification 115.7 kB
  • After compression 20.8 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. History.house.gov needs all CSS files to be minified and compressed as it can save up to 104.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (18%)

Requests Now

55

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of History 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 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

history.house.gov

history.house.gov

93 ms

combined_DE99D2DC98DA2C089B01C9EBF059099B.css

combined_DE99D2DC98DA2C089B01C9EBF059099B.css

50 ms

combined_4540DDBB53763AE8132D4CBDED9524A1.js

combined_4540DDBB53763AE8132D4CBDED9524A1.js

108 ms

addthis_widget.js

addthis_widget.js

11 ms

layout-home.css

layout-home.css

31 ms

mobile.css

mobile.css

39 ms

OHH.mobile.js

OHH.mobile.js

38 ms

41413.jpeg

41413.jpeg

113 ms

300lo.json

300lo.json

36 ms

15032421143.asset

15032421143.asset

25 ms

31766.jpeg

31766.jpeg

98 ms

107.asset

107.asset

96 ms

33053.asset

33053.asset

73 ms

33055.asset

33055.asset

98 ms

37820.jpeg

37820.jpeg

86 ms

37827.asset

37827.asset

84 ms

15032419691.asset

15032419691.asset

95 ms

37359.asset

37359.asset

105 ms

44559.jpeg

44559.jpeg

111 ms

mary-norton-display.jpg

mary-norton-display.jpg

122 ms

giddings-joshua-display.jpg

giddings-joshua-display.jpg

118 ms

wic_recommended.jpg

wic_recommended.jpg

118 ms

banks_blog_recommended_110x110.jpg

banks_blog_recommended_110x110.jpg

116 ms

1a.jpg

1a.jpg

143 ms

image_carousel_background.png

image_carousel_background.png

67 ms

bkg_logo_bar.png

bkg_logo_bar.png

68 ms

logo_history_art_archives.png

logo_history_art_archives.png

83 ms

btn_search_icon.png

btn_search_icon.png

83 ms

bkg_menu.png

bkg_menu.png

66 ms

menu_institution.png

menu_institution.png

68 ms

menu_people.png

menu_people.png

83 ms

menu_exhibitions_publications.png

menu_exhibitions_publications.png

87 ms

menu_collections.png

menu_collections.png

85 ms

menu_oral_history.png

menu_oral_history.png

85 ms

menu_education.png

menu_education.png

87 ms

menu_records_research.png

menu_records_research.png

100 ms

bkg_caption_carousel.png

bkg_caption_carousel.png

92 ms

bkg_glow.png

bkg_glow.png

99 ms

bkg_page.png

bkg_page.png

100 ms

btn_recommend.png

btn_recommend.png

101 ms

btn_cite.png

btn_cite.png

104 ms

btn_print.png

btn_print.png

106 ms

btn_share.png

btn_share.png

107 ms

bkg_map_callout_home.png

bkg_map_callout_home.png

136 ms

btn_explore_map.png

btn_explore_map.png

111 ms

title_graphic_historical_highlights.png

title_graphic_historical_highlights.png

112 ms

title_graphic_from_the_blog.png

title_graphic_from_the_blog.png

110 ms

title_graphic_most_recommended.png

title_graphic_most_recommended.png

114 ms

most_recommended_thumb.png

most_recommended_thumb.png

114 ms

bkg_footer.png

bkg_footer.png

120 ms

icon_youtube.png

icon_youtube.png

134 ms

icon_twitter.png

icon_twitter.png

119 ms

bkg_citation.png

bkg_citation.png

134 ms

btn_pause_carousel.png

btn_pause_carousel.png

135 ms

btn_carousel_image.png

btn_carousel_image.png

135 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

44 ms

Accessibility Review

history.house.gov accessibility score

89

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

history.house.gov best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

history.house.gov SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

history.house.gov

Open Graph data is detected on the main page of History House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: