1.8 sec in total
137 ms
1.2 sec
401 ms
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.comWe analyzed Mycancertracker.com page load time and found that the first response time was 137 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
mycancertracker.com performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value10.1 s
0/100
25%
Value20.3 s
0/100
10%
Value360 ms
72/100
30%
Value0.108
87/100
15%
Value41.0 s
0/100
10%
137 ms
71 ms
125 ms
123 ms
130 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 55% of them (55 requests) were addressed to the original Mycancertracker.com, 39% (39 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (943 ms) belongs to the original domain Mycancertracker.com.
Page size can be reduced by 4.4 MB (19%)
22.7 MB
18.3 MB
In fact, the total size of Mycancertracker.com main page is 22.7 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. 80% 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 22.4 MB which makes up the majority of the site volume.
Potential reduce by 29.2 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.
Potential reduce by 4.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. 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.
Potential reduce by 47.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 47.3 kB or 32% of the original size.
Potential reduce by 4.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. Mycancertracker.com has all CSS files already compressed.
Number of requests can be reduced by 21 (36%)
59
38
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.
mycancertracker.com
137 ms
bootstrap.css
71 ms
font-awesome.min.css
125 ms
simple-line-icons.css
123 ms
main.css
130 ms
custom.css
123 ms
css
19 ms
css
35 ms
js
78 ms
jquery-2.1.1.min.js
156 ms
bootstrap.min.js
166 ms
jquery.easing.min.js
191 ms
jquery.fitvids.js
204 ms
jquery.bxslider.js
203 ms
slick.js
205 ms
jquery.scrollTo-1.4.3.1-min.js
205 ms
jquery.localscroll-1.2.7-min.js
500 ms
wow.min.js
265 ms
jquery.cycle.all.js
265 ms
jquery.maximage.min.js
265 ms
zi-script.js
266 ms
contact-us.js
266 ms
loader.gif
171 ms
full-slide.jpg
415 ms
btn-appstore.png
178 ms
btn-googleplay.png
174 ms
samsung-iphone-image-1.png
398 ms
full-slide2.png
943 ms
full-slide5.png
654 ms
features_one.png
420 ms
features_two.png
535 ms
features_three.png
484 ms
features_four.png
469 ms
app-scr1.png
482 ms
app-scr2.png
539 ms
app-scr3.png
557 ms
app-scr4.png
558 ms
app-scr5.png
601 ms
app-scr6.png
601 ms
app-scr7.png
636 ms
app-scr8.png
626 ms
app-scr9.png
665 ms
app-scr10.png
667 ms
app-scr11.png
692 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjN_mQ.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQUwaEQXjN_mQ.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5OaVQUwaEQXjN_mQ.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5caVQUwaEQXjN_mQ.woff
21 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQUwaEQXjN_mQ.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQUwaEQXjN_mQ.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQUwaEQXjN_mQ.woff
21 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjN_mQ.woff
21 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQUwaEQXjN_mQ.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjN_mQ.woff
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4vaVQUwaEQXjN_mQ.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5OaVQUwaEQXjN_mQ.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5caVQUwaEQXjN_mQ.woff
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4iaVQUwaEQXjN_mQ.woff
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4jaVQUwaEQXjN_mQ.woff
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVQUwaEQXjN_mQ.woff
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQUwaEQXjN_mQ.woff
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQUwaEQXjN_mQ.woff
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjN_mQ.woff
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4vaVQUwaEQXjN_mQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5OaVQUwaEQXjN_mQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5caVQUwaEQXjN_mQ.woff
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4iaVQUwaEQXjN_mQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4jaVQUwaEQXjN_mQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4saVQUwaEQXjN_mQ.woff
37 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQUwaEQXjN_mQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQUwaEQXjN_mQ.woff
36 ms
app-scr12.png
755 ms
app-scr13.png
700 ms
app-scr14.png
714 ms
app-scr15.png
680 ms
app-scr16.png
699 ms
app-scr17.png
724 ms
app-scr18.png
738 ms
app-scr19.png
740 ms
app-scr20.png
701 ms
btn-appstore-dark.png
714 ms
btn-googleplay-dark.png
726 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMCbKsUPpjl.woff
77 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl1RMCbKsUPpjlG8Q.woff
57 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl1BMCbKsUPpjlG8Q.woff
5 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMCbKsUPpjl.woff
31 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl1RMCbKsUPpjlG8Q.woff
33 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl1BMCbKsUPpjlG8Q.woff
54 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMCbKsUPpjl.woff
135 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml1RMCbKsUPpjlG8Q.woff
114 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml1BMCbKsUPpjlG8Q.woff
107 ms
fontawesome-webfont.woff
742 ms
analytics.js
46 ms
bx_loader.gif
478 ms
bx_loader.gif
490 ms
collect
14 ms
js
56 ms
mycancertracker.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mycancertracker.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
mycancertracker.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
![]()
EN
![]()
EN
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.
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: