Tools & Wizards About Us
treasurydirect.gov screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

treasurydirect.gov

Home — TreasuryDirect

Page Load Speed

2.1 sec in total

First Response

360 ms

Resources Loaded

1.3 sec

Page Rendered

462 ms

treasurydirect.gov screenshot

About Website

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

Visit treasurydirect.gov

Key Findings

We analyzed Treasurydirect.gov page load time and found that the first response time was 360 ms and then it took 1.8 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

treasurydirect.gov performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

treasurydirect.gov

360 ms

style.css

320 ms

us_flag_small.png

241 ms

icon-dot-gov.svg

251 ms

icon-https.svg

248 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Treasurydirect.gov, 9% (3 requests) were made to Gateway.foresee.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (442 ms) belongs to the original domain Treasurydirect.gov.

Page Optimization Overview & Recommendations

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

Content Size

880.7 kB

After Optimization

547.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Treasurydirect.gov main page is 880.7 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. Images take 431.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.7 kB

  • Original 42.6 kB
  • After minification 36.1 kB
  • After compression 8.0 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 6.5 kB, which is 15% 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 34.7 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 8.5 kB

  • Original 431.7 kB
  • After minification 423.2 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. Treasury Direct images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 122.8 kB

  • Original 206.8 kB
  • After minification 205.7 kB
  • After compression 84.0 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 122.8 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 167.4 kB

  • Original 199.6 kB
  • After minification 197.4 kB
  • After compression 32.2 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. Treasurydirect.gov needs all CSS files to be minified and compressed as it can save up to 167.4 kB or 84% 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 Treasury Direct. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

treasurydirect.gov

treasurydirect.gov

360 ms

style.css

style.css

320 ms

us_flag_small.png

us_flag_small.png

241 ms

icon-dot-gov.svg

icon-dot-gov.svg

251 ms

icon-https.svg

icon-https.svg

248 ms

logo-treasurydirect-color.svg

logo-treasurydirect-color.svg

249 ms

jquery.min.js

jquery.min.js

369 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

408 ms

components.js

components.js

369 ms

back-to-top.js

back-to-top.js

369 ms

Universal-Federated-Analytics-Min.js

Universal-Federated-Analytics-Min.js

28 ms

element.js

element.js

47 ms

logo-fedinvest.svg

logo-fedinvest.svg

369 ms

logo-slgsafe.svg

logo-slgsafe.svg

403 ms

IRS-DF-logo.png

IRS-DF-logo.png

420 ms

homepage-stage-bg-1.jpg

homepage-stage-bg-1.jpg

229 ms

circle-paperbond.png

circle-paperbond.png

442 ms

PublicSans-Regular.woff

PublicSans-Regular.woff

150 ms

PublicSans-Medium.woff

PublicSans-Medium.woff

149 ms

PublicSans-Light.woff

PublicSans-Light.woff

150 ms

PublicSans-ExtraLight.woff

PublicSans-ExtraLight.woff

148 ms

PublicSans-Thin.woff

PublicSans-Thin.woff

190 ms

PublicSans-SemiBold.woff

PublicSans-SemiBold.woff

191 ms

PublicSans-Bold.woff

PublicSans-Bold.woff

191 ms

PublicSans-ExtraBold.woff

PublicSans-ExtraBold.woff

184 ms

PublicSans-Black.woff

PublicSans-Black.woff

190 ms

js

js

60 ms

analytics.js

analytics.js

43 ms

gateway.min.js

gateway.min.js

34 ms

collect

collect

80 ms

fs.utils.js

fs.utils.js

78 ms

fs.compress.js

fs.compress.js

79 ms

Accessibility Review

treasurydirect.gov accessibility score

85

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

treasurydirect.gov SEO score

73

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

    EN

  • Encoding

    UTF-8

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

treasurydirect.gov

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