526 ms in total
63 ms
286 ms
177 ms
Welcome to gao.gov homepage info - get ready to check GAO best content for United States right away, or after learning these important things about gao.gov
GAO provides fact-based, nonpartisan information to Congress. Often called the "congressional watchdog," GAO investigates federal spending and performance.
Visit gao.govWe analyzed Gao.gov page load time and found that the first response time was 63 ms and then it took 463 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
gao.gov performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value7.5 s
4/100
25%
Value7.2 s
30/100
10%
Value2,210 ms
6/100
30%
Value0.136
80/100
15%
Value14.2 s
9/100
10%
63 ms
11 ms
16 ms
19 ms
13 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 93% of them (50 requests) were addressed to the original Gao.gov, 4% (2 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (101 ms) relates to the external source Ajax.googleapis.com.
Page size can be reduced by 313.9 kB (46%)
689.0 kB
375.1 kB
In fact, the total size of Gao.gov main page is 689.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. 40% of websites need less resources to load. Images take 284.9 kB which makes up the majority of the site volume.
Potential reduce by 44.6 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 15.7 kB, which is 29% 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 44.6 kB or 83% of the original size.
Potential reduce by 19.1 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. GAO images are well optimized though.
Potential reduce by 191.2 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 191.2 kB or 69% of the original size.
Potential reduce by 58.9 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. Gao.gov needs all CSS files to be minified and compressed as it can save up to 58.9 kB or 81% of the original size.
Number of requests can be reduced by 22 (42%)
53
31
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GAO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
gao.gov
63 ms
jquery-ui.min.css
11 ms
wrapper.css
16 ms
gao.css
19 ms
nivo-slider.css
13 ms
footer.css
16 ms
jquery.min.js
79 ms
jquery-ui.min.js
101 ms
jquery.nivo.slider.pack.js
14 ms
jquery-bg_scripts.js
30 ms
jquery-cookie.min.js
13 ms
jquery-scrollable.min.js
15 ms
Ajaxer.js
28 ms
check_foresee.js
27 ms
ga.js
71 ms
magnifyer.png
66 ms
government.jpg
66 ms
auditing.jpg
26 ms
homeland_security.jpg
28 ms
space.jpg
28 ms
health.jpg
27 ms
energy.jpg
27 ms
worker_family_assistance.jpg
25 ms
US-GAO-logo.png
25 ms
resources_arrow.png
24 ms
loading.gif
8 ms
slider_bestplacetowork_2015.jpg
31 ms
slider_social_security_oct2015.jpg
29 ms
cae_slider2015.jpg
28 ms
slider_duplication2015apr.jpg
28 ms
slider_2015highrisk.jpg
31 ms
pause.png
26 ms
seal_43px.png
28 ms
footer_sprite.png
31 ms
watchblog_logo_190w.png
29 ms
cae_logo_43px.png
29 ms
hori_large_blue.png
30 ms
collections_fiscal_outlook.png
30 ms
collections_tech_assessment.png
32 ms
collections_duplication.png
33 ms
collections_high_risk.png
32 ms
collections_recovery_act.png
31 ms
press_release.gif
32 ms
2014_PAR_small.png
32 ms
scams.gif
37 ms
committees.gif
37 ms
gaoig.gif
32 ms
fraudnet_badge_cover.jpg
35 ms
footer_seal.png
33 ms
ui-bg_flat_75_ffffff_40x100.png
33 ms
scroll_arrow_down_off.png
32 ms
arrows.png
34 ms
bullets.png
33 ms
__utm.gif
19 ms
gao.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
gao.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
gao.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
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 Gao.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 Gao.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.
gao.gov
Open Graph data is detected on the main page of GAO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: