Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

jotec.net

Homepage - Artivion

Page Load Speed

2.8 sec in total

First Response

372 ms

Resources Loaded

2.1 sec

Page Rendered

344 ms

jotec.net screenshot

About Website

Visit jotec.net now to see the best up-to-date Jotec content and also check out these interesting facts you probably never knew about jotec.net

Our purpose is to develop simple, elegant solutions that address cardiac and vascular surgeons' most difficult challenges in treating patients with diseases.

Visit jotec.net

Key Findings

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

Performance Metrics

jotec.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value6,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

jotec.net

372 ms

152 ms

css

26 ms

01e412b0f7dd.css

327 ms

jquery-1.11.0.min.js

11 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Jotec.net, 80% (44 requests) were made to Jotec.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (672 ms) relates to the external source Jotec.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (64%)

Content Size

1.8 MB

After Optimization

660.4 kB

In fact, the total size of Jotec.net main page is 1.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. 40% of websites need less resources to load. Javascripts take 846.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.7 kB

  • Original 37.5 kB
  • After minification 36.8 kB
  • After compression 7.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. 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 29.7 kB or 79% of the original size.

Image Optimization

-25%

Potential reduce by 142.1 kB

  • Original 561.2 kB
  • After minification 419.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. Obviously, Jotec needs image optimization as it can save up to 142.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 655.2 kB

  • Original 846.8 kB
  • After minification 658.2 kB
  • After compression 191.7 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 655.2 kB or 77% of the original size.

CSS Optimization

-89%

Potential reduce by 341.8 kB

  • Original 383.8 kB
  • After minification 234.3 kB
  • After compression 41.9 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. Jotec.net needs all CSS files to be minified and compressed as it can save up to 341.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

47

After Optimization

27

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

Accessibility Review

jotec.net accessibility score

83

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

jotec.net 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

jotec.net SEO score

82

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 Jotec.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 Jotec.net 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

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