Tools & Wizards About Us
comeocare.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

comeocare.com

ComeoCare – Comeo

Page Load Speed

4.2 sec in total

First Response

281 ms

Resources Loaded

3.2 sec

Page Rendered

714 ms

comeocare.com screenshot

About Website

Click here to check amazing Comeo Care content. Otherwise, check out these important facts you probably never knew about comeocare.com

Smart Medication Management

Visit comeocare.com

Key Findings

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

comeocare.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.598

11/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

comeocare.com

281 ms

185 ms

frontend.css

163 ms

style.min.css

247 ms

header-footer-elementor.css

249 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Comeocare.com, 84% (79 requests) were made to Comeo.com and 13% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source Comeo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 372.2 kB (13%)

Content Size

2.9 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Comeocare.com main page is 2.9 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. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 167.4 kB

  • Original 198.8 kB
  • After minification 197.0 kB
  • After compression 31.5 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 167.4 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 197.2 kB

  • Original 2.4 MB
  • After minification 2.2 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. Comeo Care images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.0 kB

  • Original 144.3 kB
  • After minification 144.3 kB
  • After compression 142.3 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

-3%

Potential reduce by 5.6 kB

  • Original 182.3 kB
  • After minification 182.2 kB
  • After compression 176.7 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. Comeocare.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (63%)

Requests Now

75

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

comeocare.com

comeocare.com

281 ms

185 ms

frontend.css

frontend.css

163 ms

style.min.css

style.min.css

247 ms

header-footer-elementor.css

header-footer-elementor.css

249 ms

frontend.min.css

frontend.min.css

256 ms

swiper.min.css

swiper.min.css

317 ms

e-swiper.min.css

e-swiper.min.css

328 ms

post-22.css

post-22.css

330 ms

post-5667.css

post-5667.css

336 ms

be.min.css

be.min.css

517 ms

animations.min.css

animations.min.css

344 ms

fontawesome.min.css

fontawesome.min.css

475 ms

jplayer.blue.monday.min.css

jplayer.blue.monday.min.css

407 ms

responsive.min.css

responsive.min.css

413 ms

css

css

37 ms

css

css

54 ms

masterslider.main.css

masterslider.main.css

421 ms

custom.css

custom.css

429 ms

jquery.min.js

jquery.min.js

416 ms

jquery-migrate.min.js

jquery-migrate.min.js

417 ms

front.js

front.js

426 ms

tw-bs4.css

tw-bs4.css

581 ms

font-awesome.min.css

font-awesome.min.css

578 ms

front.css

front.css

578 ms

list-2.css

list-2.css

578 ms

post-5078.css

post-5078.css

581 ms

widget-heading.min.css

widget-heading.min.css

579 ms

widget-text-editor.min.css

widget-text-editor.min.css

581 ms

widget-image.min.css

widget-image.min.css

646 ms

widget-divider.min.css

widget-divider.min.css

646 ms

elementor.css

elementor.css

647 ms

core.min.js

core.min.js

647 ms

tabs.min.js

tabs.min.js

646 ms

debouncedresize.min.js

debouncedresize.min.js

697 ms

magnificpopup.min.js

magnificpopup.min.js

698 ms

menu.min.js

menu.min.js

702 ms

visible.min.js

visible.min.js

703 ms

animations.min.js

animations.min.js

703 ms

jplayer.min.js

jplayer.min.js

701 ms

enllax.min.js

enllax.min.js

670 ms

translate3d.min.js

translate3d.min.js

615 ms

scripts.min.js

scripts.min.js

709 ms

waypoints.min.js

waypoints.min.js

612 ms

chart.min.js

chart.min.js

553 ms

countdown.min.js

countdown.min.js

543 ms

slick.min.js

slick.min.js

570 ms

frontend.js

frontend.js

585 ms

webpack.runtime.min.js

webpack.runtime.min.js

606 ms

frontend-modules.min.js

frontend-modules.min.js

548 ms

frontend.min.js

frontend.min.js

541 ms

Logo-Comeo-MD.png

Logo-Comeo-MD.png

458 ms

comeocare-white.png

comeocare-white.png

647 ms

ccr-chat.png

ccr-chat.png

435 ms

ccr-magnifier.png

ccr-magnifier.png

443 ms

ccr-arrows.png

ccr-arrows.png

444 ms

ccr-flash.png

ccr-flash.png

445 ms

ccr-hospital.png

ccr-hospital.png

459 ms

circle.png

circle.png

468 ms

piggy-bank.png

piggy-bank.png

469 ms

authenticity.png

authenticity.png

469 ms

healthcare2.jpg

healthcare2.jpg

553 ms

ComeoCare-HD-scaled.jpg

ComeoCare-HD-scaled.jpg

952 ms

ComeoBox-HD.png

ComeoBox-HD.png

730 ms

ccr-automate.png

ccr-automate.png

489 ms

ccr-engage.png

ccr-engage.png

486 ms

ccr-compliance.png

ccr-compliance.png

572 ms

ccr-stress.png

ccr-stress.png

566 ms

ccr-integrate.png

ccr-integrate.png

559 ms

7Aulp_0qnzeSVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qnzeSVz7u3PJLcUMYOFnOkEk30e0.ttf

49 ms

7Aulp_0qnzeSVz7u3PJLcUMYOFn8kEk30e0.ttf

7Aulp_0qnzeSVz7u3PJLcUMYOFn8kEk30e0.ttf

70 ms

7Aulp_0qnzeSVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qnzeSVz7u3PJLcUMYOFmQkEk30e0.ttf

85 ms

7Aulp_0qnzeSVz7u3PJLcUMYOFkQl0k30e0.ttf

7Aulp_0qnzeSVz7u3PJLcUMYOFkQl0k30e0.ttf

88 ms

7Aulp_0qnzeSVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qnzeSVz7u3PJLcUMYOFkpl0k30e0.ttf

88 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

87 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

85 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

84 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

86 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

88 ms

fa-regular-400.woff

fa-regular-400.woff

580 ms

pxiGyp8kv8JHgFVrJJLucHtF.ttf

pxiGyp8kv8JHgFVrJJLucHtF.ttf

88 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

89 ms

fa-solid-900.woff

fa-solid-900.woff

598 ms

icons.woff

icons.woff

689 ms

GothamRoundedMedium_21022.ttf

GothamRoundedMedium_21022.ttf

771 ms

GothamRoundedLight_21020.ttf

GothamRoundedLight_21020.ttf

627 ms

cust3-190x190-1-150x150.png

cust3-190x190-1-150x150.png

675 ms

satreference-190x190-1-150x150.png

satreference-190x190-1-150x150.png

674 ms

ComeoCare-Label.png

ComeoCare-Label.png

746 ms

hands.jpg

hands.jpg

677 ms

contact-white-150x150.png

contact-white-150x150.png

687 ms

x-white.png

x-white.png

700 ms

linkedin-white.png

linkedin-white.png

752 ms

ccr-pattern.png

ccr-pattern.png

741 ms

Accessibility Review

comeocare.com accessibility score

77

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

comeocare.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

SEO Factors

comeocare.com SEO score

93

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

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 Comeocare.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 Comeocare.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

comeocare.com

Open Graph description is not detected on the main page of Comeo Care. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: