Tools & Wizards About Us
oncxerna.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

oncxerna.com

OncXerna | Advancing state-of-the-art precision medicine

Page Load Speed

1.8 sec in total

First Response

215 ms

Resources Loaded

1.5 sec

Page Rendered

58 ms

oncxerna.com screenshot

About Website

Welcome to oncxerna.com homepage info - get ready to check Onc Xerna best content right away, or after learning these important things about oncxerna.com

OncXerna is advancing state-of-the-art precision medicine to dramatically improve the lives of patients.

Visit oncxerna.com

Key Findings

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

oncxerna.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

215 ms

burger-menu-styles.min.css

93 ms

frontend-general.min.css

94 ms

icons.css

102 ms

cookie-law-info-public.css

100 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 70% of them (46 requests) were addressed to the original Oncxerna.com, 27% (18 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (703 ms) belongs to the original domain Oncxerna.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.8 kB (39%)

Content Size

393.5 kB

After Optimization

238.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Oncxerna.com main page is 393.5 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. 60% of websites need less resources to load. HTML takes 186.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 150.3 kB

  • Original 186.0 kB
  • After minification 184.7 kB
  • After compression 35.7 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 150.3 kB or 81% of the original size.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

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

CSS Optimization

-9%

Potential reduce by 2.0 kB

  • Original 22.7 kB
  • After minification 22.5 kB
  • After compression 20.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. Oncxerna.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (96%)

Requests Now

47

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

215 ms

burger-menu-styles.min.css

burger-menu-styles.min.css

93 ms

frontend-general.min.css

frontend-general.min.css

94 ms

icons.css

icons.css

102 ms

cookie-law-info-public.css

cookie-law-info-public.css

100 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

101 ms

wp_head.css

wp_head.css

141 ms

menu_fullscreen.min.css

menu_fullscreen.min.css

244 ms

divi-mobile-stop-stacking.min.css

divi-mobile-stop-stacking.min.css

182 ms

front-91dfe18c.min.css

front-91dfe18c.min.css

182 ms

style.min.css

style.min.css

216 ms

dsm-easy-tb.css

dsm-easy-tb.css

182 ms

ytprefs.min.css

ytprefs.min.css

238 ms

lity.min.css

lity.min.css

264 ms

embdyn.min.css

embdyn.min.css

261 ms

single-jv-team.css

single-jv-team.css

399 ms

magnific-popup.css

magnific-popup.css

299 ms

style.css

style.css

361 ms

jquery.min.js

jquery.min.js

341 ms

jquery-migrate.min.js

jquery-migrate.min.js

365 ms

cookie-law-info-public.js

cookie-law-info-public.js

356 ms

lity.min.js

lity.min.js

390 ms

ytprefs.min.js

ytprefs.min.js

453 ms

jquery.cookie.min.js

jquery.cookie.min.js

569 ms

embdyn.min.js

embdyn.min.js

454 ms

et-core-unified-235164.min.css

et-core-unified-235164.min.css

503 ms

email-decode.min.js

email-decode.min.js

392 ms

classie.js

classie.js

518 ms

TimelineMax.min.js

TimelineMax.min.js

26 ms

TweenMax.min.js

TweenMax.min.js

36 ms

scripts.min.js

scripts.min.js

525 ms

smoothscroll.js

smoothscroll.js

552 ms

front-91dfe18c.min.js

front-91dfe18c.min.js

541 ms

front-e4622e1b.min.js

front-e4622e1b.min.js

610 ms

front-9d87c420.min.js

front-9d87c420.min.js

642 ms

front-1d58e40a.min.js

front-1d58e40a.min.js

643 ms

front-ef9b14c7.min.js

front-ef9b14c7.min.js

643 ms

front-aef08774.min.js

front-aef08774.min.js

644 ms

front-91961416.min.js

front-91961416.min.js

661 ms

front-84b834a8.min.js

front-84b834a8.min.js

619 ms

jquery.fitvids.js

jquery.fitvids.js

668 ms

frontend-bundle.min.js

frontend-bundle.min.js

693 ms

new-tab.js

new-tab.js

654 ms

common.js

common.js

697 ms

dsm-easy-tb.js

dsm-easy-tb.js

635 ms

fitvids.min.js

fitvids.min.js

630 ms

wp_footer.js

wp_footer.js

703 ms

magnific-popup.js

magnific-popup.js

651 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNis.woff

61 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNig.ttf

60 ms

font

font

62 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNig.ttf

61 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNis.woff

60 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNig.ttf

67 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNis.woff

69 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXNig.ttf

68 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNis.woff

68 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWNig.ttf

70 ms

font

font

68 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf

70 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNis.woff

71 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNig.ttf

72 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNis.woff

73 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQNig.ttf

74 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNis.woff

74 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQNig.ttf

89 ms

Accessibility Review

oncxerna.com accessibility score

81

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.

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

oncxerna.com best practices score

83

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

SEO Factors

oncxerna.com SEO score

92

Search Engine Optimization Advices

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

oncxerna.com

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