Tools & Wizards About Us
weecare.co screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weecare.co

Daycare, Preschool, Nanny, & Babysitter Childcare You'll Love | Upwards

Page Load Speed

2.2 sec in total

First Response

143 ms

Resources Loaded

1.3 sec

Page Rendered

769 ms

weecare.co screenshot

About Website

Click here to check amazing Weecare content for United States. Otherwise, check out these important facts you probably never knew about weecare.co

Every day, Upwards matches thousands of families with daycares, nannies, babysitters, preschools, and caregivers that provide safe, affordable, high-quality child care.

Visit weecare.co

Key Findings

We analyzed Weecare.co page load time and found that the first response time was 143 ms and then it took 2.1 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.

Performance Metrics

weecare.co performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.154

75/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

weecare.co

143 ms

upwards.com

358 ms

js

50 ms

analytics.min.js

343 ms

placeholder-transparent.svg

316 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Weecare.co, 76% (19 requests) were made to Static.upwards.com and 8% (2 requests) were made to Upwards.com. The less responsive or slowest element that took the longest time to load (786 ms) relates to the external source Static.upwards.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.6 kB (23%)

Content Size

829.4 kB

After Optimization

642.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weecare.co main page is 829.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 560.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 135.1 kB

  • Original 152.4 kB
  • After minification 115.2 kB
  • After compression 17.2 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. This page needs HTML code to be minified as it can gain 37.1 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 135.1 kB or 89% of the original size.

Image Optimization

-9%

Potential reduce by 51.2 kB

  • Original 560.9 kB
  • After minification 509.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. Weecare images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 47 B

  • Original 105.2 kB
  • After minification 105.2 kB
  • After compression 105.1 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.

CSS Optimization

-2%

Potential reduce by 206 B

  • Original 11.0 kB
  • After minification 11.0 kB
  • After compression 10.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. Weecare.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (28%)

Requests Now

18

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weecare.co

weecare.co

143 ms

upwards.com

upwards.com

358 ms

js

js

50 ms

analytics.min.js

analytics.min.js

343 ms

placeholder-transparent.svg

placeholder-transparent.svg

316 ms

base.11156.css

base.11156.css

301 ms

services.11156.css

services.11156.css

303 ms

home.11156.css

home.11156.css

304 ms

jquery.min.js

jquery.min.js

22 ms

config.11156.js

config.11156.js

80 ms

common.11156.js

common.11156.js

414 ms

home.11156.js

home.11156.js

346 ms

close-dark.svg

close-dark.svg

342 ms

upwards-wordmark-black.svg

upwards-wordmark-black.svg

394 ms

background-radial-teal.svg

background-radial-teal.svg

342 ms

graphic-orange-star.svg

graphic-orange-star.svg

344 ms

graphic-carnation-heart.svg

graphic-carnation-heart.svg

379 ms

hero-family.png

hero-family.png

786 ms

hero-arc-bottom.png

hero-arc-bottom.png

406 ms

placeholder.svg

placeholder.svg

408 ms

webfont.woff

webfont.woff

571 ms

webfont.woff

webfont.woff

197 ms

webfont.woff

webfont.woff

274 ms

webfont.woff

webfont.woff

149 ms

webfont.woff

webfont.woff

158 ms

Accessibility Review

weecare.co accessibility score

96

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

Best Practices

weecare.co best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

weecare.co 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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Weecare.co 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 Weecare.co 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

weecare.co

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