Tools & Wizards About Us
ihaterogers.ca screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

ihaterogers.ca

I hate Rogers Cable, Rogers Video, Rogers wireless, Rogers mobility, Rogers AT&T;, Rogers Internet and son and so forth - get it, ihaterogers, ihatero...

Page Load Speed

2.5 sec in total

First Response

535 ms

Resources Loaded

1.6 sec

Page Rendered

441 ms

ihaterogers.ca screenshot

About Website

Click here to check amazing I Hate Rogers content. Otherwise, check out these important facts you probably never knew about ihaterogers.ca

The anti Rogers Cable, Rogers Video, Rogers wireless, Rogers mobility, Rogers AT&T, Rogers Internet web site offering alternatives to products and services provided by Rogers.

Visit ihaterogers.ca

Key Findings

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

Performance Metrics

ihaterogers.ca performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

ihaterogers.ca

535 ms

gereralstyle.css

410 ms

embed

217 ms

embed

193 ms

embed

225 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 50% of them (26 requests) were addressed to the original Ihaterogers.ca, 48% (25 requests) were made to Google.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ihaterogers.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.8 kB (68%)

Content Size

30.4 kB

After Optimization

9.6 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 20.7 kB

  • Original 27.7 kB
  • After minification 26.3 kB
  • After compression 7.0 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 20.7 kB or 75% of the original size.

JavaScript Optimization

-3%

Potential reduce by 77 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.4 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

-14%

Potential reduce by 33 B

  • Original 244 B
  • After minification 244 B
  • After compression 211 B

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. Ihaterogers.ca needs all CSS files to be minified and compressed as it can save up to 33 B or 14% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ihaterogers.ca

ihaterogers.ca

535 ms

gereralstyle.css

gereralstyle.css

410 ms

embed

embed

217 ms

embed

embed

193 ms

embed

embed

225 ms

embed

embed

217 ms

embed

embed

236 ms

embed

embed

194 ms

embed

embed

502 ms

embed

embed

368 ms

embed

embed

421 ms

embed

embed

391 ms

embed

embed

459 ms

embed

embed

426 ms

embed

embed

532 ms

embed

embed

608 ms

embed

embed

605 ms

embed

embed

606 ms

embed

embed

647 ms

embed

embed

643 ms

embed

embed

712 ms

embed

embed

779 ms

embed

embed

785 ms

embed

embed

820 ms

embed

embed

822 ms

embed

embed

822 ms

embed

embed

885 ms

banner1.gif

banner1.gif

198 ms

spacer.gif

spacer.gif

202 ms

index_01.gif

index_01.gif

215 ms

index_02.gif

index_02.gif

205 ms

index_03.gif

index_03.gif

214 ms

index_05.gif

index_05.gif

387 ms

index_08.gif

index_08.gif

409 ms

index_09.gif

index_09.gif

409 ms

index_10.gif

index_10.gif

410 ms

index_11.gif

index_11.gif

416 ms

index_12.gif

index_12.gif

572 ms

index_13.gif

index_13.gif

640 ms

index_14.gif

index_14.gif

583 ms

index_15.gif

index_15.gif

582 ms

index_16.gif

index_16.gif

595 ms

home_03.gif

home_03.gif

613 ms

home_04.gif

home_04.gif

760 ms

home_05.gif

home_05.gif

780 ms

home_11.gif

home_11.gif

763 ms

home_15.gif

home_15.gif

778 ms

home_16.gif

home_16.gif

804 ms

home_17.gif

home_17.gif

1032 ms

home_18.gif

home_18.gif

938 ms

index_27.gif

index_27.gif

948 ms

js

js

57 ms

Accessibility Review

ihaterogers.ca accessibility score

56

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

ihaterogers.ca best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

ihaterogers.ca SEO score

71

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ihaterogers.ca can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ihaterogers.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

ihaterogers.ca

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