Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cancermonthly.com

Cancer Monthly- Cancer Treatments Therapy Results, Survival Rates

Page Load Speed

347 ms in total

First Response

51 ms

Resources Loaded

160 ms

Page Rendered

136 ms

cancermonthly.com screenshot

About Website

Visit cancermonthly.com now to see the best up-to-date Cancer Monthly content for United States and also check out these interesting facts you probably never knew about cancermonthly.com

Information about 100s of cancer treatments so that patients can compare therapy, survival rates, toxicity, to make more informed treatment decisions.

Visit cancermonthly.com

Key Findings

We analyzed Cancermonthly.com page load time and found that the first response time was 51 ms and then it took 296 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

cancermonthly.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

cancermonthly.com

51 ms

cancermonthly.css

29 ms

d_basic.css

19 ms

mm2scripts.js

26 ms

StandardScript.js

12 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that all of those requests were addressed to Cancermonthly.com and no external sources were called. The less responsive or slowest element that took the longest time to load (51 ms) belongs to the original domain Cancermonthly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.9 kB (47%)

Content Size

100.2 kB

After Optimization

53.3 kB

In fact, the total size of Cancermonthly.com main page is 100.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 54.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 22.3 kB

  • Original 28.0 kB
  • After minification 23.2 kB
  • After compression 5.8 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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.3 kB or 79% of the original size.

Image Optimization

-20%

Potential reduce by 11.1 kB

  • Original 54.6 kB
  • After minification 43.6 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. Obviously, Cancer Monthly needs image optimization as it can save up to 11.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 4.1 kB

  • Original 6.1 kB
  • After minification 5.6 kB
  • After compression 2.0 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 4.1 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 9.4 kB

  • Original 11.4 kB
  • After minification 7.2 kB
  • After compression 2.0 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. Cancermonthly.com needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (51%)

Requests Now

35

After Optimization

17

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

Accessibility Review

cancermonthly.com accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

cancermonthly.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cancermonthly.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cancermonthly.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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