Tools & Wizards About Us
oricom.ca screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

oricom.ca

Compagnie Internet la moins chère au Québec | Oricom.ca

Page Load Speed

1.3 sec in total

First Response

66 ms

Resources Loaded

928 ms

Page Rendered

295 ms

oricom.ca screenshot

About Website

Welcome to oricom.ca homepage info - get ready to check Oricom best content for Canada right away, or after learning these important things about oricom.ca

Internet provider since 1995, ORICOM INTERNET has the best technologies available anywhere in Canada, which allows us to adapt to the needs of our business and residential customers.

Visit oricom.ca

Key Findings

We analyzed Oricom.ca page load time and found that the first response time was 66 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

oricom.ca performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.267

46/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

oricom.ca

66 ms

oricom.ca

85 ms

www.oricom.ca

175 ms

css2

47 ms

DependencyHandler.axd

44 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Oricom.ca, 9% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (532 ms) belongs to the original domain Oricom.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.1 kB (67%)

Content Size

91.4 kB

After Optimization

30.2 kB

  • HTML
  • JavaScript

In fact, the total size of Oricom.ca main page is 91.4 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. 45% of websites need less resources to load. HTML takes 70.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 61.1 kB

  • Original 70.4 kB
  • After minification 39.3 kB
  • After compression 9.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 31.1 kB, which is 44% 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 61.1 kB or 87% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 25 (50%)

Requests Now

50

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oricom.ca

oricom.ca

66 ms

oricom.ca

oricom.ca

85 ms

www.oricom.ca

www.oricom.ca

175 ms

css2

css2

47 ms

DependencyHandler.axd

DependencyHandler.axd

44 ms

all.min.css

all.min.css

37 ms

DependencyHandler.axd

DependencyHandler.axd

70 ms

analytics.js

analytics.js

32 ms

js

js

136 ms

DependencyHandler.axd

DependencyHandler.axd

315 ms

gtm.js

gtm.js

100 ms

fbevents.js

fbevents.js

100 ms

logo.svg

logo.svg

170 ms

mail.svg

mail.svg

171 ms

social.svg

social.svg

250 ms

small-phone.svg

small-phone.svg

251 ms

grille.png

grille.png

285 ms

bk-gradient.svg

bk-gradient.svg

296 ms

jeune-gamer-1.png

jeune-gamer-1.png

400 ms

internet_image1_1.png

internet_image1_1.png

321 ms

slide3-grand.png

slide3-grand.png

331 ms

logo-protegezvous.png

logo-protegezvous.png

299 ms

slide2-grand.png

slide2-grand.png

495 ms

slide2-petit.png

slide2-petit.png

409 ms

triangle-y.svg

triangle-y.svg

321 ms

round-low-g.svg

round-low-g.svg

343 ms

round-low-y.svg

round-low-y.svg

342 ms

round-p.svg

round-p.svg

353 ms

forfaits.png

forfaits.png

364 ms

internetg.png

internetg.png

370 ms

telephonie.png

telephonie.png

408 ms

demenagement.png

demenagement.png

406 ms

affaires.png

affaires.png

391 ms

choixoricom.png

choixoricom.png

419 ms

circle.svg

circle.svg

424 ms

section2-1.png

section2-1.png

532 ms

section2-2.png

section2-2.png

434 ms

section2-4.jpeg

section2-4.jpeg

457 ms

google-logo.png

google-logo.png

440 ms

star-on.svg

star-on.svg

445 ms

star-off.svg

star-off.svg

469 ms

section3-2.png

section3-2.png

467 ms

section4-1.png

section4-1.png

504 ms

section4-2.png

section4-2.png

521 ms

round-up-p.svg

round-up-p.svg

489 ms

round-up-g.svg

round-up-g.svg

490 ms

collect

collect

39 ms

round-up-y.svg

round-up-y.svg

463 ms

92zPtBhPNqw79Ij1E865zBUv7myRJQVF.woff

92zPtBhPNqw79Ij1E865zBUv7myRJQVF.woff

118 ms

92zPtBhPNqw79Ij1E865zBUv7myjJQVF.woff

92zPtBhPNqw79Ij1E865zBUv7myjJQVF.woff

119 ms

92zPtBhPNqw79Ij1E865zBUv7mz9JQVF.woff

92zPtBhPNqw79Ij1E865zBUv7mz9JQVF.woff

205 ms

92zPtBhPNqw79Ij1E865zBUv7mx9IgVF.woff

92zPtBhPNqw79Ij1E865zBUv7mx9IgVF.woff

205 ms

92zPtBhPNqw79Ij1E865zBUv7mxEIgVF.woff

92zPtBhPNqw79Ij1E865zBUv7mxEIgVF.woff

208 ms

collect

collect

197 ms

circle-blue.svg

circle-blue.svg

351 ms

fb-logo.png

fb-logo.png

362 ms

logo.png

logo.png

286 ms

ga-audiences

ga-audiences

31 ms

Accessibility Review

oricom.ca accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

oricom.ca best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

oricom.ca SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oricom.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 Oricom.ca main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

oricom.ca

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