Tools & Wizards About Us
eiw.ca screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

eiw.ca

Full Range of Accessories and Technical Services - Etobicoke Ironworks Limited

Page Load Speed

1.8 sec in total

First Response

151 ms

Resources Loaded

1.4 sec

Page Rendered

334 ms

eiw.ca screenshot

About Website

Welcome to eiw.ca homepage info - get ready to check Eiw best content right away, or after learning these important things about eiw.ca

We started as a miscellaneous ironwork company in the city of Etobicoke in 1955. Over the years the company grew and moved to our current location at the north end of Toronto (Weston), Canada. Structu...

Visit eiw.ca

Key Findings

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

Performance Metrics

eiw.ca performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

eiw.ca

151 ms

www.eiw.ca

555 ms

1b391e20-ab33-40a2-a7ee-de5d83ed7785.css

22 ms

custom-flex.css

54 ms

require.js

45 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Eiw.ca, 46% (34 requests) were made to D25bp99q88v7sv.cloudfront.net and 42% (31 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Eiw.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.2 kB (14%)

Content Size

873.6 kB

After Optimization

748.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eiw.ca main page is 873.6 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. 70% of websites need less resources to load. Images take 391.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 125.1 kB

  • Original 142.1 kB
  • After minification 140.6 kB
  • After compression 17.1 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 125.1 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 391.0 kB
  • After minification 391.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. Eiw images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 135 B

  • Original 215.9 kB
  • After minification 215.9 kB
  • After compression 215.7 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

-0%

Potential reduce by 20 B

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

Requests Breakdown

Number of requests can be reduced by 34 (85%)

Requests Now

40

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eiw.ca

eiw.ca

151 ms

www.eiw.ca

www.eiw.ca

555 ms

1b391e20-ab33-40a2-a7ee-de5d83ed7785.css

1b391e20-ab33-40a2-a7ee-de5d83ed7785.css

22 ms

custom-flex.css

custom-flex.css

54 ms

require.js

require.js

45 ms

app.js

app.js

48 ms

js

js

114 ms

8a16b4ca-19d9-4d6f-9a55-13f470674dd7_m.jpg

8a16b4ca-19d9-4d6f-9a55-13f470674dd7_m.jpg

45 ms

pin_it_button.png

pin_it_button.png

35 ms

c7c34ec8-aa6c-4437-b25e-7516649e7658.jpg

c7c34ec8-aa6c-4437-b25e-7516649e7658.jpg

64 ms

page.js

page.js

30 ms

kbx0azt.js

kbx0azt.js

144 ms

header.v1.js

header.v1.js

28 ms

jquery1102.js

jquery1102.js

27 ms

socialprofile.v1.js

socialprofile.v1.js

26 ms

flexcontainer.js

flexcontainer.js

26 ms

supersized.js

supersized.js

26 ms

kenburns.js

kenburns.js

34 ms

mediabackground.v1.js

mediabackground.v1.js

34 ms

image.v1.js

image.v1.js

33 ms

article.v1.js

article.v1.js

34 ms

buttonlink.v1.js

buttonlink.v1.js

29 ms

footer.v1.js

footer.v1.js

29 ms

utility.js

utility.js

15 ms

data.js

data.js

10 ms

jquery.svg-1.5.0.js

jquery.svg-1.5.0.js

9 ms

domReady.js

domReady.js

13 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

13 ms

lozad.js

lozad.js

9 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

17 ms

bootstrap.js

bootstrap.js

16 ms

jquery-ui-1.10.3.js

jquery-ui-1.10.3.js

28 ms

underscore-min.js

underscore-min.js

25 ms

modernizr-latest.js

modernizr-latest.js

23 ms

sdk.js

sdk.js

415 ms

sticky.min.js

sticky.min.js

19 ms

jquery.mousewheel.js

jquery.mousewheel.js

78 ms

backbone-min.js

backbone-min.js

74 ms

underscore.string.js

underscore.string.js

72 ms

mopro-social-icons.ttf

mopro-social-icons.ttf

315 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

316 ms

jquery.selectik.js

jquery.selectik.js

312 ms

d

d

97 ms

d

d

95 ms

d

d

92 ms

d

d

40 ms

d

d

46 ms

d

d

90 ms

d

d

46 ms

d

d

89 ms

d

d

90 ms

d

d

91 ms

d

d

90 ms

d

d

92 ms

d

d

93 ms

d

d

93 ms

d

d

92 ms

d

d

93 ms

d

d

94 ms

d

d

95 ms

d

d

95 ms

d

d

96 ms

d

d

96 ms

d

d

96 ms

d

d

94 ms

d

d

97 ms

d

d

99 ms

d

d

97 ms

d

d

97 ms

d

d

99 ms

d

d

98 ms

d

d

97 ms

pinit.js

pinit.js

28 ms

sdk.js

sdk.js

35 ms

Accessibility Review

eiw.ca accessibility score

75

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

eiw.ca SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eiw.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 Eiw.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

eiw.ca

Open Graph data is detected on the main page of Eiw. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: