Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

kinzingerforms.house.gov

Congressman Adam Kinzinger

Page Load Speed

1.5 sec in total

First Response

55 ms

Resources Loaded

1.3 sec

Page Rendered

190 ms

kinzingerforms.house.gov screenshot

About Website

Visit kinzingerforms.house.gov now to see the best up-to-date Kinzinger Forms House content for United States and also check out these interesting facts you probably never knew about kinzingerforms.house.gov

...

Visit kinzingerforms.house.gov

Key Findings

We analyzed Kinzingerforms.house.gov page load time and found that the first response time was 55 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster. This domain responded with an error, which can significantly jeopardize Kinzingerforms.house.gov rating and web reputation

Performance Metrics

kinzingerforms.house.gov performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value280 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

kinzingerforms.house.gov

55 ms

kinzinger.house.gov

432 ms

jquery14.js

39 ms

jquery.min.js

62 ms

style.css

60 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kinzingerforms.house.gov, 74% (70 requests) were made to Kinzinger.house.gov and 8% (8 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (472 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (18%)

Content Size

5.5 MB

After Optimization

4.5 MB

In fact, the total size of Kinzingerforms.house.gov main page is 5.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 33.1 kB

  • Original 41.4 kB
  • After minification 37.1 kB
  • After compression 8.3 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 4.4 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 33.1 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 183.3 kB

  • Original 4.4 MB
  • After minification 4.2 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. Kinzinger Forms House images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 502.5 kB

  • Original 729.8 kB
  • After minification 666.4 kB
  • After compression 227.3 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 502.5 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 285.3 kB

  • Original 341.0 kB
  • After minification 316.5 kB
  • After compression 55.7 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. Kinzingerforms.house.gov needs all CSS files to be minified and compressed as it can save up to 285.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (51%)

Requests Now

73

After Optimization

36

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

Accessibility Review

kinzingerforms.house.gov accessibility score

87

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

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

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

kinzingerforms.house.gov best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kinzingerforms.house.gov SEO score

76

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

Links do not have descriptive text

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kinzingerforms.house.gov can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kinzingerforms.house.gov main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Kinzinger Forms 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: