Tools & Wizards About Us
caring.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

caring.com

Caring.com: The Leading Free Resource for Senior Living & Care Support

Page Load Speed

4 sec in total

First Response

14 ms

Resources Loaded

1 sec

Page Rendered

2.9 sec

caring.com screenshot

About Website

Welcome to caring.com homepage info - get ready to check Caring best content for United States right away, or after learning these important things about caring.com

The leading online destination for family caregivers seeking information, support, in-home care and senior living options for aging parents, spouses and other loved ones.

Visit caring.com

Key Findings

We analyzed Caring.com page load time and found that the first response time was 14 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.

Performance Metrics

caring.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

48/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value5,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

caring.com

14 ms

www.caring.com

98 ms

48678db3a8ff4c78.css

58 ms

c9ee3f8f75d24b5a.css

59 ms

polyfills-c67a75d1b6f99dc8.js

102 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 96% of them (81 requests) were addressed to the original Caring.com, 2% (2 requests) were made to Prod.dxp.caring.com and 1% (1 request) were made to Polyfill.io. The less responsive or slowest element that took the longest time to load (939 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.7 kB (15%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images

In fact, the total size of Caring.com main page is 4.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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 612.6 kB

  • Original 802.7 kB
  • After minification 802.5 kB
  • After compression 190.1 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 612.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 15.1 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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 images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 49 (60%)

Requests Now

82

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caring. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

caring.com

caring.com

14 ms

www.caring.com

www.caring.com

98 ms

48678db3a8ff4c78.css

48678db3a8ff4c78.css

58 ms

c9ee3f8f75d24b5a.css

c9ee3f8f75d24b5a.css

59 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

102 ms

6562.56ffadb30f75360b.js

6562.56ffadb30f75360b.js

131 ms

4573.02693339a9b25d77.js

4573.02693339a9b25d77.js

97 ms

113.58b647c7dc71a6bf.js

113.58b647c7dc71a6bf.js

129 ms

9408.b7424f6b842001ad.js

9408.b7424f6b842001ad.js

96 ms

9040.1d16c90274409164.js

9040.1d16c90274409164.js

97 ms

8760.3a0a8074d4c71e82.js

8760.3a0a8074d4c71e82.js

129 ms

8976.b06822d68fe63422.js

8976.b06822d68fe63422.js

128 ms

3239.0b80acb1823f1d81.js

3239.0b80acb1823f1d81.js

133 ms

9850.926fda4ea167fe7f.js

9850.926fda4ea167fe7f.js

135 ms

8514.16ce965e69cf77da.js

8514.16ce965e69cf77da.js

134 ms

2779.4645bb6456dc46bd.js

2779.4645bb6456dc46bd.js

131 ms

5361.875cb6d249f2d118.js

5361.875cb6d249f2d118.js

141 ms

8782.1592fbbc1e49867a.js

8782.1592fbbc1e49867a.js

132 ms

6140.db1267fedc66d0aa.js

6140.db1267fedc66d0aa.js

141 ms

3359.ffd7817b65a0359d.js

3359.ffd7817b65a0359d.js

140 ms

369.613860687bfe614b.js

369.613860687bfe614b.js

141 ms

5075.fc8ec6bf6b9075fa.js

5075.fc8ec6bf6b9075fa.js

139 ms

9582.452d4974760afc41.js

9582.452d4974760afc41.js

140 ms

2014.9198b56a16dfbede.js

2014.9198b56a16dfbede.js

151 ms

948.8f44bba7a76a316c.js

948.8f44bba7a76a316c.js

151 ms

3104.a670a1912be0b1c9.js

3104.a670a1912be0b1c9.js

150 ms

1916.27e9cfc7adf5047f.js

1916.27e9cfc7adf5047f.js

152 ms

webpack-051aa49b0451823e.js

webpack-051aa49b0451823e.js

149 ms

framework-e381d50338923e28.js

framework-e381d50338923e28.js

168 ms

main-5d4f129a4673ec5c.js

main-5d4f129a4673ec5c.js

154 ms

_app-b68ae4fa7c4e89eb.js

_app-b68ae4fa7c4e89eb.js

183 ms

98ea7ec2-067cae0fe93582f1.js

98ea7ec2-067cae0fe93582f1.js

153 ms

bd1a647f-a82a155b5e2339a2.js

bd1a647f-a82a155b5e2339a2.js

156 ms

5794-1d308ded05f615a0.js

5794-1d308ded05f615a0.js

152 ms

7168-17892ed79a800a0f.js

7168-17892ed79a800a0f.js

155 ms

3394-bfaed36e6b162825.js

3394-bfaed36e6b162825.js

157 ms

7637-9c0db4387d4241f3.js

7637-9c0db4387d4241f3.js

157 ms

Caring_Emblem_WYellow.svg

Caring_Emblem_WYellow.svg

119 ms

polyfill.min.js

polyfill.min.js

939 ms

9815-13a9a56d32b4684c.js

9815-13a9a56d32b4684c.js

133 ms

8099-1875154d1a3fde2b.js

8099-1875154d1a3fde2b.js

95 ms

TestimonialBG.jpg

TestimonialBG.jpg

77 ms

6088-5c82eb5b7c7f2cc4.js

6088-5c82eb5b7c7f2cc4.js

80 ms

7149-4580c1f2213f1c85.js

7149-4580c1f2213f1c85.js

92 ms

3361-35e786fb81ee3154.js

3361-35e786fb81ee3154.js

111 ms

5108-cc999598137e2d60.js

5108-cc999598137e2d60.js

93 ms

1100-8f0bb2ac0435edbd.js

1100-8f0bb2ac0435edbd.js

86 ms

7710-9bcc6619e932f4c6.js

7710-9bcc6619e932f4c6.js

98 ms

4903-27466a2377988ce9.js

4903-27466a2377988ce9.js

84 ms

968-12db9982c5d5fa31.js

968-12db9982c5d5fa31.js

81 ms

6756-cf74626328a0bd14.js

6756-cf74626328a0bd14.js

81 ms

9220-c201350be1816c43.js

9220-c201350be1816c43.js

82 ms

417-f8d075f346be8043.js

417-f8d075f346be8043.js

84 ms

%5B%5B...catchall%5D%5D-39c73c159eb07094.js

%5B%5B...catchall%5D%5D-39c73c159eb07094.js

84 ms

_buildManifest.js

_buildManifest.js

81 ms

_ssgManifest.js

_ssgManifest.js

81 ms

image

image

81 ms

image

image

97 ms

image

image

82 ms

image

image

90 ms

image

image

80 ms

image

image

80 ms

image

image

80 ms

image

image

75 ms

image

image

75 ms

image

image

75 ms

image

image

74 ms

image

image

73 ms

image

image

78 ms

image

image

76 ms

image

image

73 ms

image

image

80 ms

image

image

75 ms

image

image

74 ms

image

image

54 ms

image

image

56 ms

image

image

56 ms

image

image

57 ms

image

image

38 ms

image

image

115 ms

image

image

34 ms

image

image

111 ms

image

image

112 ms

image

image

112 ms

Accessibility Review

caring.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best Practices

caring.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

caring.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caring.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 Caring.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.

Social Sharing Optimization

caring.com

Open Graph data is detected on the main page of Caring. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: