Tools & Wizards About Us
checkware.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

checkware.com

CheckWare | Software for digital patient involvement | Global

Page Load Speed

2.4 sec in total

First Response

59 ms

Resources Loaded

2.3 sec

Page Rendered

67 ms

checkware.com screenshot

About Website

Click here to check amazing Check Ware content for Norway. Otherwise, check out these important facts you probably never knew about checkware.com

CheckWare offers solutions with high professional expertise and quality for digital assessments, remote patient monitoring and online treatment programs

Visit checkware.com

Key Findings

We analyzed Checkware.com page load time and found that the first response time was 59 ms and then it took 2.3 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

checkware.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

www.checkware.com

59 ms

minified.js

67 ms

focus-within-polyfill.js

127 ms

polyfill.min.js

933 ms

thunderbolt-commons.b790d5df.bundle.min.js

115 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Checkware.com, 38% (20 requests) were made to Static.wixstatic.com and 34% (18 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (976 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 535.2 kB (44%)

Content Size

1.2 MB

After Optimization

673.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Checkware.com main page is 1.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. 40% of websites need less resources to load. HTML takes 662.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 529.5 kB

  • Original 662.2 kB
  • After minification 660.5 kB
  • After compression 132.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 529.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 293.3 kB
  • After minification 291.2 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. Check Ware images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 253.3 kB
  • After minification 253.3 kB
  • After compression 249.6 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.

Requests Breakdown

Number of requests can be reduced by 11 (24%)

Requests Now

45

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.checkware.com

www.checkware.com

59 ms

minified.js

minified.js

67 ms

focus-within-polyfill.js

focus-within-polyfill.js

127 ms

polyfill.min.js

polyfill.min.js

933 ms

thunderbolt-commons.b790d5df.bundle.min.js

thunderbolt-commons.b790d5df.bundle.min.js

115 ms

main.c07e8381.bundle.min.js

main.c07e8381.bundle.min.js

115 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

114 ms

lodash.min.js

lodash.min.js

115 ms

react.production.min.js

react.production.min.js

116 ms

react-dom.production.min.js

react-dom.production.min.js

119 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

118 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

116 ms

561f1e_446c85640afc4eaeb4d16cb864291a67~mv2.png

561f1e_446c85640afc4eaeb4d16cb864291a67~mv2.png

132 ms

561f1e_77ec9bc9d7b54ed3bb4b3e3abda6ff66~mv2.jpg

561f1e_77ec9bc9d7b54ed3bb4b3e3abda6ff66~mv2.jpg

232 ms

561f1e_07beb0849c754818b84a464d0c92560e~mv2.webp

561f1e_07beb0849c754818b84a464d0c92560e~mv2.webp

385 ms

561f1e_07beb0849c754818b84a464d0c92560e~mv2.webp

561f1e_07beb0849c754818b84a464d0c92560e~mv2.webp

486 ms

561f1e_ba20ffc25fd2442e8b3982d44ec70d8a~mv2.webp

561f1e_ba20ffc25fd2442e8b3982d44ec70d8a~mv2.webp

484 ms

561f1e_ba20ffc25fd2442e8b3982d44ec70d8a~mv2.webp

561f1e_ba20ffc25fd2442e8b3982d44ec70d8a~mv2.webp

533 ms

7af972_585fc07f48b04222a51b52fe7a9e1e04~mv2.webp

7af972_585fc07f48b04222a51b52fe7a9e1e04~mv2.webp

506 ms

7af972_585fc07f48b04222a51b52fe7a9e1e04~mv2.webp

7af972_585fc07f48b04222a51b52fe7a9e1e04~mv2.webp

496 ms

7af972_bba80c43538443b1ad77cf486dc1a6e3~mv2.webp

7af972_bba80c43538443b1ad77cf486dc1a6e3~mv2.webp

590 ms

7af972_ce91ffc6d05f473788c24b2950ec489e~mv2.webp

7af972_ce91ffc6d05f473788c24b2950ec489e~mv2.webp

659 ms

7af972_ce91ffc6d05f473788c24b2950ec489e~mv2.webp

7af972_ce91ffc6d05f473788c24b2950ec489e~mv2.webp

713 ms

7af972_e0eb435a5a7c4b319899bd69423ed4f2~mv2.webp

7af972_e0eb435a5a7c4b319899bd69423ed4f2~mv2.webp

701 ms

7af972_e0eb435a5a7c4b319899bd69423ed4f2~mv2.webp

7af972_e0eb435a5a7c4b319899bd69423ed4f2~mv2.webp

716 ms

7af972_94a50a3f00b3491c9ed59e6f85b744b1~mv2.webp

7af972_94a50a3f00b3491c9ed59e6f85b744b1~mv2.webp

711 ms

7af972_94a50a3f00b3491c9ed59e6f85b744b1~mv2.webp

7af972_94a50a3f00b3491c9ed59e6f85b744b1~mv2.webp

778 ms

7af972_e5ecde38191949f3adc12e88fd0c4a91~mv2.webp

7af972_e5ecde38191949f3adc12e88fd0c4a91~mv2.webp

976 ms

7af972_e5ecde38191949f3adc12e88fd0c4a91~mv2.webp

7af972_e5ecde38191949f3adc12e88fd0c4a91~mv2.webp

973 ms

c9027e_13fee9b482ef4846bd0a6cb16de302f3~mv2.webp

c9027e_13fee9b482ef4846bd0a6cb16de302f3~mv2.webp

971 ms

bundle.min.js

bundle.min.js

170 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

14 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

33 ms

file.woff

file.woff

489 ms

file.woff

file.woff

511 ms

126 ms

127 ms

123 ms

125 ms

123 ms

119 ms

149 ms

153 ms

149 ms

149 ms

145 ms

deprecation-en.v5.html

deprecation-en.v5.html

27 ms

bolt-performance

bolt-performance

25 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

17 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

6 ms

Accessibility Review

checkware.com accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

checkware.com 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

checkware.com SEO score

91

Search Engine Optimization Advices

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 doesn't use 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 Checkware.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 Checkware.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

checkware.com

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