Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

i2i.ca

i2i fulfillment | Omni-Channel Order fulfillment | Healthcare

Page Load Speed

1.6 sec in total

First Response

71 ms

Resources Loaded

1.1 sec

Page Rendered

403 ms

About Website

Welcome to i2i.ca homepage info - get ready to check I 2 best content right away, or after learning these important things about i2i.ca

As your inventory fulfillment partner, the team at i2i fulfillment takes care of your omni-channel order fulfillment and logistics needs. And did we mention, we’re certified by Health Canada to serve ...

Visit i2i.ca

Key Findings

We analyzed I2i.ca page load time and found that the first response time was 71 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

i2i.ca performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

i2i.ca

71 ms

i2i.ca

705 ms

jquery-magnific-popup.css

22 ms

jquery.js

69 ms

js

95 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 73% of them (22 requests) were addressed to the original I2i.ca, 10% (3 requests) were made to Maxcdn.bootstrapcdn.com and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (705 ms) belongs to the original domain I2i.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.1 kB (1%)

Content Size

1.6 MB

After Optimization

1.5 MB

In fact, the total size of I2i.ca main page is 1.6 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.3 kB

  • Original 17.8 kB
  • After minification 14.9 kB
  • After compression 4.6 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 3.0 kB, which is 17% 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.3 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 4.6 kB

  • Original 1.4 MB
  • After minification 1.4 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. I 2 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 345 B

  • Original 92.3 kB
  • After minification 92.3 kB
  • After compression 92.0 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

-11%

Potential reduce by 898 B

  • Original 8.2 kB
  • After minification 8.2 kB
  • After compression 7.3 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. I2i.ca needs all CSS files to be minified and compressed as it can save up to 898 B or 11% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

14

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 2. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

i2i.ca accessibility score

91

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

Best Practices

i2i.ca 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

SEO Factors

i2i.ca 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 I2i.ca 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 I2i.ca 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 description is not detected on the main page of I 2. 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: