Tools & Wizards About Us
digitalgov.gov screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

digitalgov.gov

Digital.gov — Guidance on building better digital services in government

Page Load Speed

1.6 sec in total

First Response

20 ms

Resources Loaded

831 ms

Page Rendered

750 ms

digitalgov.gov screenshot

About Website

Visit digitalgov.gov now to see the best up-to-date Digital Gov content for United States and also check out these interesting facts you probably never knew about digitalgov.gov

Guidance on building better digital services in government

Visit digitalgov.gov

Key Findings

We analyzed Digitalgov.gov page load time and found that the first response time was 20 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

digitalgov.gov performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

digitalgov.gov

20 ms

digitalgov.gov

26 ms

digital.gov

136 ms

gtm.js

136 ms

styles.css

16 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Digitalgov.gov, 42% (20 requests) were made to Digital.gov and 29% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Digital.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.9 kB (17%)

Content Size

442.3 kB

After Optimization

365.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 38.3 kB

  • Original 47.5 kB
  • After minification 39.2 kB
  • After compression 9.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 8.3 kB, which is 17% 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 38.3 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 15.1 kB

  • Original 152.5 kB
  • After minification 137.5 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. Digital Gov images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 4 B

  • Original 164.4 kB
  • After minification 164.4 kB
  • After compression 164.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-30%

Potential reduce by 23.5 kB

  • Original 77.8 kB
  • After minification 77.8 kB
  • After compression 54.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. Digitalgov.gov needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 30% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digitalgov.gov

digitalgov.gov

20 ms

digitalgov.gov

digitalgov.gov

26 ms

digital.gov

digital.gov

136 ms

gtm.js

gtm.js

136 ms

styles.css

styles.css

16 ms

uswds-init.min.js

uswds-init.min.js

47 ms

Signup.js

Signup.js

238 ms

uswds.min.js

uswds.min.js

124 ms

main.js

main.js

125 ms

gsa-accessibility-conformance-report-acr-editor-logo_w400.png

gsa-accessibility-conformance-report-acr-editor-logo_w400.png

93 ms

feedback-communication-gentle-studio-istock-getty-images-1428649542_w400.png

feedback-communication-gentle-studio-istock-getty-images-1428649542_w400.png

216 ms

title-card-navy-peo-digital-delivering-it-that-just-works-case-study-trio_w400.jpg

title-card-navy-peo-digital-delivering-it-that-just-works-case-study-trio_w400.jpg

88 ms

us_flag_small.png

us_flag_small.png

46 ms

expand_more.svg

expand_more.svg

43 ms

icon-dot-gov.svg

icon-dot-gov.svg

44 ms

icon-https.svg

icon-https.svg

44 ms

digitalgov-logo.svg

digitalgov-logo.svg

58 ms

sprite.svg

sprite.svg

215 ms

close.svg

close.svg

341 ms

search--white.svg

search--white.svg

286 ms

digit-50.png

digit-50.png

214 ms

18f-logo.png

18f-logo.png

275 ms

digit-dark.png

digit-dark.png

280 ms

digit-light.png

digit-light.png

451 ms

va-logo.png

va-logo.png

329 ms

doj-logo.png

doj-logo.png

450 ms

gsa-logo-w100.png

gsa-logo-w100.png

451 ms

109311838

109311838

17 ms

124215424

124215424

19 ms

29952804

29952804

20 ms

form

form

82 ms

signup_form-71024b7cf10fdccc9793a9a89baa70363475c348aaae809717e528bc328035ed.css

signup_form-71024b7cf10fdccc9793a9a89baa70363475c348aaae809717e528bc328035ed.css

24 ms

css

css

37 ms

SignupForm-9abc37b11e5086724820f2dc508e39353a234ce2306a34d8e0ee565e55b8aed3.js

SignupForm-9abc37b11e5086724820f2dc508e39353a234ce2306a34d8e0ee565e55b8aed3.js

30 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

22 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7jujVj9_mf.woff

34 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qN67jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qN67jujVj9_mf.woff

48 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qO67jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qO67jujVj9_mf.woff

46 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNK7jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNK7jujVj9_mf.woff

56 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qPK7jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qPK7jujVj9_mf.woff

47 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNa7jujVj9_mf.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNa7jujVj9_mf.woff

57 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

58 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo3cOWxy40.woff

57 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmBdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmBdo3cOWxy40.woff

56 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlBdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlBdo3cOWxy40.woff

57 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmxdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmxdo3cOWxy40.woff

75 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwkxdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwkxdo3cOWxy40.woff

74 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmhdo3cOWxy40.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmhdo3cOWxy40.woff

58 ms

Accessibility Review

digitalgov.gov accessibility score

100

Accessibility Issues

Best Practices

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

digitalgov.gov SEO score

100

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

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

digitalgov.gov

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