Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

inso.ca

Accueil - Solutions informatiques INSO

Page Load Speed

5.1 sec in total

First Response

1.3 sec

Resources Loaded

3.6 sec

Page Rendered

277 ms

inso.ca screenshot

About Website

Visit inso.ca now to see the best up-to-date INSO content for Canada and also check out these interesting facts you probably never knew about inso.ca

Chef de fil en intégration de solution technologique et informatique, depuis 1983, notre dynamisme et notre créativité nous ont permis de nous adapter aux besoins d’un large éventail de clients, tout ...

Visit inso.ca

Key Findings

We analyzed Inso.ca page load time and found that the first response time was 1.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

inso.ca performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

shop.inso.ca

1267 ms

css

110 ms

contentslider.css

67 ms

default.advanced.css

69 ms

jquery.ad-gallery.css

65 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Inso.ca, 3% (2 requests) were made to Analytic.registrationone.ca and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Shop.inso.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (62%)

Content Size

2.0 MB

After Optimization

771.7 kB

In fact, the total size of Inso.ca main page is 2.0 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. Javascripts take 909.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.7 kB

  • Original 43.0 kB
  • After minification 33.5 kB
  • After compression 8.2 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 9.5 kB, which is 22% 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 34.7 kB or 81% of the original size.

Image Optimization

-44%

Potential reduce by 352.5 kB

  • Original 810.2 kB
  • After minification 457.7 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, INSO needs image optimization as it can save up to 352.5 kB or 44% 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 640.3 kB

  • Original 909.9 kB
  • After minification 847.4 kB
  • After compression 269.6 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 640.3 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 220.7 kB

  • Original 256.8 kB
  • After minification 186.6 kB
  • After compression 36.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. Inso.ca needs all CSS files to be minified and compressed as it can save up to 220.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (72%)

Requests Now

74

After Optimization

21

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

Accessibility Review

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

inso.ca SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inso.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Inso.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 INSO. 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: