Tools & Wizards About Us

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

helius.com

Helius Therapeutics | Medicinal Cannabis | New Zealand

Page Load Speed

3.5 sec in total

First Response

634 ms

Resources Loaded

2.8 sec

Page Rendered

114 ms

About Website

Welcome to helius.com homepage info - get ready to check Helius best content for United States right away, or after learning these important things about helius.com

Helius Therapeutics is a biotechnology company focused on medicinal cannabis research and development in Auckland, New Zealand

Visit helius.com

Key Findings

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

Performance Metrics

helius.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

helius.com

634 ms

www.helius.co.nz

838 ms

minified.js

67 ms

focus-within-polyfill.js

177 ms

polyfill.min.js

179 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 Helius.com, 55% (30 requests) were made to Static.wixstatic.com and 33% (18 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.2 kB (64%)

Content Size

966.0 kB

After Optimization

348.8 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-79%

Potential reduce by 497.5 kB

  • Original 626.6 kB
  • After minification 624.8 kB
  • After compression 129.1 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 497.5 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 25.3 kB

  • Original 201.1 kB
  • After minification 175.8 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, Helius needs image optimization as it can save up to 25.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 94.5 kB

  • Original 138.3 kB
  • After minification 138.3 kB
  • After compression 43.9 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 94.5 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (19%)

Requests Now

47

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

helius.com accessibility score

87

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

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

Heading elements are not in a sequentially-descending order

Best Practices

helius.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

helius.com SEO score

100

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

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