Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

design.cms.gov

Introduction - CMS Design System

Page Load Speed

454 ms in total

First Response

97 ms

Resources Loaded

357 ms

Page Rendered

0 ms

About Website

Click here to check amazing Design CMS content for United States. Otherwise, check out these important facts you probably never knew about design.cms.gov

The CMS Design System is a set of open source design and front-end development resources for creating Section 508 compliant, responsive, and consistent websites.

Visit design.cms.gov

Key Findings

We analyzed Design.cms.gov page load time and found that the first response time was 97 ms and then it took 357 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

design.cms.gov performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.542

13/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

design.cms.gov

97 ms

core-theme.css

80 ms

utag.sync.js

60 ms

app-9125924eb431aadadf01.js

124 ms

framework-b71c4cc9499f57f6e354.js

41 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 71% of them (5 requests) were addressed to the original Design.cms.gov, 29% (2 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (124 ms) belongs to the original domain Design.cms.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 835.0 kB (76%)

Content Size

1.1 MB

After Optimization

262.4 kB

In fact, the total size of Design.cms.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. Only 10% of websites need less resources to load. Javascripts take 735.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 287.5 kB

  • Original 358.8 kB
  • After minification 358.7 kB
  • After compression 71.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. 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 287.5 kB or 80% of the original size.

JavaScript Optimization

-74%

Potential reduce by 547.4 kB

  • Original 735.2 kB
  • After minification 735.1 kB
  • After compression 187.8 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 547.4 kB or 74% of the original size.

CSS Optimization

-1%

Potential reduce by 45 B

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 3.3 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. Design.cms.gov has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (67%)

Requests Now

6

After Optimization

2

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Design CMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

design.cms.gov accessibility score

92

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

Buttons do not have an accessible name

Best Practices

design.cms.gov best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

design.cms.gov SEO score

78

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 Design.cms.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 Design.cms.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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: