Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hello.io

Hello IO / Creative Technologies

Page Load Speed

6.2 sec in total

First Response

519 ms

Resources Loaded

5.1 sec

Page Rendered

563 ms

hello.io screenshot

About Website

Click here to check amazing Hello content for Russia. Otherwise, check out these important facts you probably never knew about hello.io

We create immersive high-tech spaces that tell stories and engage people in new experiences.

Visit hello.io

Key Findings

We analyzed Hello.io page load time and found that the first response time was 519 ms and then it took 5.7 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

hello.io performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

en

519 ms

s.css

312 ms

team.jpg

1814 ms

01-beeline.png

1259 ms

02-yandex.png

498 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 89% of them (57 requests) were addressed to the original Hello.io, 3% (2 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Hello.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 721.8 kB (27%)

Content Size

2.7 MB

After Optimization

2.0 MB

In fact, the total size of Hello.io main page is 2.7 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. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.0 kB

  • Original 16.9 kB
  • After minification 14.8 kB
  • After compression 3.9 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 2.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 13.0 kB or 77% of the original size.

Image Optimization

-23%

Potential reduce by 554.3 kB

  • Original 2.5 MB
  • After minification 1.9 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. Obviously, Hello needs image optimization as it can save up to 554.3 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 154.4 kB

  • Original 219.1 kB
  • After minification 197.3 kB
  • After compression 64.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 154.4 kB or 70% of the original size.

Requests Breakdown

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

Requests Now

62

After Optimization

58

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

Accessibility Review

hello.io accessibility score

86

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

hello.io best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hello.io SEO score

86

Search Engine Optimization Advices

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

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 Hello.io 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 Hello.io 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 Hello. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: