Tools & Wizards About Us
digital.gov screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

digital.gov

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

Page Load Speed

4.8 sec in total

First Response

54 ms

Resources Loaded

3.5 sec

Page Rendered

1.2 sec

digital.gov screenshot

About Website

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

Guidance on building better digital services in government

Visit digital.gov

Key Findings

We analyzed Digital.gov page load time and found that the first response time was 54 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

digital.gov performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

digital.gov

54 ms

digital.gov

241 ms

gtm.js

75 ms

styles.css

372 ms

dbf359f887.js

49 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 48% of them (40 requests) were addressed to the original Digital.gov, 7% (6 requests) were made to Kit-free.fontawesome.com and 6% (5 requests) were made to Github.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Digital.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.2 kB (38%)

Content Size

203.8 kB

After Optimization

126.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digital.gov main page is 203.8 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. 70% of websites need less resources to load. HTML takes 84.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 68.1 kB

  • Original 84.9 kB
  • After minification 79.1 kB
  • After compression 16.9 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 68.1 kB or 80% of the original size.

Image Optimization

-21%

Potential reduce by 1.8 kB

  • Original 8.7 kB
  • After minification 6.9 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, Digital needs image optimization as it can save up to 1.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 7.3 kB

  • Original 44.4 kB
  • After minification 44.4 kB
  • After compression 37.1 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 7.3 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 13 B

  • Original 65.8 kB
  • After minification 65.8 kB
  • After compression 65.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. Digital.gov has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

59

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digital.gov

digital.gov

54 ms

digital.gov

digital.gov

241 ms

gtm.js

gtm.js

75 ms

styles.css

styles.css

372 ms

dbf359f887.js

dbf359f887.js

49 ms

9651.js

9651.js

59 ms

v2.js

v2.js

193 ms

jquery.min.js

jquery.min.js

820 ms

uswds.min.js

uswds.min.js

347 ms

common.js

common.js

347 ms

analytics.js

analytics.js

52 ms

9651.js

9651.js

41 ms

9651.json

9651.json

85 ms

linkid.js

linkid.js

69 ms

11.1.118.js

11.1.118.js

33 ms

collect

collect

16 ms

collect

collect

910 ms

hero-image_w400.png

hero-image_w400.png

1385 ms

likhitha.png

likhitha.png

1224 ms

AileenMcGraw-PIF.png

AileenMcGraw-PIF.png

1188 ms

claricechan.png

claricechan.png

1188 ms

RachelF.png

RachelF.png

1181 ms

afeijoo.png

afeijoo.png

1182 ms

impactsummit-blog-post-graphic_w400.png

impactsummit-blog-post-graphic_w400.png

1402 ms

clarice-chan-fellows-meetup_w400.png

clarice-chan-fellows-meetup_w400.png

1553 ms

adele-at-all-of-us-trailer_w400.png

adele-at-all-of-us-trailer_w400.png

1618 ms

this-weeks-idea-card-wk3_w400.png

this-weeks-idea-card-wk3_w400.png

1180 ms

us_flag_small.png

us_flag_small.png

778 ms

chevron.svg

chevron.svg

640 ms

icon-dot-gov.svg

icon-dot-gov.svg

784 ms

icon-https.svg

icon-https.svg

776 ms

digitalgov-logo.svg

digitalgov-logo.svg

797 ms

close.svg

close.svg

998 ms

search.svg

search.svg

1000 ms

gsa-logo-w100.png

gsa-logo-w100.png

1001 ms

digit-50.png

digit-50.png

1002 ms

digitalgov-icon.png

digitalgov-icon.png

1081 ms

uswds-icon.png

uswds-icon.png

1086 ms

dap-logo.png

dap-logo.png

1372 ms

uswds-logo.png

uswds-logo.png

1371 ms

18f-logo.png

18f-logo.png

1371 ms

gsa-logo.png

gsa-logo.png

1372 ms

digit-light.png

digit-light.png

1396 ms

codegov-logo.png

codegov-logo.png

1370 ms

Universal-Federated-Analytics-Min.js

Universal-Federated-Analytics-Min.js

1106 ms

js

js

1335 ms

f8c8ff73-dbc9-4242-90e4-e8cbcee02f6a

f8c8ff73-dbc9-4242-90e4-e8cbcee02f6a

737 ms

PublicSans-Regular.woff

PublicSans-Regular.woff

1458 ms

PublicSans-ExtraLight.woff

PublicSans-ExtraLight.woff

1456 ms

PublicSans-Thin.woff

PublicSans-Thin.woff

1458 ms

PublicSans-SemiBold.woff

PublicSans-SemiBold.woff

1165 ms

PublicSans-Bold.woff

PublicSans-Bold.woff

1457 ms

PublicSans-ExtraBold.woff

PublicSans-ExtraBold.woff

1457 ms

PublicSans-Black.woff

PublicSans-Black.woff

1758 ms

PublicSans-Italic.woff

PublicSans-Italic.woff

1861 ms

PublicSans-ExtraLightItalic.woff

PublicSans-ExtraLightItalic.woff

1862 ms

PublicSans-ThinItalic.woff

PublicSans-ThinItalic.woff

1759 ms

PublicSans-SemiBoldItalic.woff

PublicSans-SemiBoldItalic.woff

1754 ms

PublicSans-BoldItalic.woff

PublicSans-BoldItalic.woff

1757 ms

PublicSans-ExtraBoldItalic.woff

PublicSans-ExtraBoldItalic.woff

1865 ms

PublicSans-BlackItalic.woff

PublicSans-BlackItalic.woff

1864 ms

arrow-down.svg

arrow-down.svg

1862 ms

angle-arrow-down-white.svg

angle-arrow-down-white.svg

1860 ms

free-v4-shims.min.css

free-v4-shims.min.css

919 ms

clicks.json

clicks.json

823 ms

clicks.json

clicks.json

934 ms

clicks.json

clicks.json

932 ms

clicks.json

clicks.json

932 ms

clicks.json

clicks.json

932 ms

commits

commits

1030 ms

ga-audiences

ga-audiences

532 ms

collect

collect

277 ms

56059235

56059235

1045 ms

62405438

62405438

1046 ms

11972199

11972199

1038 ms

2413403

2413403

1028 ms

400690

400690

1033 ms

1536685

1536685

1033 ms

love-letter.png

love-letter.png

1133 ms

free-v4-font-face.min.css

free-v4-font-face.min.css

229 ms

free.min.css

free.min.css

565 ms

free-fa-solid-900.woff

free-fa-solid-900.woff

8 ms

free-fa-regular-400.woff

free-fa-regular-400.woff

39 ms

free-fa-brands-400.woff

free-fa-brands-400.woff

40 ms

Accessibility Review

digital.gov accessibility score

100

Accessibility Issues

Best Practices

digital.gov best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digital.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 Digital.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

digital.gov

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