Tools & Wizards About Us
io.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

io.org

Primus

Page Load Speed

2 sec in total

First Response

578 ms

Resources Loaded

1.3 sec

Page Rendered

161 ms

io.org screenshot

About Website

Visit io.org now to see the best up-to-date Io content for United States and also check out these interesting facts you probably never knew about io.org

: Primus offers a smarter connectivity choice for Canadian consumers, businesses and wholesale customers.

Visit io.org

Key Findings

We analyzed Io.org page load time and found that the first response time was 578 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

io.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

primus.ca

578 ms

tracking-header.js

28 ms

PrimusScript.js

54 ms

t.js

40 ms

jquery.js

118 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Io.org, 9% (2 requests) were made to Px.spiceworks.com and 9% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (578 ms) relates to the external source Primus.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.3 kB (33%)

Content Size

517.9 kB

After Optimization

348.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Io.org main page is 517.9 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. 15% of websites need less resources to load. Images take 338.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 15.0 kB

  • Original 18.3 kB
  • After minification 16.2 kB
  • After compression 3.3 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.0 kB, which is 11% 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 15.0 kB or 82% of the original size.

Image Optimization

-17%

Potential reduce by 56.4 kB

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

JavaScript Optimization

-60%

Potential reduce by 94.0 kB

  • Original 156.6 kB
  • After minification 147.8 kB
  • After compression 62.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 94.0 kB or 60% of the original size.

CSS Optimization

-77%

Potential reduce by 3.9 kB

  • Original 5.0 kB
  • After minification 3.8 kB
  • After compression 1.1 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. Io.org needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (33%)

Requests Now

21

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

primus.ca

primus.ca

578 ms

tracking-header.js

tracking-header.js

28 ms

PrimusScript.js

PrimusScript.js

54 ms

t.js

t.js

40 ms

jquery.js

jquery.js

118 ms

jquery.quickflip.source.js

jquery.quickflip.source.js

93 ms

basic-quickflips.css

basic-quickflips.css

91 ms

style.css

style.css

92 ms

px.js

px.js

38 ms

ga.js

ga.js

35 ms

Primus.Logo.png

Primus.Logo.png

39 ms

newresiIcons.png

newresiIcons.png

108 ms

btn.go.png

btn.go.png

42 ms

newbusiIcons.png

newbusiIcons.png

108 ms

__utm.gif

__utm.gif

14 ms

elqCfg.min.js

elqCfg.min.js

88 ms

newWelcomeToPrimus.png

newWelcomeToPrimus.png

98 ms

tileBlankl.png

tileBlankl.png

24 ms

tileBlankr.png

tileBlankr.png

23 ms

hiring.png

hiring.png

24 ms

a9si

a9si

13 ms

svrGP

svrGP

265 ms

svrGP.aspx

svrGP.aspx

47 ms

Accessibility Review

io.org accessibility score

100

Accessibility Issues

Best Practices

io.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

io.org SEO score

85

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

robots.txt is not valid

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 Io.org 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 Io.org 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

io.org

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