Tools & Wizards About Us
oies.ca screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

oies.ca

Ottawa IAQ, Asbestos, Mold Air Testing and Designated Substances Testing - OIES

Page Load Speed

1.8 sec in total

First Response

131 ms

Resources Loaded

1.2 sec

Page Rendered

507 ms

oies.ca screenshot

About Website

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

Ottawa Certified Mold Air Testing, IAQ Assessments, Asbestos Testing, Asbestos Surveys, Type 3 Asbestos Air Clearance.

Visit oies.ca

Key Findings

We analyzed Oies.ca page load time and found that the first response time was 131 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

oies.ca performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

oies.ca

131 ms

oies.ca

218 ms

index.html

61 ms

css

52 ms

bootstrap.min.css

111 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Oies.ca, 14% (8 requests) were made to Embed.tawk.to and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (420 ms) belongs to the original domain Oies.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.0 kB (13%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 18.2 kB

  • Original 24.3 kB
  • After minification 19.6 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 4.7 kB, which is 19% 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 18.2 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 202 B

  • Original 1.2 MB
  • After minification 1.2 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. OIES images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 236.4 kB

  • Original 679.2 kB
  • After minification 647.5 kB
  • After compression 442.9 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 236.4 kB or 35% of the original size.

CSS Optimization

-7%

Potential reduce by 7.3 kB

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

Requests Breakdown

Number of requests can be reduced by 33 (73%)

Requests Now

45

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oies.ca

oies.ca

131 ms

oies.ca

oies.ca

218 ms

index.html

index.html

61 ms

css

css

52 ms

bootstrap.min.css

bootstrap.min.css

111 ms

all.min.css

all.min.css

161 ms

theme.css

theme.css

213 ms

theme-elements.css

theme-elements.css

222 ms

theme-blog.css

theme-blog.css

165 ms

theme-shop.css

theme-shop.css

158 ms

default.css

default.css

169 ms

custom.css

custom.css

222 ms

modernizr.min.js

modernizr.min.js

239 ms

js

js

96 ms

jquery.min.js

jquery.min.js

320 ms

jquery.appear.min.js

jquery.appear.min.js

317 ms

jquery.easing.min.js

jquery.easing.min.js

317 ms

jquery.cookie.min.js

jquery.cookie.min.js

318 ms

bootstrap.min.js

bootstrap.min.js

320 ms

common.min.js

common.min.js

318 ms

theme.js

theme.js

378 ms

api.js

api.js

50 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

36 ms

bootstrap.min.js

bootstrap.min.js

43 ms

validator.js

validator.js

356 ms

contact.js

contact.js

356 ms

theme.init.js

theme.init.js

393 ms

js

js

163 ms

js

js

148 ms

logoB.png

logoB.png

140 ms

family2.jpg

family2.jpg

420 ms

home_iaq-testing.jpg

home_iaq-testing.jpg

205 ms

home_assessments.jpg

home_assessments.jpg

271 ms

asbestos_vermiculite.jpg

asbestos_vermiculite.jpg

301 ms

services_iaq.jpg

services_iaq.jpg

204 ms

petri-dish.jpg

petri-dish.jpg

369 ms

oies-asbestos-testing.jpg

oies-asbestos-testing.jpg

369 ms

inspector.jpg

inspector.jpg

307 ms

certifications.png

certifications.png

325 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

79 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

80 ms

fa-regular-400.woff

fa-regular-400.woff

290 ms

fa-solid-900.woff

fa-solid-900.woff

301 ms

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD_.woff

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD_.woff

46 ms

recaptcha__en.js

recaptcha__en.js

79 ms

default

default

253 ms

twk-event-polyfill.js

twk-event-polyfill.js

81 ms

twk-main.js

twk-main.js

33 ms

twk-vendor.js

twk-vendor.js

15 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

23 ms

twk-chunk-common.js

twk-chunk-common.js

34 ms

twk-runtime.js

twk-runtime.js

32 ms

twk-app.js

twk-app.js

33 ms

Accessibility Review

oies.ca accessibility score

72

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oies.ca SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

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

oies.ca

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