Tools & Wizards About Us
explore.data.gov screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

explore.data.gov

Data.gov

Page Load Speed

2.4 sec in total

First Response

32 ms

Resources Loaded

1.9 sec

Page Rendered

435 ms

explore.data.gov screenshot

About Website

Click here to check amazing Explore Data content for United States. Otherwise, check out these important facts you probably never knew about explore.data.gov

Visit explore.data.gov

Key Findings

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

Performance Metrics

explore.data.gov performance score

0

Network Requests Diagram

dataset

32 ms

select2.min.css

22 ms

main.min.css

57 ms

harvest.css

34 ms

leaflet.css

33 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Explore.data.gov, 13% (5 requests) were made to Google-analytics.com and 5% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Catalog.data.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 725.0 kB (75%)

Content Size

967.0 kB

After Optimization

242.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 156.3 kB

  • Original 172.8 kB
  • After minification 103.6 kB
  • After compression 16.5 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 69.2 kB, which is 40% 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 156.3 kB or 90% of the original size.

Image Optimization

-15%

Potential reduce by 5.3 kB

  • Original 35.7 kB
  • After minification 30.4 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, Explore Data needs image optimization as it can save up to 5.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 341.0 kB

  • Original 489.4 kB
  • After minification 473.7 kB
  • After compression 148.3 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 341.0 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 222.5 kB

  • Original 269.2 kB
  • After minification 255.5 kB
  • After compression 46.7 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. Explore.data.gov needs all CSS files to be minified and compressed as it can save up to 222.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dataset

dataset

32 ms

select2.min.css

select2.min.css

22 ms

main.min.css

main.min.css

57 ms

harvest.css

harvest.css

34 ms

leaflet.css

leaflet.css

33 ms

leaflet.draw.css

leaflet.draw.css

40 ms

datagovtheme.css

datagovtheme.css

34 ms

extlink.css

extlink.css

53 ms

font-awesome.min.css

font-awesome.min.css

50 ms

dap.min.js

dap.min.js

160 ms

jquery.min.js

jquery.min.js

68 ms

select2.min.js

select2.min.js

64 ms

media-grid.js

media-grid.js

64 ms

googleanalytics_event_tracking.js

googleanalytics_event_tracking.js

61 ms

location_autocomplete.js

location_autocomplete.js

67 ms

jquery.cookie.js

jquery.cookie.js

60 ms

datagovtheme.js

datagovtheme.js

63 ms

sorting.js

sorting.js

62 ms

extlink.js

extlink.js

63 ms

css

css

52 ms

ga.js

ga.js

1190 ms

logo.svg

logo.svg

1164 ms

icon-search-27x26.png

icon-search-27x26.png

1200 ms

nav.png

nav.png

1126 ms

alpha.png

alpha.png

1200 ms

number.png

number.png

1124 ms

logo.png

logo.png

1126 ms

analytics.js

analytics.js

1182 ms

number_down.png

number_down.png

85 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

en

en

26 ms

1.png

1.png

52 ms

1.png

1.png

53 ms

select2.png

select2.png

51 ms

pencil.png

pencil.png

53 ms

__utm.gif

__utm.gif

30 ms

collect

collect

54 ms

collect

collect

64 ms

SEO Factors

explore.data.gov SEO score

0

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

Social Sharing Optimization

explore.data.gov

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