3.3 sec in total
244 ms
2.5 sec
523 ms
Visit caringcomm.org now to see the best up-to-date Caring Comm content and also check out these interesting facts you probably never knew about caringcomm.org
Caring Communities is the leading Member-owned liability insurance company to exclusively serve not-for-profit senior housing and care organizations
Visit caringcomm.orgWe analyzed Caringcomm.org page load time and found that the first response time was 244 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
caringcomm.org performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value22.7 s
0/100
25%
Value13.8 s
1/100
10%
Value5,270 ms
0/100
30%
Value0
100/100
15%
Value24.2 s
0/100
10%
244 ms
77 ms
117 ms
122 ms
158 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 66% of them (61 requests) were addressed to the original Caringcomm.org, 15% (14 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain Caringcomm.org.
Page size can be reduced by 456.7 kB (27%)
1.7 MB
1.3 MB
In fact, the total size of Caringcomm.org main page is 1.7 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. Only a small number of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 232.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 232.7 kB or 88% of the original size.
Potential reduce by 1.3 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. Caring Comm images are well optimized though.
Potential reduce by 187.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 187.3 kB or 16% of the original size.
Potential reduce by 35.4 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. Caringcomm.org needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 15% of the original size.
Number of requests can be reduced by 72 (94%)
77
5
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caring Comm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
caringcomm.org
244 ms
styles.css
77 ms
frontend.min.css
117 ms
grid-system.css
122 ms
style.css
158 ms
header-secondary-nav.css
121 ms
element-highlighted-text.css
124 ms
element-post-grid.css
125 ms
element-cascading-images.css
169 ms
cf7.css
174 ms
css
54 ms
responsive.css
170 ms
skin-material.css
173 ms
menu-dynamic.css
177 ms
js_composer.min.css
216 ms
salient-dynamic-styles.css
210 ms
style.css
196 ms
css
51 ms
jquery.min.js
246 ms
jquery-migrate.min.js
224 ms
css
47 ms
css
49 ms
eventon_styles.css
281 ms
all.css
333 ms
style-non-critical.css
245 ms
jquery.fancybox.css
245 ms
core.css
304 ms
slide-out-right-material.css
305 ms
slide-out-right-hover.css
305 ms
hooks.min.js
306 ms
i18n.min.js
341 ms
index.js
342 ms
index.js
342 ms
imagesloaded.min.js
341 ms
masonry.min.js
341 ms
jquery.masonry.min.js
342 ms
maps.js
651 ms
js
97 ms
wpgmp_frontend.min.js
632 ms
jquery.easing.min.js
362 ms
jquery.mousewheel.min.js
362 ms
api.js
45 ms
js
92 ms
external_api.js
76 ms
priority.js
360 ms
transit.min.js
324 ms
waypoints.js
575 ms
imagesLoaded.min.js
571 ms
hoverintent.min.js
569 ms
jquery.fancybox.js
569 ms
anime.min.js
650 ms
superfish.js
608 ms
init.js
779 ms
touchswipe.min.js
605 ms
wp-polyfill.min.js
601 ms
index.js
601 ms
js_composer_front.min.js
780 ms
eventon_gen_maps.js
762 ms
eventon_functions.js
739 ms
jquery.easing.1.3.js
855 ms
handlebars.js
905 ms
gtm.js
115 ms
CkctYzsOqeY
420 ms
jquery.mobile.min.js
798 ms
moment.min.js
796 ms
moment_timezone_min.js
795 ms
jquery.mousewheel.min.js
736 ms
eventon_script.js
737 ms
akismet-frontend.js
737 ms
logo-home.png
737 ms
92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI0.ttf
56 ms
92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI0.ttf
327 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IjVBNI0.ttf
352 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIjVBNI0.ttf
353 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
353 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
354 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
353 ms
icomoon.woff
736 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6Vc.ttf
35 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6Vc.ttf
34 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
36 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
34 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
35 ms
www-player.css
68 ms
www-embed-player.js
89 ms
base.js
116 ms
ad_status.js
239 ms
recaptcha__en.js
331 ms
V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js
132 ms
embed.js
89 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
31 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
31 ms
id
124 ms
caringcomm.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
caringcomm.org 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
Browser errors were logged to the console
Page has valid source maps
caringcomm.org 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 Caringcomm.org 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 Caringcomm.org 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.
caringcomm.org
Open Graph data is detected on the main page of Caring Comm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: