Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ebox.net

Fournisseur Internet au Québec et en Ontario | EBOX

Page Load Speed

3 sec in total

First Response

254 ms

Resources Loaded

2.5 sec

Page Rendered

265 ms

About Website

Welcome to ebox.net homepage info - get ready to check EBOX best content for Canada right away, or after learning these important things about ebox.net

Fournisseur Internet au Québec et en Ontario, EBOX offre l'Internet Haute Vitesse et la Téléphonie IP au meilleur prix sur le marché. 

Visit ebox.net

Key Findings

We analyzed Ebox.net page load time and found that the first response time was 254 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ebox.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.0 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

ebox.net

254 ms

www.ebox.ca

976 ms

gtm.js

71 ms

style.min.css

61 ms

style.min.css

50 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ebox.net, 95% (76 requests) were made to Ebox.ca and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (976 ms) relates to the external source Ebox.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (49%)

Content Size

2.1 MB

After Optimization

1.1 MB

In fact, the total size of Ebox.net main page is 2.1 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. 70% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 897.8 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 333.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. 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 897.8 kB or 73% of the original size.

Image Optimization

-16%

Potential reduce by 7.3 kB

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

JavaScript Optimization

-15%

Potential reduce by 97.6 kB

  • Original 669.8 kB
  • After minification 665.4 kB
  • After compression 572.2 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 97.6 kB or 15% of the original size.

CSS Optimization

-16%

Potential reduce by 22.3 kB

  • Original 143.1 kB
  • After minification 143.1 kB
  • After compression 120.8 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. Ebox.net needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (46%)

Requests Now

70

After Optimization

38

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

Accessibility Review

ebox.net accessibility score

84

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

High

ARIA IDs are not unique

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

Form elements do not have associated labels

Best Practices

ebox.net best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

ebox.net 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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebox.net can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Ebox.net 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 data is detected on the main page of EBOX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: