Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ior.ca

Truck Accessories Edmonton | Custom Parts | Prince George | Grande Prairie | IOR.ca

Page Load Speed

3.9 sec in total

First Response

439 ms

Resources Loaded

2.9 sec

Page Rendered

595 ms

ior.ca screenshot

About Website

Click here to check amazing IOR content. Otherwise, check out these important facts you probably never knew about ior.ca

Interior Offroad Equipment in Grande Prairie, Prince George & Edmonton has been serving the light truck industry since 1977. For all your needs in truck products, accessories and equipment.

Visit ior.ca

Key Findings

We analyzed Ior.ca page load time and found that the first response time was 439 ms and then it took 3.5 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

ior.ca performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

ior.ca

439 ms

css

35 ms

bu2l.css

410 ms

css

49 ms

bu2l.css

224 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 59% of them (52 requests) were addressed to the original Ior.ca, 20% (18 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Ior.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.5 kB (11%)

Content Size

1.5 MB

After Optimization

1.3 MB

In fact, the total size of Ior.ca main page is 1.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 951.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 100.8 kB

  • Original 125.7 kB
  • After minification 116.3 kB
  • After compression 24.9 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 100.8 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 60.4 kB

  • Original 951.4 kB
  • After minification 891.0 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. IOR images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.4 kB

  • Original 283.8 kB
  • After minification 283.8 kB
  • After compression 278.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

-3%

Potential reduce by 3.8 kB

  • Original 125.1 kB
  • After minification 125.1 kB
  • After compression 121.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. Ior.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (59%)

Requests Now

81

After Optimization

33

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

Accessibility Review

ior.ca accessibility score

92

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.

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

Links do not have a discernible name

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

ior.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ior.ca SEO score

86

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

High

robots.txt is not valid

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 Ior.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 Ior.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 data is detected on the main page of IOR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: