3.8 sec in total
14 ms
3.4 sec
372 ms
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
Federal Office of Management and Budget lets you access, visualize, and share its budget and financial information on the OpenGov Platform
Visit whitehouse.opengov.comWe 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.
whitehouse.opengov.com performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value21.4 s
0/100
25%
Value12.8 s
2/100
10%
Value3,190 ms
2/100
30%
Value0.115
86/100
15%
Value24.5 s
0/100
10%
14 ms
46 ms
175 ms
58 ms
102 ms
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.
Page size can be reduced by 2.1 MB (71%)
3.0 MB
866.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. 80% 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.
Potential reduce by 593.3 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 593.3 kB or 91% of the original size.
Potential reduce by 3.5 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. Whitehouse Opengov images are well optimized though.
Potential reduce by 1.3 MB
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.
Potential reduce by 192.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. 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.
Number of requests can be reduced by 21 (41%)
51
30
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.
{{url}}
{{time}} ms
whitehouse.opengov.com 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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
whitehouse.opengov.com 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
Page has valid source maps
whitehouse.opengov.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
N/A
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.
{{og_description}}
whitehouse.opengov.com
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: