Analyze

data.gov: Data.gov

The home of the U.S. Government’s open data Here you will find data, tools, and resources to conduct research, develop web and mobile applications, design data visualizations, and more.

Page load speed analysis

  • 80/100

    Good result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    31 ms

  • Resources loaded

    539 ms

  • Page rendered

    267 ms

  • Total page load time

    837 ms

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

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

Page optimization

  • HTML 43.5 kB
    Images 349.8 kB
    Javascripts 692.2 kB
    CSS 352.0 kB

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

    • Original 43.5 kB
    • After minification 39.0 kB
    • After compression 10.2 kB

    HTML optimization

    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.3 kB or 77% of the original size.

    • Original 349.8 kB
    • After optimization 333.4 kB

    Image optimization

    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. Data images are well optimized though.

    • Original 692.2 kB
    • After minification 672.1 kB
    • After compression 223.7 kB

    JavaScript optimization

    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 468.5 kB or 68% of the original size.

    • Original 352.0 kB
    • After minification 323.8 kB
    • After compression 63.7 kB

    CSS optimization

    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. Data.gov needs all CSS files to be minified and compressed as it can save up to 288.2 kB or 82% of the original size.

Network requests diagram

  • data.gov
  • www.data.gov
  • wp-emoji-release.min.js
  • q-a-plus.css
  • zebra_tooltips.css
  • styles.css
  • colorbox.css
  • templates.css
  • chosen.min.css
  • public.css
  • css
  • main.min.css
  • rei.css
  • jquery.min.js
  • flowplayer-3.2.6.min.js
  • smartpaginator.min.js
  • jquery-tablesorter-min.js
  • jsapi
  • wpp-popup-frontend.js
  • chosen.jquery.min.js
  • public.js
  • respond.min.js
  • modernizr-2.7.1.min.js
  • jquery.dataTables.min.js
  • dataTables.fixedColumns.min.js
  • dataTables.scroller.min.js
  • ext-link-handler.js
  • dap.min.js
  • external-tracking.min.js
  • q-a-plus.js
  • zebra_tooltips.js
  • wp-external-links.js
  • jquery.form.min.js
  • scripts.js
  • scripts.min.js
  • wp-embed.min.js
  • analytics.js
  • ga.js
  • logo.png
  • twitter.png
  • v0SdcGFAl2aezM9Vq_aFTQ.ttf
  • nj47mAZe0mYUIySgfn0wpQ.ttf
  • zJY4gsxBiSo5L7tNutxFNg.ttf
  • DvlFBScY1r-FMtZSYIYoYw.ttf
  • fontawesome-webfont.woff
  • datagov-icons.woff
  • logo.svg
  • collect
  • collect
  • __utm.gif
  • nr-852.min.js

Our browser made a total of 51 requests to load all elements on the main page. We found that 65% of them (33 requests) were addressed to the original Data.gov, 10% (5 requests) were made to Google-analytics.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (229 ms) relates to the external source Google-analytics.com.

Additional info on data.gov

Requests

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

27

Javascripts

6

Images

10

CSS

1

AJAX

44

All

Possible request optimization

1

Javascripts

6

Images

1

CSS

1

AJAX

35

Optimized

9

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.data.gov/ before it reached this domain.

IP address

Data.gov uses IP addresses which are currently shared with 16 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

data.gov

aiononline.com

umuc.edu

americascup.com

discovery.com

143.204.158.82

data.gov

theladders.com

nikkansports.com

people.com

dailyherald.com

143.204.158.99

data.gov

suntrust.com

kelkoo.co.uk

pornpros.com

akb48.co.jp

143.204.158.127

DNS records

Type Host Target/ip TTL Other
A

data.gov

34.193.244.109 300
NS

data.gov

dns4.gsa.gov 10800
NS

data.gov

dns2.gsa.gov 10800
NS

data.gov

dns3.gsa.gov 10800
NS

data.gov

dns5.gsa.gov 10800

HTTPS certificate

SSL Certificate

Data.gov has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 64.6% of all visits is United States. It’s good for Data.gov that their server is also located in United States, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Good result

Social Sharing Optimization

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

data.gov

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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

Share this report in social media

Analyze another website

Analyze