Tools & Wizards About Us
doe.in.gov screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

doe.in.gov

DOE: Home

Page Load Speed

1.3 sec in total

First Response

120 ms

Resources Loaded

905 ms

Page Rendered

265 ms

doe.in.gov screenshot

About Website

Welcome to doe.in.gov homepage info - get ready to check DOE In best content for United States right away, or after learning these important things about doe.in.gov

Visit doe.in.gov

Key Findings

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

Performance Metrics

doe.in.gov performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value36.9 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value3,790 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

www.doe.in.gov

120 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

43 ms

css_0M-rJCd4MWs-O8FG-exb7PBophdTlD93MB720jOyqV0.css

52 ms

css_wBuHSew-j9KkwaGqKVJuBBe29qARlolHu7yxgZOy1jk.css

55 ms

css_7sjCzZ1eJGQuG50KoFqUXr-jHk_r6bg2QzyeRN5Mp4Y.css

57 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 72% of them (31 requests) were addressed to the original Doe.in.gov, 7% (3 requests) were made to S.ytimg.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (236 ms) relates to the external source S.ytimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 623.6 kB (59%)

Content Size

1.1 MB

After Optimization

437.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Doe.in.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. 40% of websites need less resources to load. Javascripts take 445.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 33.7 kB

  • Original 44.7 kB
  • After minification 41.0 kB
  • After compression 11.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. 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 33.7 kB or 75% of the original size.

Image Optimization

-12%

Potential reduce by 31.4 kB

  • Original 257.4 kB
  • After minification 226.0 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, DOE In needs image optimization as it can save up to 31.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 300.9 kB

  • Original 445.9 kB
  • After minification 400.4 kB
  • After compression 144.9 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 300.9 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 257.6 kB

  • Original 313.2 kB
  • After minification 311.2 kB
  • After compression 55.6 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. Doe.in.gov needs all CSS files to be minified and compressed as it can save up to 257.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DOE In. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.doe.in.gov

www.doe.in.gov

120 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

43 ms

css_0M-rJCd4MWs-O8FG-exb7PBophdTlD93MB720jOyqV0.css

css_0M-rJCd4MWs-O8FG-exb7PBophdTlD93MB720jOyqV0.css

52 ms

css_wBuHSew-j9KkwaGqKVJuBBe29qARlolHu7yxgZOy1jk.css

css_wBuHSew-j9KkwaGqKVJuBBe29qARlolHu7yxgZOy1jk.css

55 ms

css_7sjCzZ1eJGQuG50KoFqUXr-jHk_r6bg2QzyeRN5Mp4Y.css

css_7sjCzZ1eJGQuG50KoFqUXr-jHk_r6bg2QzyeRN5Mp4Y.css

57 ms

css_ohLEdzwv3LwJjBXjdpdIms0cgh9y5xMnhEFSQ9tEqT8.css

css_ohLEdzwv3LwJjBXjdpdIms0cgh9y5xMnhEFSQ9tEqT8.css

60 ms

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

80 ms

js_nT-3TqmhkiIn30tHICx1inWtvQizOLtaBPI9cbRYVJE.js

js_nT-3TqmhkiIn30tHICx1inWtvQizOLtaBPI9cbRYVJE.js

67 ms

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

76 ms

js_juV8max7J8nCiceCgEo0-MtO5c96GZUl6mVZJlxO43I.js

js_juV8max7J8nCiceCgEo0-MtO5c96GZUl6mVZJlxO43I.js

75 ms

js_b61LJMuM9aVQlPwHZS7DdD8A0otqi8BLxr3_Dw6o_OU.js

js_b61LJMuM9aVQlPwHZS7DdD8A0otqi8BLxr3_Dw6o_OU.js

77 ms

6YV2Z6ZVY-M

6YV2Z6ZVY-M

147 ms

analytics.js

analytics.js

42 ms

bg_header_lineless.gif

bg_header_lineless.gif

39 ms

header.jpg

header.jpg

135 ms

menu-leaf.png

menu-leaf.png

39 ms

search-button.png

search-button.png

37 ms

lightbulb.png

lightbulb.png

38 ms

hoosierreaders.gif

hoosierreaders.gif

64 ms

appsplash01.png

appsplash01.png

114 ms

bicentennial.png

bicentennial.png

91 ms

today_minical_bg.gif

today_minical_bg.gif

62 ms

footer_bg.gif

footer_bg.gif

65 ms

icons_fb.gif

icons_fb.gif

90 ms

icons_twitter.gif

icons_twitter.gif

87 ms

icons_rss.gif

icons_rss.gif

90 ms

icons_pod.gif

icons_pod.gif

116 ms

icons_youtube.gif

icons_youtube.gif

115 ms

icons_flickr.gif

icons_flickr.gif

118 ms

extlink_s.png

extlink_s.png

119 ms

collect

collect

12 ms

collect

collect

58 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

108 ms

www-embed-player.js

www-embed-player.js

134 ms

base.js

base.js

236 ms

css_2mcTG2xobSnaX2pXOUP97nw61PM9VZw2o7FBwkc5GYM.css

css_2mcTG2xobSnaX2pXOUP97nw61PM9VZw2o7FBwkc5GYM.css

27 ms

css_qDMP1e2PFQkInyJ786VvoPDUGG9dxTNEUh6TNai_gJ8.css

css_qDMP1e2PFQkInyJ786VvoPDUGG9dxTNEUh6TNai_gJ8.css

28 ms

css_QN2i6iEUqEUPstm59_ALsOBKg-DcUIzl3VyTeBzN5Ps.css

css_QN2i6iEUqEUPstm59_ALsOBKg-DcUIzl3VyTeBzN5Ps.css

66 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

41 ms

ad_status.js

ad_status.js

44 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

85 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

93 ms

nr-852.min.js

nr-852.min.js

19 ms

Accessibility Review

doe.in.gov accessibility score

96

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-hidden="true"] elements contain focusable descendents

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

doe.in.gov best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

doe.in.gov SEO score

75

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

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 Doe.in.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 Doe.in.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

doe.in.gov

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