3.9 sec in total
209 ms
3.3 sec
425 ms
Visit va.gov now to see the best up-to-date VA content for United States and also check out these interesting facts you probably never knew about va.gov
Visit va.govWe analyzed Va.gov page load time and found that the first response time was 209 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
va.gov performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.1 s
24/100
25%
Value9.2 s
13/100
10%
Value2,510 ms
4/100
30%
Value0.305
39/100
15%
Value17.8 s
4/100
10%
209 ms
230 ms
323 ms
405 ms
296 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 26% of them (13 requests) were addressed to the original Va.gov, 34% (17 requests) were made to Prod-va-gov-assets.s3-us-gov-west-1.amazonaws.com and 16% (8 requests) were made to S3-us-gov-west-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source S3-us-gov-west-1.amazonaws.com.
Page size can be reduced by 146.5 kB (10%)
1.5 MB
1.4 MB
In fact, the total size of Va.gov main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 718.0 kB which makes up the majority of the site volume.
Potential reduce by 78.8 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 78.8 kB or 79% of the original size.
Potential reduce by 64.6 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. VA images are well optimized though.
Potential reduce by 257 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 2.8 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. Va.gov has all CSS files already compressed.
Number of requests can be reduced by 28 (70%)
40
12
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
va.gov
209 ms
va.gov
230 ms
www.va.gov
323 ms
polyfills.entry.js
405 ms
web-components.css
296 ms
web-components.entry.js
532 ms
style.css
531 ms
content-build.css
282 ms
static-pages.css
299 ms
vendor.entry.js
577 ms
static-pages.entry.js
788 ms
Universal-Federated-Analytics-Min.js
17 ms
embed.js
365 ms
gtm.js
669 ms
js
661 ms
analytics.js
660 ms
tiny-usa-flag.png
615 ms
icon-dot-gov.svg
1468 ms
icon-https.svg
1592 ms
arrow-right-white.svg
1589 ms
header-logo.png
1594 ms
va-mission-to-better-serve-all.png
1838 ms
veterans-banner-desktop-1.png
1771 ms
sourcesanspro-bold-webfont.woff
593 ms
sourcesanspro-regular-webfont.woff
593 ms
sourcesanspro-light-webfont.woff
595 ms
bitter-bold.ttf
551 ms
bitter-regular.ttf
549 ms
fa-solid-900.woff
553 ms
fa-regular-400.woff
1404 ms
polyfills-dom.entry.js
1336 ms
polyfills-core-js.entry.js
1379 ms
announcements-widget.entry.js
1070 ms
vamc-ehr.json
1057 ms
maintenance-banner-widget.entry.js
1230 ms
vet-center-hours-widget.entry.js
1188 ms
vendors-node_modules_mapbox_mapbox-sdk_index_js-node_modules_mapbox_mapbox-sdk_services_geoco-ff2156.entry.js
1209 ms
facility-detail.entry.js
1184 ms
src_applications_static-pages_homepage_HomepageSearch_jsx.entry.js
1180 ms
VCL-icon-white.svg
983 ms
arrow-down-white.svg
981 ms
vcl-logo.png
979 ms
va-logo-white.png
1161 ms
collect
799 ms
js
408 ms
collect
378 ms
collect
518 ms
collect
286 ms
collect
137 ms
collect
286 ms
va.gov accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
va.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
va.gov SEO score
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 Va.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 Va.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.
va.gov
Open Graph description is not detected on the main page of VA. 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: