3.1 sec in total
113 ms
2.9 sec
72 ms
Welcome to vnastl.com homepage info - get ready to check Vna St L best content right away, or after learning these important things about vnastl.com
For over 100 years, VNA of Greater St. Louis has provided the best hospice care, private duty, palliative care, wellness, and disease preventive care.
Visit vnastl.comWe analyzed Vnastl.com page load time and found that the first response time was 113 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
vnastl.com performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value6.4 s
10/100
25%
Value5.0 s
63/100
10%
Value1,850 ms
9/100
30%
Value0.038
100/100
15%
Value16.4 s
5/100
10%
113 ms
71 ms
70 ms
70 ms
288 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vnastl.com, 57% (46 requests) were made to Static.wixstatic.com and 21% (17 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 1.3 MB (61%)
2.2 MB
856.3 kB
In fact, the total size of Vnastl.com main page is 2.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. 55% of websites need less resources to load. HTML takes 1.6 MB which makes up the majority of the site volume.
Potential reduce by 1.3 MB
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 1.3 MB or 83% of the original size.
Potential reduce by 19.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. Vna St L images are well optimized though.
Potential reduce by 2.7 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.
Number of requests can be reduced by 11 (17%)
63
52
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vna St L. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.vnastl.com
113 ms
minified.js
71 ms
focus-within-polyfill.js
70 ms
polyfill.min.js
70 ms
EmptyState.chunk.min.js
288 ms
thunderbolt-commons.587aa77c.bundle.min.js
449 ms
main.317a27be.bundle.min.js
447 ms
lodash.min.js
447 ms
react.production.min.js
448 ms
react-dom.production.min.js
450 ms
siteTags.bundle.min.js
450 ms
wix-perf-measure.umd.min.js
450 ms
fc653d_c0111b1361034d1a96e0c6fee485e486.png
581 ms
mqdefault.jpg
369 ms
maxresdefault.jpg%202x
326 ms
fc653d_e44ff0568836446697281fa5af54f0ec~mv2.jpg
841 ms
VNA_STL_LOGO-01.jpg
899 ms
fc653d_b9249649db15448e858ae4d9010f2174~mv2.jpg
734 ms
fc653d_1b065ceb5ac4447b8d50f0b81a62522b~mv2.png
685 ms
fc653d_5ee8ba140bbb431a8050ed06ab3d2f47~mv2.png
828 ms
fc653d_772b0a893ce2464d8b9a94c189dfa64e~mv2.png
725 ms
file.jpeg
955 ms
file.jpeg%202x
944 ms
file.jpeg
986 ms
file.jpeg%202x
971 ms
file.jpeg
1093 ms
file.jpeg%202x
902 ms
file.jpeg
1135 ms
file.jpeg%202x
946 ms
file.jpeg
1264 ms
file.jpeg%202x
963 ms
file.jpeg
1287 ms
file.jpeg%202x
977 ms
file.jpeg
1225 ms
file.jpeg%202x
1258 ms
fc653d_e44ff0568836446697281fa5af54f0ec~mv2.jpg
1096 ms
fc653d_e44ff0568836446697281fa5af54f0ec~mv2.jpg
1101 ms
fc653d_229ee8e246a04d33aa24372d4420860c~mv2.jpg
1267 ms
fc653d_229ee8e246a04d33aa24372d4420860c~mv2.jpg
1319 ms
fc653d_ef74693d23114ae1bb017d3f71d17a75~mv2.jpg
1445 ms
fc653d_ef74693d23114ae1bb017d3f71d17a75~mv2.jpg
1428 ms
fc653d_b6578deccf0f4d49901a90a2b0364498~mv2.jpg
1450 ms
fc653d_b6578deccf0f4d49901a90a2b0364498~mv2.jpg
1453 ms
fc653d_bb76e2ad8d164724bdcbe54ba1b1facc~mv2.jpg
1555 ms
fc653d_bb76e2ad8d164724bdcbe54ba1b1facc~mv2.jpg
1554 ms
fc653d_700bfe74d6574685b95c84646c89a6fe~mv2.jpg
1611 ms
fc653d_700bfe74d6574685b95c84646c89a6fe~mv2.jpg
1603 ms
VNA_Wellness_Logo.png
1712 ms
fc653d_544e6212b3d44f7f90200b368ed93895.png
1719 ms
fc653d_7a3053cdbd7047daa0c5eea7dc375a7e~mv2.jpg
1749 ms
bundle.min.js
161 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
81 ms
150 ms
143 ms
143 ms
145 ms
140 ms
138 ms
173 ms
168 ms
172 ms
170 ms
165 ms
165 ms
fc653d_963fb4c80a534de4bfa562be8b5116c0~mv2.jpg
1244 ms
f0b46b_74e729e63b3b4a6a8afb6a93ddeff298~mv2.jpg
1208 ms
fc653d_502523770f5c4b21b478baad08921a6e.png
1127 ms
fc653d_38b1237864344387baaae3ae80368207.png
1257 ms
UW%20logo%20orange.png
1091 ms
fc653d_aafc1aa8ecb740c9a66697b29b73752a.png
1169 ms
AFHS_FNL.png
1100 ms
f0b46b_a41d3466257e4b7381c8584a17a97887~mv2_d_2053_2401_s_2.png
1149 ms
fc653d_14409bbf9f074195900d81481d8bbca5.png
1197 ms
fc653d_b38c93ed136f428eab6090068d8eb287.png
1240 ms
deprecation-en.v5.html
22 ms
bolt-performance
14 ms
deprecation-style.v5.css
5 ms
right-arrow.svg
20 ms
WixMadeforDisplay_W_Bd.woff
4 ms
WixMadeforText_W_Bd.woff
8 ms
WixMadeforText_W_Rg.woff
8 ms
vnastl.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
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
vnastl.com 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
vnastl.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Vnastl.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 Vnastl.com 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.
vnastl.com
Open Graph data is detected on the main page of Vna St L. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: