Tools & Wizards About Us
ctcr.in screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ctcr.in

Centre for Translational Cancer Research – CTCR

Page Load Speed

6 sec in total

First Response

942 ms

Resources Loaded

4.7 sec

Page Rendered

399 ms

ctcr.in screenshot

About Website

Welcome to ctcr.in homepage info - get ready to check CTCR best content right away, or after learning these important things about ctcr.in

Visit ctcr.in

Key Findings

We analyzed Ctcr.in page load time and found that the first response time was 942 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ctcr.in performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

ctcr.in

942 ms

style.min.css

89 ms

view.css

231 ms

mediaelementplayer-legacy.min.css

93 ms

wp-mediaelement.min.css

91 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 58% of them (51 requests) were addressed to the original Ctcr.in, 18% (16 requests) were made to I0.wp.com and 10% (9 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ctcr.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.9 kB (11%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ctcr.in main page is 1.3 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 521.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 134.0 kB

  • Original 158.2 kB
  • After minification 154.3 kB
  • After compression 24.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 134.0 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 5.7 kB

  • Original 521.8 kB
  • After minification 516.1 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. CTCR images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 412.3 kB
  • After minification 412.3 kB
  • After compression 410.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.8 kB

  • Original 176.1 kB
  • After minification 175.9 kB
  • After compression 174.3 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. Ctcr.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 58 (73%)

Requests Now

79

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ctcr.in

ctcr.in

942 ms

style.min.css

style.min.css

89 ms

view.css

view.css

231 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

93 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

91 ms

styles.css

styles.css

461 ms

learndash_quiz_front.min.css

learndash_quiz_front.min.css

472 ms

jquery.dropdown.min.css

jquery.dropdown.min.css

489 ms

learndash_lesson_video.min.css

learndash_lesson_video.min.css

488 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

484 ms

grid-system.css

grid-system.css

498 ms

style.css

style.css

696 ms

header-layout-centered-bottom-bar.css

header-layout-centered-bottom-bar.css

707 ms

element-team-member.css

element-team-member.css

717 ms

element-icon-with-text.css

element-icon-with-text.css

728 ms

element-wpb-column-border.css

element-wpb-column-border.css

732 ms

cf7.css

cf7.css

738 ms

css

css

111 ms

responsive.css

responsive.css

926 ms

flickity.css

flickity.css

942 ms

skin-material.css

skin-material.css

952 ms

menu-dynamic.css

menu-dynamic.css

969 ms

learndash.min.css

learndash.min.css

981 ms

js_composer.min.css

js_composer.min.css

979 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

1160 ms

style.css

style.css

1176 ms

css

css

67 ms

jetpack.css

jetpack.css

76 ms

jquery.min.js

jquery.min.js

88 ms

jquery-migrate.min.js

jquery-migrate.min.js

86 ms

animate.min.css

animate.min.css

1239 ms

style-non-critical.css

style-non-critical.css

1241 ms

jquery.fancybox.css

jquery.fancybox.css

1241 ms

core.css

core.css

1241 ms

slide-out-right-material.css

slide-out-right-material.css

1440 ms

slide-out-right-hover.css

slide-out-right-hover.css

1439 ms

image-cdn.js

image-cdn.js

1440 ms

index.js

index.js

1474 ms

index.js

index.js

1484 ms

jquery.easing.min.js

jquery.easing.min.js

1475 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

1669 ms

priority.js

priority.js

1674 ms

transit.min.js

transit.min.js

1673 ms

waypoints.js

waypoints.js

1715 ms

api.js

api.js

107 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

84 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

84 ms

wp-polyfill.min.js

wp-polyfill.min.js

83 ms

e-202410.js

e-202410.js

83 ms

imagesLoaded.min.js

imagesLoaded.min.js

1712 ms

hoverintent.min.js

hoverintent.min.js

1507 ms

jquery.fancybox.js

jquery.fancybox.js

1453 ms

anime.min.js

anime.min.js

1446 ms

flickity.js

flickity.js

1436 ms

superfish.js

superfish.js

1478 ms

init.js

init.js

1732 ms

touchswipe.min.js

touchswipe.min.js

1483 ms

learndash.js

learndash.js

1440 ms

index.js

index.js

1443 ms

js_composer_front.min.js

js_composer_front.min.js

1440 ms

iiser_logo_resize.png

iiser_logo_resize.png

276 ms

bajaj.png

bajaj.png

1000 ms

pccm.png

pccm.png

275 ms

cropped-icgalogo.png

cropped-icgalogo.png

276 ms

RTPCR-logo2_resize.png

RTPCR-logo2_resize.png

286 ms

bajaj.png

bajaj.png

287 ms

event_icon-removebg.png

event_icon-removebg.png

279 ms

swasthya.jpg

swasthya.jpg

286 ms

TCS_.png

TCS_.png

284 ms

STRAND.png

STRAND.png

285 ms

UEA.png

UEA.png

284 ms

PRANA.png

PRANA.png

326 ms

ChennaiBreastCentre.jpg

ChennaiBreastCentre.jpg

325 ms

stryker.png

stryker.png

324 ms

ICGA.png

ICGA.png

325 ms

TataMemorialHospital.jpg

TataMemorialHospital.jpg

324 ms

Ctcr_office_pic.png

Ctcr_office_pic.png

1273 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

56 ms

font

font

166 ms

font

font

167 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

1777 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

101 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

128 ms

font

font

165 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

165 ms

icomoon.woff

icomoon.woff

936 ms

recaptcha__en.js

recaptcha__en.js

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

460 ms

Accessibility Review

ctcr.in accessibility score

90

Accessibility Issues

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

ctcr.in 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ctcr.in 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

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 Ctcr.in 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 Ctcr.in 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

ctcr.in

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