2.4 sec in total
236 ms
1.7 sec
474 ms
Welcome to villageatprimacyplace.com homepage info - get ready to check Village At Primacy Place best content for United States right away, or after learning these important things about villageatprimacyplace.com
Welcome to The Village at Primacy Place. Our programs promote independence with our Assisted Living and Short-Term Stays. Come in for a tour!
Visit villageatprimacyplace.comWe analyzed Villageatprimacyplace.com page load time and found that the first response time was 236 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
villageatprimacyplace.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value10.1 s
0/100
25%
Value12.6 s
3/100
10%
Value2,910 ms
3/100
30%
Value1.041
2/100
15%
Value21.2 s
1/100
10%
236 ms
171 ms
32 ms
26 ms
223 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 64% of them (83 requests) were addressed to the original Villageatprimacyplace.com, 14% (18 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Villageatprimacyplace.com.
Page size can be reduced by 129.5 kB (6%)
2.2 MB
2.0 MB
In fact, the total size of Villageatprimacyplace.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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 102.7 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 102.7 kB or 79% of the original size.
Potential reduce by 0 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 At Primacy Place images are well optimized though.
Potential reduce by 18.4 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 8.3 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. Villageatprimacyplace.com has all CSS files already compressed.
Number of requests can be reduced by 89 (87%)
102
13
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Village At Primacy Place. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.villageatprimacyplace.com
236 ms
style-blocks.build.css
171 ms
extra.min.css
32 ms
df-style.css
26 ms
events-manager.min.css
223 ms
front.min.css
26 ms
dashicons.min.css
190 ms
lsl7bwp.css
118 ms
style.min.css
36 ms
style.min.css
34 ms
style.min.css
41 ms
css
39 ms
formreset.min.css
49 ms
formsmain.min.css
51 ms
readyclass.min.css
55 ms
browsers.min.css
94 ms
style-static.min.css
67 ms
style.css
94 ms
jquery.min.js
98 ms
jquery-migrate.min.js
96 ms
core.min.js
95 ms
mouse.min.js
98 ms
sortable.min.js
97 ms
datepicker.min.js
110 ms
resizable.min.js
109 ms
draggable.min.js
109 ms
controlgroup.min.js
126 ms
checkboxradio.min.js
125 ms
button.min.js
124 ms
dialog.min.js
147 ms
events-manager.min.js
138 ms
preloader-script.js
145 ms
ie-compat.min.js
149 ms
ds-script.js
155 ms
jquery.json.min.js
157 ms
gravityforms.min.js
161 ms
conditional_logic.min.js
167 ms
master-csl.css
62 ms
api.js
45 ms
et-core-unified-tb-7-tb-8-tb-12-12424.min.css
168 ms
et-core-unified-12424.min.css
154 ms
et-core-unified-tb-7-tb-8-tb-12-deferred-12424.min.css
337 ms
mediaelementplayer-legacy.min.css
332 ms
wp-mediaelement.min.css
152 ms
utils.min.js
156 ms
df-script.js
164 ms
dismiss.js
421 ms
front.min.js
154 ms
userway.js
162 ms
scripts.min.js
163 ms
jquery.fitvids.js
371 ms
comment-reply.min.js
178 ms
jquery.mobile.js
369 ms
magnific-popup.js
368 ms
easypiechart.js
519 ms
salvattore.js
515 ms
frontend-bundle.min.js
515 ms
frontend-bundle.min.js
514 ms
frontend-bundle.min.js
559 ms
wp-polyfill-inert.min.js
503 ms
regenerator-runtime.min.js
689 ms
p.css
22 ms
wp-polyfill.min.js
543 ms
dom-ready.min.js
542 ms
hooks.min.js
545 ms
i18n.min.js
529 ms
a11y.min.js
559 ms
jquery.maskedinput.min.js
734 ms
placeholders.jquery.min.js
555 ms
vendor-theme.min.js
548 ms
scripts-theme.min.js
546 ms
frontend.min.js
579 ms
common.js
575 ms
smush-lazy-load.min.js
625 ms
mediaelement-and-player.min.js
569 ms
mediaelement-migrate.min.js
705 ms
wp-mediaelement.min.js
818 ms
akismet-frontend.js
694 ms
motion-effects.js
710 ms
sticky-elements.js
827 ms
gtm.js
48 ms
js
117 ms
analytics.js
242 ms
events.js
113 ms
loader.js
257 ms
9261781398.js
729 ms
a6e5f0e9-450d-4e37-952f-8b4759d8956b
443 ms
preloader.gif
517 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
287 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
316 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
322 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
321 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
319 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
320 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
320 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
343 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
343 ms
d
214 ms
d
273 ms
wARDj0u
20 ms
modules.woff
736 ms
playing-cards.jpg
718 ms
ALimage6.jpg
719 ms
iStock-546025824.jpg
764 ms
iStock-510851232.jpg
862 ms
ship.gif
724 ms
events.js
257 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXZ0ow.ttf
277 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXZ0ow.ttf
276 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXZ0ow.ttf
276 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXZ0ow.ttf
328 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXZ0ow.ttf
398 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXZ0ow.ttf
398 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXZ0ow.ttf
399 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXZ0ow.ttf
399 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXZ0ow.ttf
397 ms
widget.js
393 ms
collect
96 ms
call-tracking_7.js
42 ms
recaptcha__en.js
68 ms
collect
175 ms
sa.css
64 ms
saq_pxl
73 ms
a6e5f0e9-450d-4e37-952f-8b4759d8956b
135 ms
logo.png
374 ms
ga-audiences
16 ms
wcm
19 ms
wcm
12 ms
navigator-launcher-bundle-1701330928.js
20 ms
widget_app_base_1705584376091.js
62 ms
villageatprimacyplace.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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
villageatprimacyplace.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
villageatprimacyplace.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
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 Villageatprimacyplace.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 Villageatprimacyplace.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.
villageatprimacyplace.com
Open Graph data is detected on the main page of Village At Primacy Place. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: