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

  • 82

    SEO

    Google-friendlier than
    44% of websites

redax.it

Redax S.p.a. - New drainage technologies born of experience. and innovation.

Page Load Speed

2.9 sec in total

First Response

395 ms

Resources Loaded

2 sec

Page Rendered

497 ms

About Website

Welcome to redax.it homepage info - get ready to check Redax best content right away, or after learning these important things about redax.it

Redax combines experience and innovation with the ability to portray clinical requirements, through continuous cooperation with physicians, engineers and opinion leaders.

Visit redax.it

Key Findings

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

Performance Metrics

redax.it performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

redax.it

395 ms

www.redax.it

485 ms

237 ms

gtm.js

57 ms

main.css

182 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 51% of them (25 requests) were addressed to the original Redax.it, 29% (14 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (732 ms) belongs to the original domain Redax.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.2 kB (10%)

Content Size

2.3 MB

After Optimization

2.0 MB

In fact, the total size of Redax.it main page is 2.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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 127.7 kB

  • Original 158.0 kB
  • After minification 136.8 kB
  • After compression 30.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. This page needs HTML code to be minified as it can gain 21.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 127.7 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 106.4 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Redax images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 331.9 kB
  • After minification 331.9 kB
  • After compression 330.8 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

-0%

Potential reduce by 15 B

  • Original 20.5 kB
  • After minification 20.5 kB
  • After compression 20.5 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. Redax.it has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (21%)

Requests Now

29

After Optimization

23

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

Accessibility Review

redax.it accessibility score

81

Accessibility Issues

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

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

redax.it 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

High

Page has valid source maps

SEO Factors

redax.it 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 Redax.it 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 Redax.it 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 data is detected on the main page of Redax. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: