Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

cancerjournal.net

Wolters Kluwer Health

Page Load Speed

1.9 sec in total

First Response

530 ms

Resources Loaded

1.1 sec

Page Rendered

270 ms

About Website

Click here to check amazing Cancerjournal content for India. Otherwise, check out these important facts you probably never knew about cancerjournal.net

Journal of Cancer Research and Therapeutics, cancerjournal, online journal, Impact Factor, Medical oncology, radiation oncology, medical imaging, radiation protection, non-ionising radiation, radiobio...

Visit cancerjournal.net

Key Findings

We analyzed Cancerjournal.net page load time and found that the first response time was 530 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

cancerjournal.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

cancerjournal.net

530 ms

current.css

33 ms

css

70 ms

layer.js

69 ms

jquery-1.9.1.min.js

72 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 68% of them (32 requests) were addressed to the original Cancerjournal.net, 11% (5 requests) were made to Medknow.com and 9% (4 requests) were made to Subscriptions.medknow.com. The less responsive or slowest element that took the longest time to load (530 ms) belongs to the original domain Cancerjournal.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.6 kB (14%)

Content Size

1.1 MB

After Optimization

932.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cancerjournal.net main page is 1.1 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 972.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.7 kB

  • Original 22.6 kB
  • After minification 20.7 kB
  • After compression 5.9 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 16.7 kB or 74% of the original size.

Image Optimization

-12%

Potential reduce by 115.9 kB

  • Original 972.4 kB
  • After minification 856.5 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, Cancerjournal needs image optimization as it can save up to 115.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 17.1 kB

  • Original 75.7 kB
  • After minification 75.6 kB
  • After compression 58.5 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 17.1 kB or 23% of the original size.

CSS Optimization

-41%

Potential reduce by 7.9 kB

  • Original 19.1 kB
  • After minification 19.1 kB
  • After compression 11.2 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. Cancerjournal.net needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (37%)

Requests Now

43

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

cancerjournal.net accessibility score

67

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

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

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

cancerjournal.net best practices score

75

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cancerjournal.net SEO score

75

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cancerjournal.net 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 Cancerjournal.net main page’s claimed encoding is windows-1252. 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 Cancerjournal. 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: