4.2 sec in total
155 ms
2.8 sec
1.2 sec
Click here to check amazing Village Parkway content. Otherwise, check out these important facts you probably never knew about villageparkway.com
Welcome to Village on the Parkway! We have a great community for students looking to live off-campus. We are close to UVU campus. Schedule a tour today!
Visit villageparkway.comWe analyzed Villageparkway.com page load time and found that the first response time was 155 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
villageparkway.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value11.3 s
0/100
25%
Value9.1 s
14/100
10%
Value1,430 ms
15/100
30%
Value0.259
48/100
15%
Value13.7 s
10/100
10%
155 ms
630 ms
111 ms
785 ms
201 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Villageparkway.com, 59% (60 requests) were made to 27ne77.p3cdn1.secureserver.net and 12% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 27ne77.p3cdn1.secureserver.net.
Page size can be reduced by 134.6 kB (6%)
2.2 MB
2.1 MB
In fact, the total size of Villageparkway.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. 75% 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. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 117.5 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 117.5 kB or 82% of the original size.
Potential reduce by 589 B
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. Village Parkway images are well optimized though.
Potential reduce by 12.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.
Potential reduce by 3.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. Villageparkway.com has all CSS files already compressed.
Number of requests can be reduced by 62 (74%)
84
22
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Village Parkway. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
villageparkway.com
155 ms
villageparkway.com
630 ms
js
111 ms
style.min.css
785 ms
page-notifications-public.css
201 ms
all.css
278 ms
redcore.css
197 ms
dashicons.min.css
718 ms
nectar-slider.css
203 ms
font-awesome-legacy.min.css
197 ms
grid-system.css
297 ms
style.css
322 ms
header-layout-centered-menu.css
356 ms
header-secondary-nav.css
337 ms
element-fancy-box.css
406 ms
element-scrolling-text.css
395 ms
element-highlighted-text.css
417 ms
asset-reveal-animation.css
454 ms
element-button-legacy.css
510 ms
wpforms.css
498 ms
css
82 ms
responsive.css
516 ms
flickity.css
554 ms
skin-material.css
601 ms
menu-dynamic.css
606 ms
widget-nectar-posts.css
741 ms
js_composer.min.css
676 ms
salient-dynamic-styles.css
726 ms
style.css
735 ms
css
89 ms
frontend-gtag.min.js
790 ms
jquery.min.js
837 ms
jquery-migrate.min.js
813 ms
page-notifications-public.js
852 ms
rentgrata.js
93 ms
style-non-critical.css
870 ms
jquery.fancybox.css
984 ms
core.css
983 ms
slide-out-right-hover.css
986 ms
anime.min.js
987 ms
nectar-slider.js
989 ms
jquery.easing.min.js
987 ms
jquery.mousewheel.min.js
1072 ms
js
77 ms
priority.js
1020 ms
nectar-slider-priority.js
886 ms
transit.min.js
1019 ms
waypoints.js
1014 ms
analytics.js
26 ms
imagesLoaded.min.js
920 ms
collect
27 ms
hoverintent.min.js
1296 ms
jquery.fancybox.js
984 ms
collect
11 ms
flickity.js
965 ms
ga-audiences
27 ms
superfish.js
923 ms
init.js
941 ms
touchswipe.min.js
902 ms
redcore.js
984 ms
js_composer_front.min.js
920 ms
css2
13 ms
css2
20 ms
css
30 ms
css2
19 ms
linkid.js
45 ms
gtm.js
129 ms
fbevents.js
128 ms
164319210Equal-Housing-Opportunity-Accessibility-Logo-1.png
122 ms
Village-on-the-Parkway-Logoe.png
575 ms
Village-on-the-Parkway-Logo-White-01.png
541 ms
539400_479739302058775_859999451_n.jpg
583 ms
1771274916VOTP-Map-01.png
916 ms
VP-copy-1.jpg
674 ms
VPfff-1.jpg
1137 ms
vp-bg3.jpg
889 ms
VP1.jpg
684 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf
216 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyccg.ttf
317 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmj.ttf
345 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyccg.ttf
345 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmj.ttf
347 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyccg.ttf
346 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSyccg.ttf
347 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2ccg.ttf
347 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyuccg.ttf
348 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuccg.ttf
349 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSuccg.ttf
349 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICuccg.ttf
349 ms
Bender-Solid.otf
212 ms
Bender-Inline.otf
314 ms
icomoon.woff
794 ms
fontawesome-webfont.svg
794 ms
collect
309 ms
collect
78 ms
126 ms
collect
90 ms
collect
65 ms
ga-audiences
15 ms
21 ms
ga-audiences
20 ms
fontawesome-webfont.woff
108 ms
villageparkway.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
villageparkway.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
villageparkway.com 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 Villageparkway.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 Villageparkway.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.
villageparkway.com
Open Graph data is detected on the main page of Village Parkway. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: