Tools & Wizards About Us
intello.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

intello.com

WiFi and technology solutions | Intello by TELUS Business

Page Load Speed

1.9 sec in total

First Response

47 ms

Resources Loaded

1.8 sec

Page Rendered

66 ms

intello.com screenshot

About Website

Click here to check amazing Intello content for Canada. Otherwise, check out these important facts you probably never knew about intello.com

Intello by TELUS Business are your WiFi experts. We provide internet access solutions and technology solutions for hospitality and multi-dwelling environments.

Visit intello.com

Key Findings

We analyzed Intello.com page load time and found that the first response time was 47 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

intello.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

www.intello.com

47 ms

minified.js

76 ms

focus-within-polyfill.js

75 ms

polyfill.min.js

876 ms

thunderbolt-commons.14431d95.bundle.min.js

110 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Intello.com, 36% (18 requests) were made to Static.wixstatic.com and 32% (16 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (876 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.3 kB (54%)

Content Size

845.8 kB

After Optimization

390.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Intello.com main page is 845.8 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 466.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 364.8 kB

  • Original 466.6 kB
  • After minification 464.9 kB
  • After compression 101.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 364.8 kB or 78% of the original size.

Image Optimization

-19%

Potential reduce by 9.9 kB

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

JavaScript Optimization

-25%

Potential reduce by 80.5 kB

  • Original 327.8 kB
  • After minification 327.8 kB
  • After compression 247.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.5 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (37%)

Requests Now

30

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.intello.com

www.intello.com

47 ms

minified.js

minified.js

76 ms

focus-within-polyfill.js

focus-within-polyfill.js

75 ms

polyfill.min.js

polyfill.min.js

876 ms

thunderbolt-commons.14431d95.bundle.min.js

thunderbolt-commons.14431d95.bundle.min.js

110 ms

main.e99c0319.bundle.min.js

main.e99c0319.bundle.min.js

112 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

109 ms

lodash.min.js

lodash.min.js

109 ms

react.production.min.js

react.production.min.js

109 ms

react-dom.production.min.js

react-dom.production.min.js

111 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

111 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

111 ms

Intello_TELUS_Business_EN_Vert_WebLogo.png

Intello_TELUS_Business_EN_Vert_WebLogo.png

36 ms

Intello_TELUS_Business_EN_Hor_WebLogo.png

Intello_TELUS_Business_EN_Hor_WebLogo.png

271 ms

26a17a_341485a805384003b38e4ed74cc6bdfdf000.jpg

26a17a_341485a805384003b38e4ed74cc6bdfdf000.jpg

258 ms

c378ef_b67581e8a3fc4026896110dd65db2629~mv2.jpg

c378ef_b67581e8a3fc4026896110dd65db2629~mv2.jpg

372 ms

BW_Endorsed-Supplier.png

BW_Endorsed-Supplier.png

403 ms

Choice_QV.png

Choice_QV.png

366 ms

c378ef_a2f058fae5224a6f873e86df179caa4b~mv2.png

c378ef_a2f058fae5224a6f873e86df179caa4b~mv2.png

354 ms

c378ef_d5279404f78e45f8b498cf116ddb218b~mv2.jpg

c378ef_d5279404f78e45f8b498cf116ddb218b~mv2.jpg

287 ms

c378ef_785d2a485e6548b1b21e3d65b6a51e96~mv2.png

c378ef_785d2a485e6548b1b21e3d65b6a51e96~mv2.png

498 ms

26a17a_b8f5962697c94ff2b4e13a41e0431d9d~mv2.jpg

26a17a_b8f5962697c94ff2b4e13a41e0431d9d~mv2.jpg

294 ms

c378ef_4afad6c0dd4b4a8487bb6badaa2c3922~mv2.png

c378ef_4afad6c0dd4b4a8487bb6badaa2c3922~mv2.png

541 ms

c378ef_56f1eb4097b24cb1b73453cf0c33edc4~mv2.png

c378ef_56f1eb4097b24cb1b73453cf0c33edc4~mv2.png

594 ms

c378ef_cf78a80cbba74b19a0d26ce2e707c51e~mv2.png

c378ef_cf78a80cbba74b19a0d26ce2e707c51e~mv2.png

753 ms

c378ef_598f338c8d0744948959dbb070a71e93~mv2.png

c378ef_598f338c8d0744948959dbb070a71e93~mv2.png

618 ms

bundle.min.js

bundle.min.js

81 ms

file.woff

file.woff

256 ms

file.woff

file.woff

264 ms

file.woff

file.woff

276 ms

file.woff

file.woff

277 ms

112 ms

110 ms

103 ms

104 ms

105 ms

104 ms

139 ms

137 ms

136 ms

132 ms

128 ms

130 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

26 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

20 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

9 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

4 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

5 ms

Accessibility Review

intello.com accessibility score

98

Accessibility Issues

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

intello.com 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

intello.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 Intello.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 Intello.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

intello.com

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