Analyze

Federal Office of Management and Budget lets you access, visualize, and share its budget and financial information on the OpenGov Platform

Page load speed analysis

  • 55/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    14 ms

  • Resources loaded

    3.4 sec

  • Page rendered

    372 ms

  • Total page load time

    3.8 sec

Welcome to whitehouse.opengov.com homepage info - get ready to check Whitehouse Opengov best content for United States right away, or after learning these important things about whitehouse.opengov.com

We analyzed Whitehouse.opengov.com page load time and found that the first response time was 14 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Page optimization

  • HTML 651.9 kB
    Images 203.0 kB
    Javascripts 1.9 MB
    CSS 228.1 kB

    In fact, the total size of Whitehouse.opengov.com main page is 3.0 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. 85% 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. Javascripts take 1.9 MB which makes up the majority of the site volume.

    • Original 651.9 kB
    • After minification 650.9 kB
    • After compression 58.6 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 593.3 kB or 91% of the original size.

    • Original 203.0 kB
    • After optimization 199.5 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. Whitehouse Opengov images are well optimized though.

    • Original 1.9 MB
    • After minification 1.9 MB
    • After compression 562.6 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 1.3 MB or 70% of the original size.

    • Original 228.1 kB
    • After minification 226.6 kB
    • After compression 35.4 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. Whitehouse.opengov.com needs all CSS files to be minified and compressed as it can save up to 192.7 kB or 84% of the original size.

Network requests diagram

  • whitehouse.opengov.com
  • whitehouse.opengov.com
  • transparency
  • rapp_standalone-0.9d4dcbe554e14556de2c25a1395ae6bb.css
  • rapp_standalone.80b10935dbcb6e41c2f0065204712d2c.js
  • analytics.js
  • heap-3859143578.js
  • all.js
  • widgets.js
  • platform.js
  • jsapi
  • saved_views
  • 56ab34ab-4498-4321-9ef8-e6daa4053d28
  • United_States_of_America.png
  • 2BC1E6_7_0.e70044608398ebfc90c601bfe230d829.woff
  • 2BC1E6_6_0.0d2240abf91638b80ab13886d769fea6.woff
  • 2BC1E6_8_0.a6ff4afe432e351144eeae17289ac9df.woff
  • opengovicons-2.fd7d9ecada0c755268fb75aebc2d901d.woff
  • h
  • collect
  • button.0308b81ff1714e446f674b5b9793f2cd.js
  • xd_arbiter.php
  • ui+en,table+en.css
  • webfontloader,format+en,default+en,ui+en,table+en,corechart+en.I.js
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • fastbutton
  • events
  • tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
  • reports
  • annotations
  • 56ab34ab-4498-4321-9ef8-e6daa4053d28
  • events
  • 1.c8fd30ce9e719304ae8349d9ee3c3ca5.png
  • 2.1b6eaea9f5bc9ec3994015c1967335df.png
  • 3.3cae8c849c3abd877fd343e999263fcf.png
  • 4.5ce4d54675c342ad54d25bf9f80cab68.png
  • 5.eb41f76f142d81d8d344d850f34574e6.png
  • 1.d75100243fcef95e118f7a8c2854a86e.png
  • 2.18507467b91fe9576ce84939afb7e424.png
  • 3.02f77b3db2931c6eac958eea645cc107.png
  • 4.0a45dbb5f943692e8f7ea8f673d95585.png
  • reports.7dfe43adc089f3662f13544a7ab5dcaf.png
  • filters.b304d9a2399c88354ebaf0aa16f27680.png
  • export.dcacf09e8c16d6bb0668c4e1d5b08dae.png
  • legend.e69750be2aa08b39b17361abbb1d3b67.png
  • postmessageRelay
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • jot
  • W5F8_SL0XFawnjxHGsZjJA.ttf
  • collect
  • events
  • h
  • 3193398744-postmessagerelay.js
  • rpc:shindig_random.js
  • cb=gapi.loaded_0

Our browser made a total of 59 requests to load all elements on the main page. We found that 14% of them (8 requests) were addressed to the original Whitehouse.opengov.com, 32% (19 requests) were made to D1h0vg87u5ax2f.cloudfront.net and 14% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Api.keen.io.

Additional info on whitehouse.opengov.com

Requests

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

17

Javascripts

20

Images

2

CSS

12

AJAX

51

All

Possible request optimization

1

Javascripts

15

Images

2

CSS

12

AJAX

21

Optimized

30

All

Normal result

Redirects

As for redirects, our browser reached this domain in two steps. The first redirect led to https://whitehouse.opengov.com/, then it was forwarded to https://whitehouse.opengov.com/transparency, and finally we managed to open this domain. We strongly recommend that the redirects should be reduced, as the more redirects a site has, the slower it loads.

IP address

Whitehouse.opengov.com uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, 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.

Poor result

IP Trace

whitehouse.opengov.com

newhavenct.opengov.com

minneapolismn.opengov.com

pittsburghpa.opengov.com

pinellascountyfl.opengov.com

50.16.225.252

DNS records

Type Host Target/ip TTL Other
A

whitehouse.opengov.com

50.17.235.197 59

Language and encoding

Normal result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

N/A

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitehouse.opengov.com 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 Whitehouse.opengov.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

HTTPS certificate

SSL Certificate

Whitehouse.opengov.com 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 88% of all visits is United States. It’s good for Whitehouse.opengov.com 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

Normal result

Social Sharing Optimization

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

whitehouse.opengov.com

Share this report in social media

Analyze another website

Analyze