1.5 sec in total
92 ms
1.2 sec
154 ms
Click here to check amazing Vvsd content for United States. Otherwise, check out these important facts you probably never knew about vvsd.net
Veterans Village of San Diego (VVSD) has served all veterans since 1981 and is dedicated to “Leave No One Behind.” For forty years, VVSD has sought to provide services and support to our nation’s hero...
Visit vvsd.netWe analyzed Vvsd.net page load time and found that the first response time was 92 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
vvsd.net performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value16.0 s
0/100
25%
Value8.7 s
16/100
10%
Value3,310 ms
2/100
30%
Value0
100/100
15%
Value19.4 s
2/100
10%
92 ms
204 ms
90 ms
181 ms
109 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Vvsd.net, 70% (76 requests) were made to Vvsd.wpenginepowered.com and 14% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (458 ms) relates to the external source Vvsd.wpenginepowered.com.
Page size can be reduced by 310.0 kB (27%)
1.2 MB
858.4 kB
In fact, the total size of Vvsd.net main page is 1.2 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 560.9 kB which makes up the majority of the site volume.
Potential reduce by 278.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 278.8 kB or 89% of the original size.
Potential reduce by 2.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. Vvsd images are well optimized though.
Potential reduce by 8.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. This website has mostly compressed JavaScripts.
Potential reduce by 20.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. Vvsd.net needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 11% of the original size.
Number of requests can be reduced by 81 (90%)
90
9
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vvsd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
vvsd.net
92 ms
vvsd.net
204 ms
js
90 ms
js
181 ms
style.min.css
109 ms
style.css
78 ms
styles.css
70 ms
ctf-styles.min.css
117 ms
style.min.css
78 ms
frontend.min.css
72 ms
flatpickr.min.css
110 ms
select2.min.css
111 ms
font-awesome.min.css
114 ms
style.css
111 ms
style.css
141 ms
theme.css
158 ms
blog-layouts-module.css
140 ms
css
65 ms
custom-jet-blocks.css
114 ms
jet-elements.css
147 ms
jet-elements-skin.css
135 ms
elementor-icons.min.css
159 ms
frontend-legacy.min.css
162 ms
frontend.min.css
163 ms
swiper.min.css
128 ms
jet-blog.css
219 ms
jet-tabs-frontend.css
135 ms
jet-tricks-frontend.css
162 ms
fluent-forms-elementor-widget.css
222 ms
nucleo-outline.css
223 ms
general.min.css
212 ms
css
38 ms
fontawesome.min.css
214 ms
brands.min.css
227 ms
solid.min.css
230 ms
frontend-gtag.min.js
316 ms
frontend-gtag.min.js
240 ms
jquery.min.js
239 ms
jquery-migrate.min.js
240 ms
flatpickr.min.js
238 ms
select2.min.js
242 ms
api.js
41 ms
api.js
96 ms
animations.min.css
214 ms
ctct-plugin-recaptcha-v2.min.js
209 ms
ctct-plugin-frontend.min.js
278 ms
index.js
278 ms
index.js
281 ms
frontend.min.js
244 ms
theme-script.js
276 ms
general.min.js
275 ms
twitter-widgets.js
271 ms
js
136 ms
analytics.js
132 ms
js
131 ms
wp-polyfill-inert.min.js
254 ms
regenerator-runtime.min.js
252 ms
wp-polyfill.min.js
243 ms
index.js
234 ms
hoverIntent.min.js
229 ms
webpack.runtime.min.js
229 ms
frontend-modules.min.js
229 ms
waypoints.min.js
227 ms
core.min.js
222 ms
swiper.min.js
223 ms
share-link.min.js
221 ms
dialog.min.js
194 ms
frontend.min.js
148 ms
jet-blocks.min.js
141 ms
jet-elements.min.js
141 ms
jet-tabs-frontend.min.js
137 ms
popperjs.js
134 ms
tippy-bundle.js
133 ms
jet-tricks-frontend.js
132 ms
preloaded-modules.min.js
122 ms
underscore-before.js
122 ms
underscore.min.js
190 ms
underscore-after.js
189 ms
wp-util.min.js
188 ms
frontend.min.js
189 ms
jet-blog.min.js
189 ms
collect
123 ms
ctf-sprite.png
296 ms
VVSD-Full-White-Text_transparent.png
86 ms
thumbnail_VVSD-SEAL-Blue-Text-230x230.png
85 ms
VVSD-Full-White-Text_transparent-300x81.png
88 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
94 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
94 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
93 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
105 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
93 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
93 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
124 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
126 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
125 ms
fa-solid-900.woff
458 ms
fa-brands-400.woff
431 ms
widget.js
152 ms
recaptcha__en.js
113 ms
widgets.js
160 ms
widget_app_base_1716562046528.js
17 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
51 ms
settings
100 ms
vvsd.net 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
button, link, and menuitem elements do not have accessible names.
vvsd.net 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
vvsd.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vvsd.net 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 Vvsd.net 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.
vvsd.net
Open Graph data is detected on the main page of Vvsd. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: