8 sec in total
308 ms
7.4 sec
248 ms
Visit eia.gov now to see the best up-to-date EIA content for United States and also check out these interesting facts you probably never knew about eia.gov
Energy Information Administration - EIA - Official Energy Statistics from the U.S. Government
Visit eia.govWe analyzed Eia.gov page load time and found that the first response time was 308 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eia.gov performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value8.9 s
1/100
25%
Value11.4 s
5/100
10%
Value1,130 ms
23/100
30%
Value0.656
8/100
15%
Value18.4 s
3/100
10%
308 ms
235 ms
13 ms
15 ms
21 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 85% of them (80 requests) were addressed to the original Eia.gov, 3% (3 requests) were made to Search.usa.gov and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Eia.gov.
Page size can be reduced by 1.1 MB (40%)
2.6 MB
1.6 MB
In fact, the total size of Eia.gov main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 64.1 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 64.1 kB or 73% of the original size.
Potential reduce by 125.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. EIA images are well optimized though.
Potential reduce by 690.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 690.0 kB or 66% of the original size.
Potential reduce by 185.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. Eia.gov needs all CSS files to be minified and compressed as it can save up to 185.6 kB or 86% of the original size.
Number of requests can be reduced by 32 (35%)
92
60
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EIA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
eia.gov
308 ms
www.eia.gov
235 ms
screen.css
13 ms
jquery-ui-dp.custom.css
15 ms
EIA_global.css
21 ms
jquery-1.11.1.min.js
19 ms
jquery-migrate-1.2.1.min.js
14 ms
jquery-ui-1.10.3.custom.min.js
50 ms
jquery.ui.touch-punch.min.js
14 ms
eia_utils.js
15 ms
eia_global.js
13 ms
highcharts.js
41 ms
highcharts-more.js
42 ms
exporting.js
45 ms
no-data-to-display.js
39 ms
ga-file-downloads.js
39 ms
jquery.fancybox.css
40 ms
jquery.fancybox.pack.js
41 ms
survey_engine.js
41 ms
layout.css
39 ms
addthis_widget.js
42 ms
ga.js
133 ms
remote.loader.js
120 ms
whatsnew.htm
163 ms
index.php
287 ms
social-twitter.jpg
55 ms
social-facebook.jpg
54 ms
header_bg.jpg
58 ms
eia_logo_print.png
55 ms
eia_logo.jpg
56 ms
es_off.png
56 ms
es_dropdown.png
59 ms
topics_off.png
57 ms
topics_dropdown.png
60 ms
geo_off.png
59 ms
geo_dropdown.png
64 ms
tools_off.png
60 ms
tools_dropdown.png
61 ms
learn_off.png
61 ms
learn_dropdown.png
62 ms
news_off.png
65 ms
news_dropdown.png
63 ms
arrow_go.png
65 ms
az_off.png
66 ms
a-z_dropdown.png
68 ms
homepage_banner1.jpg
67 ms
home_feature_overlay.png
68 ms
homepage_banner2.jpg
67 ms
homepage_banner3.jpg
72 ms
homepage_banner4.jpg
69 ms
homepage_banner5.jpg
70 ms
homepage_banner6.jpg
70 ms
h_line_shadow_feature_banner.png
69 ms
h_line_shadow_rc.png
71 ms
feature_p1.png
6295 ms
features_bg.jpg
72 ms
electricity_browser.jpg
71 ms
feature_conference2016.jpg
52 ms
energy_mapping_system.jpg
50 ms
up.png
50 ms
down.png
50 ms
kids-winter.png
48 ms
footer_bg.jpg
49 ms
eia_address.png
48 ms
arrow_gr_r.png
48 ms
external_link.png
47 ms
facebook.png
48 ms
twitter.png
48 ms
youtube.png
47 ms
flickr.png
47 ms
linkedin.png
46 ms
email.png
47 ms
rss.png
46 ms
homepage_banner1.jpg
1083 ms
homepage_banner2.jpg
382 ms
homepage_banner3.jpg
349 ms
homepage_banner4.jpg
1836 ms
homepage_banner5.jpg
1704 ms
homepage_banner6.jpg
709 ms
thumbs3_on.png
381 ms
thumbs3.png
383 ms
sayt.css
33 ms
sayt_loader_libs.js
35 ms
stats.js
35 ms
__utm.gif
38 ms
print.css
5 ms
300lo.json
29 ms
widgets.js
22 ms
all.js&version=v2.0
378 ms
ui-bg_flat_75_ffffff_40x100.png
52 ms
sh.7c7179124ea24ac6ba46caac.html
46 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
35 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
16 ms
jot
100 ms
eia.gov accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eia.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
eia.gov SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eia.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 Eia.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.
eia.gov
Open Graph description is not detected on the main page of EIA. 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: