Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

homeland.house.gov

Committee on Homeland Security – Congressional Website

Page Load Speed

825 ms in total

First Response

159 ms

Resources Loaded

666 ms

Page Rendered

0 ms

homeland.house.gov screenshot

About Website

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

Visit homeland.house.gov

Key Findings

We analyzed Homeland.house.gov page load time and found that the first response time was 159 ms and then it took 666 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

homeland.house.gov performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

homeland.house.gov

159 ms

wp-emoji-release.min.js

307 ms

email-css.css

295 ms

css

96 ms

css

110 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Homeland.house.gov, 15% (2 requests) were made to Fonts.googleapis.com and 8% (1 request) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (494 ms) belongs to the original domain Homeland.house.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.4 kB (75%)

Content Size

445.0 kB

After Optimization

109.6 kB

In fact, the total size of Homeland.house.gov main page is 445.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 235.1 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 12.6 kB

  • Original 19.3 kB
  • After minification 19.1 kB
  • After compression 6.7 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 12.6 kB or 65% of the original size.

JavaScript Optimization

-70%

Potential reduce by 164.2 kB

  • Original 235.1 kB
  • After minification 233.8 kB
  • After compression 70.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 164.2 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 158.6 kB

  • Original 190.6 kB
  • After minification 189.4 kB
  • After compression 32.0 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. Homeland.house.gov needs all CSS files to be minified and compressed as it can save up to 158.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

12

After Optimization

2

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

Accessibility Review

homeland.house.gov accessibility score

71

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

[role]s do not have all required [aria-*] attributes

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[role] values are not valid

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

homeland.house.gov SEO score

91

Search Engine Optimization Advices

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 Homeland.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 Homeland.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 description is not detected on the main page of Homeland 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: