Tools & Wizards About Us
oncoqr.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

oncoqr.com

Biotech start-up that develops cancer immunotherapies | OncoQR ML

Page Load Speed

5.8 sec in total

First Response

591 ms

Resources Loaded

4.5 sec

Page Rendered

728 ms

oncoqr.com screenshot

About Website

Click here to check amazing OncoQR content. Otherwise, check out these important facts you probably never knew about oncoqr.com

Our vision is to defeat cancer. Our aim is to fully arm the patient’s immune system to successfully fight and thus win the battle against cancer.

Visit oncoqr.com

Key Findings

We analyzed Oncoqr.com page load time and found that the first response time was 591 ms and then it took 5.2 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

oncoqr.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

oncoqr.com

591 ms

wp-emoji-release.min.js

257 ms

styles.css

282 ms

settings.css

376 ms

settings.css

378 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 98% of them (60 requests) were addressed to the original Oncoqr.com, 2% (1 request) were made to Oncoqr.com.dedi4187.your-server.de. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Oncoqr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (81%)

Content Size

2.8 MB

After Optimization

538.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oncoqr.com main page is 2.8 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. 45% of websites need less resources to load. CSS take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 74.8 kB

  • Original 95.3 kB
  • After minification 92.8 kB
  • After compression 20.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 74.8 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 14.3 kB

  • Original 139.6 kB
  • After minification 125.3 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. OncoQR images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 629.2 kB

  • Original 868.4 kB
  • After minification 849.3 kB
  • After compression 239.2 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 629.2 kB or 72% of the original size.

CSS Optimization

-91%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 153.1 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. Oncoqr.com needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (76%)

Requests Now

58

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oncoqr.com

oncoqr.com

591 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

257 ms

styles.css

styles.css

282 ms

settings.css

settings.css

376 ms

settings.css

settings.css

378 ms

fontello.min.css

fontello.min.css

285 ms

style.css

style.css

381 ms

core.animation.min.css

core.animation.min.css

349 ms

theme.shortcodes.css

theme.shortcodes.css

656 ms

plugin.instagram-widget.min.css

plugin.instagram-widget.min.css

380 ms

skin.css

skin.css

631 ms

custom-style.min.css

custom-style.min.css

469 ms

responsive.css

responsive.css

563 ms

skin.responsive.min.css

skin.responsive.min.css

469 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

470 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

563 ms

front.min.css

front.min.css

502 ms

js_composer.min.css

js_composer.min.css

878 ms

oncoqr.com

oncoqr.com

852 ms

jquery.js

jquery.js

598 ms

jquery-migrate.min.js

jquery-migrate.min.js

597 ms

lightbox.js

lightbox.js

659 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

684 ms

jquery.themepunch.essential.min.js

jquery.themepunch.essential.min.js

876 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

686 ms

modernizr.min.js

modernizr.min.js

753 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

778 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

781 ms

style.cssRoboto%3A500

style.cssRoboto%3A500

2920 ms

core.messages.min.css

core.messages.min.css

781 ms

js_composer_tta.min.css

js_composer_tta.min.css

877 ms

prettyPhoto.min.css

prettyPhoto.min.css

851 ms

scripts.js

scripts.js

874 ms

superfish.min.js

superfish.min.js

877 ms

jquery.slidemenu.min.js

jquery.slidemenu.min.js

878 ms

core.utils.min.js

core.utils.min.js

945 ms

core.init.js

core.init.js

968 ms

theme.init.min.js

theme.init.min.js

877 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

849 ms

front.min.js

front.min.js

848 ms

wp-embed.min.js

wp-embed.min.js

849 ms

theme.shortcodes.min.js

theme.shortcodes.min.js

847 ms

core.messages.min.js

core.messages.min.js

845 ms

style.css

style.css

942 ms

js_composer_front.min.js

js_composer_front.min.js

846 ms

vc-accordion.min.js

vc-accordion.min.js

824 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

847 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

847 ms

OncoQRML-Logo-iloveimg-cropped-1.png

OncoQRML-Logo-iloveimg-cropped-1.png

491 ms

dummy.png

dummy.png

96 ms

aboutus-150x150.png

aboutus-150x150.png

102 ms

technology-150x150.png

technology-150x150.png

101 ms

collaboration-150x150.png

collaboration-150x150.png

102 ms

Christof-Langer-370x370.jpg

Christof-Langer-370x370.jpg

101 ms

W5-Wall-blurr-bw-370x370.jpg

W5-Wall-blurr-bw-370x370.jpg

102 ms

OncoQRML-Footer.png

OncoQRML-Footer.png

191 ms

fontello.woff

fontello.woff

282 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

201 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

142 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

200 ms

revolution.extension.kenburn.min.js

revolution.extension.kenburn.min.js

143 ms

Accessibility Review

oncoqr.com accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

oncoqr.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

oncoqr.com SEO score

84

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

High

Tap targets are not sized appropriately

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

oncoqr.com

Open Graph data is detected on the main page of OncoQR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: