Tools & Wizards About Us
iem.ca screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

iem.ca

Bulk Material Handling Equipment | Belt Feeder | Apron Feeder

Page Load Speed

2.3 sec in total

First Response

163 ms

Resources Loaded

1.7 sec

Page Rendered

437 ms

iem.ca screenshot

About Website

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

IEM designs and manufactures bulk material handling equipment including: apron feeders, belt feeders, conveyors, and debarkers

Visit iem.ca

Key Findings

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

Performance Metrics

iem.ca performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

iem.ca

163 ms

iem.ca

521 ms

bootstrap.min.css

30 ms

font-awesome.min.css

40 ms

owl.carousel.min.css

233 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 77% of them (36 requests) were addressed to the original Iem.ca, 11% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (946 ms) belongs to the original domain Iem.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 379.4 kB (16%)

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iem.ca main page is 2.4 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. 45% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 39.4 kB

  • Original 45.0 kB
  • After minification 28.1 kB
  • After compression 5.5 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 16.9 kB, which is 37% 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 39.4 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 6.4 kB

  • Original 2.0 MB
  • After minification 2.0 MB

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. Iem images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 65.2 kB

  • Original 93.5 kB
  • After minification 93.5 kB
  • After compression 28.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 65.2 kB or 70% of the original size.

CSS Optimization

-90%

Potential reduce by 268.4 kB

  • Original 296.8 kB
  • After minification 194.3 kB
  • After compression 28.4 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. Iem.ca needs all CSS files to be minified and compressed as it can save up to 268.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

39

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iem.ca

iem.ca

163 ms

iem.ca

iem.ca

521 ms

bootstrap.min.css

bootstrap.min.css

30 ms

font-awesome.min.css

font-awesome.min.css

40 ms

owl.carousel.min.css

owl.carousel.min.css

233 ms

owl.theme.default.min.css

owl.theme.default.min.css

238 ms

style.css

style.css

788 ms

logo.png

logo.png

165 ms

mining.jpg

mining.jpg

469 ms

Pulp&Paper%20Industry.jpg

Pulp&Paper%20Industry.jpg

470 ms

oil-sands.jpg

oil-sands.jpg

730 ms

port-infrastructure.jpg

port-infrastructure.jpg

634 ms

cement.jpg

cement.jpg

729 ms

agriculture.jpg

agriculture.jpg

729 ms

ApronFeeder.jpg

ApronFeeder.jpg

549 ms

BeltFeederCropped.jpg

BeltFeederCropped.jpg

629 ms

Conveyors.jpg

Conveyors.jpg

730 ms

screening.jpg

screening.jpg

731 ms

polyfill.js

polyfill.js

4 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

14 ms

bootstrap.min.js

bootstrap.min.js

17 ms

owl.carousel.min.js

owl.carousel.min.js

729 ms

myScript.js

myScript.js

787 ms

shadowbox.css

shadowbox.css

787 ms

shadowbox.js

shadowbox.js

787 ms

gallery.js

gallery.js

787 ms

IEM-Contacts.jpg

IEM-Contacts.jpg

807 ms

work-in-progress.jpg

work-in-progress.jpg

808 ms

drawing1.jpg

drawing1.jpg

863 ms

drawing3.png

drawing3.png

864 ms

drawing2.png

drawing2.png

864 ms

quality%20equipment-1-min.jpg

quality%20equipment-1-min.jpg

865 ms

quality%20equipment-2-min.jpg

quality%20equipment-2-min.jpg

866 ms

quality%20equipment-3-min.jpg

quality%20equipment-3-min.jpg

868 ms

quality%20equipment-4-min.jpg

quality%20equipment-4-min.jpg

945 ms

quality%20equipment-5-min.jpg

quality%20equipment-5-min.jpg

943 ms

quality%20equipment-6-min.jpg

quality%20equipment-6-min.jpg

944 ms

quality%20equipment-7-min.jpg

quality%20equipment-7-min.jpg

945 ms

quality%20equipment-8-min.jpg

quality%20equipment-8-min.jpg

946 ms

css

css

32 ms

social-medias.jpg

social-medias.jpg

274 ms

design-built-solutions1.jpg

design-built-solutions1.jpg

349 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

79 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

80 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

95 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

101 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

102 ms

Accessibility Review

iem.ca accessibility score

79

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

Buttons do not have an accessible name

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iem.ca SEO score

90

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

High

Tap targets are not sized appropriately

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

iem.ca

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