Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

solve.care

Advanced Healthcare Platform On Blockchain | Solve.Care

Page Load Speed

7.7 sec in total

First Response

726 ms

Resources Loaded

6.2 sec

Page Rendered

757 ms

solve.care screenshot

About Website

Visit solve.care now to see the best up-to-date Solve content for United States and also check out these interesting facts you probably never knew about solve.care

Global healthcare blockchain platform for care coordination, administration and payments – Solve.Care – redefines cost and convenience of healthcare

Visit solve.care

Key Findings

We analyzed Solve.care page load time and found that the first response time was 726 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

solve.care performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value29.1 s

0/100

25%

SI (Speed Index)

Value36.3 s

0/100

10%

TBT (Total Blocking Time)

Value77,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value94.3 s

0/100

10%

Network Requests Diagram

solve.care

726 ms

lato.woff.css

792 ms

gtm.js

252 ms

wp-emoji-release.min.js

459 ms

style.min.css

351 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 51% of them (67 requests) were addressed to the original Solve.care, 8% (10 requests) were made to Google-analytics.com and 5% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Solve.care.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.9 MB

In fact, the total size of Solve.care main page is 3.4 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. 85% 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. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 170.3 kB

  • Original 337.3 kB
  • After minification 337.1 kB
  • After compression 166.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 170.3 kB or 51% of the original size.

Image Optimization

-10%

Potential reduce by 252.8 kB

  • Original 2.6 MB
  • After minification 2.3 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. Solve images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 22.4 kB

  • Original 134.6 kB
  • After minification 134.4 kB
  • After compression 112.2 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 22.4 kB or 17% of the original size.

CSS Optimization

-14%

Potential reduce by 43.9 kB

  • Original 308.0 kB
  • After minification 308.0 kB
  • After compression 264.1 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. Solve.care needs all CSS files to be minified and compressed as it can save up to 43.9 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (55%)

Requests Now

121

After Optimization

55

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

Accessibility Review

solve.care accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

High

Links do not have a discernible name

Best Practices

solve.care 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

solve.care SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

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 Solve.care 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 Solve.care 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 Solve. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: