Tools & Wizards About Us

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

wellscare.net

IASO Personal Cold Laser Pain Relief Massager | Wellscare

Page Load Speed

2.5 sec in total

First Response

109 ms

Resources Loaded

2.3 sec

Page Rendered

64 ms

About Website

Click here to check amazing Wellscare content. Otherwise, check out these important facts you probably never knew about wellscare.net

Wearable, Compact, Rechargeable. IASO is your FDA-REGISTERED personal massager on the go. Not an ordinary massager. IASO is a lifestyle product that fits your lifestyle and will always be with you whe...

Visit wellscare.net

Key Findings

We analyzed Wellscare.net page load time and found that the first response time was 109 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wellscare.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value8,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

www.wellscare.net

109 ms

minified.js

50 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

273 ms

js

109 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wellscare.net, 55% (42 requests) were made to Static.wixstatic.com and 20% (15 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (49%)

Content Size

2.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wellscare.net main page is 2.3 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. 55% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 227.9 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 1.0 MB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 751.0 kB
  • After minification 717.5 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. Wellscare images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 60.3 kB

  • Original 279.1 kB
  • After minification 279.1 kB
  • After compression 218.8 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 60.3 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

60

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

wellscare.net 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

wellscare.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wellscare.net SEO score

77

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

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

High

Tap targets are not sized appropriately

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 Wellscare.net 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 Wellscare.net 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

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