Tools & Wizards About Us
mycancertracker.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mycancertracker.com

My Cancer Tracker - Personal Health Tracker for Cancer Patients

Page Load Speed

12.3 sec in total

First Response

271 ms

Resources Loaded

11.2 sec

Page Rendered

839 ms

mycancertracker.com screenshot

About Website

Click here to check amazing My Cancer Tracker content. Otherwise, check out these important facts you probably never knew about mycancertracker.com

My Cancer Tracker is the fastest and easiest to use cancer diary app available on the AppStore & Google Play Store. With amazing simple steps, you can record information about your diagnosis, keep tab...

Visit mycancertracker.com

Key Findings

We analyzed Mycancertracker.com page load time and found that the first response time was 271 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

mycancertracker.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value75.5 s

0/100

25%

SI (Speed Index)

Value33.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value41.9 s

0/100

10%

Network Requests Diagram

mycancertracker.com

271 ms

bootstrap.css

77 ms

font-awesome.min.css

140 ms

simple-line-icons.css

130 ms

main.css

143 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 82% of them (55 requests) were addressed to the original Mycancertracker.com, 9% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.7 sec) belongs to the original domain Mycancertracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 MB (19%)

Content Size

22.6 MB

After Optimization

18.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mycancertracker.com main page is 22.6 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. 70% of websites need less resources to load. Images take 22.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.2 kB

  • Original 38.6 kB
  • After minification 34.7 kB
  • After compression 9.4 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 29.2 kB or 76% of the original size.

Image Optimization

-19%

Potential reduce by 4.3 MB

  • Original 22.4 MB
  • After minification 18.1 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. Obviously, My Cancer Tracker needs image optimization as it can save up to 4.3 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 15.4 kB

  • Original 114.0 kB
  • After minification 114.0 kB
  • After compression 98.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 15.4 kB or 13% of the original size.

CSS Optimization

-10%

Potential reduce by 4.7 kB

  • Original 45.6 kB
  • After minification 45.6 kB
  • After compression 40.9 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. Mycancertracker.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (36%)

Requests Now

59

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mycancertracker.com

mycancertracker.com

271 ms

bootstrap.css

bootstrap.css

77 ms

font-awesome.min.css

font-awesome.min.css

140 ms

simple-line-icons.css

simple-line-icons.css

130 ms

main.css

main.css

143 ms

custom.css

custom.css

141 ms

css

css

41 ms

css

css

58 ms

js

js

224 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

349 ms

bootstrap.min.js

bootstrap.min.js

345 ms

jquery.easing.min.js

jquery.easing.min.js

413 ms

jquery.fitvids.js

jquery.fitvids.js

414 ms

jquery.bxslider.js

jquery.bxslider.js

407 ms

slick.js

slick.js

405 ms

jquery.scrollTo-1.4.3.1-min.js

jquery.scrollTo-1.4.3.1-min.js

430 ms

jquery.localscroll-1.2.7-min.js

jquery.localscroll-1.2.7-min.js

429 ms

wow.min.js

wow.min.js

431 ms

jquery.cycle.all.js

jquery.cycle.all.js

432 ms

jquery.maximage.min.js

jquery.maximage.min.js

433 ms

zi-script.js

zi-script.js

432 ms

contact-us.js

contact-us.js

431 ms

loader.gif

loader.gif

258 ms

full-slide.jpg

full-slide.jpg

1418 ms

btn-appstore.png

btn-appstore.png

261 ms

btn-googleplay.png

btn-googleplay.png

262 ms

samsung-iphone-image-1.png

samsung-iphone-image-1.png

620 ms

full-slide2.png

full-slide2.png

10720 ms

full-slide5.png

full-slide5.png

4524 ms

features_one.png

features_one.png

666 ms

features_two.png

features_two.png

618 ms

features_three.png

features_three.png

818 ms

features_four.png

features_four.png

818 ms

app-scr1.png

app-scr1.png

823 ms

app-scr2.png

app-scr2.png

973 ms

app-scr3.png

app-scr3.png

1386 ms

app-scr4.png

app-scr4.png

1138 ms

app-scr5.png

app-scr5.png

1075 ms

app-scr6.png

app-scr6.png

1180 ms

app-scr7.png

app-scr7.png

1295 ms

app-scr8.png

app-scr8.png

1438 ms

app-scr9.png

app-scr9.png

1456 ms

app-scr10.png

app-scr10.png

1642 ms

app-scr11.png

app-scr11.png

1668 ms

app-scr12.png

app-scr12.png

2006 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

200 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

201 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

201 ms

app-scr13.png

app-scr13.png

1589 ms

app-scr14.png

app-scr14.png

1634 ms

app-scr15.png

app-scr15.png

1660 ms

app-scr16.png

app-scr16.png

1761 ms

app-scr17.png

app-scr17.png

1841 ms

app-scr18.png

app-scr18.png

2120 ms

app-scr19.png

app-scr19.png

1996 ms

app-scr20.png

app-scr20.png

1920 ms

btn-appstore-dark.png

btn-appstore-dark.png

1869 ms

btn-googleplay-dark.png

btn-googleplay-dark.png

1919 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

83 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf

97 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf

99 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1892 ms

analytics.js

analytics.js

96 ms

bx_loader.gif

bx_loader.gif

1608 ms

bx_loader.gif

bx_loader.gif

1660 ms

collect

collect

13 ms

js

js

57 ms

Accessibility Review

mycancertracker.com accessibility score

82

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.

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

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

mycancertracker.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mycancertracker.com SEO score

92

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

mycancertracker.com

Open Graph description is not detected on the main page of My Cancer Tracker. 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: