Tools & Wizards About Us
niscocanada.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

niscocanada.com

Nisco Canada – Burlington Oakville Hamilton Commercial Leasing

Page Load Speed

16.8 sec in total

First Response

1.3 sec

Resources Loaded

15.2 sec

Page Rendered

300 ms

niscocanada.com screenshot

About Website

Welcome to niscocanada.com homepage info - get ready to check Nisco Canada best content right away, or after learning these important things about niscocanada.com

Visit niscocanada.com

Key Findings

We analyzed Niscocanada.com page load time and found that the first response time was 1.3 sec and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

niscocanada.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

niscocanada.com

1335 ms

wp-emoji-release.min.js

55 ms

style.min.css

94 ms

classic-themes.min.css

121 ms

styles.css

162 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 63% of them (57 requests) were addressed to the original Niscocanada.com, 36% (32 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Niscocanada.com.

Page Optimization Overview & Recommendations

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

Content Size

689.1 kB

After Optimization

610.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Niscocanada.com main page is 689.1 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. 75% 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 538.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 66.1 kB

  • Original 79.3 kB
  • After minification 77.5 kB
  • After compression 13.2 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 66.1 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 4.1 kB

  • Original 538.5 kB
  • After minification 534.4 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. Nisco Canada images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 2.3 kB

  • Original 16.7 kB
  • After minification 16.7 kB
  • After compression 14.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 2.3 kB or 14% of the original size.

CSS Optimization

-10%

Potential reduce by 5.7 kB

  • Original 54.6 kB
  • After minification 54.4 kB
  • After compression 48.9 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. Niscocanada.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (82%)

Requests Now

56

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

niscocanada.com

niscocanada.com

1335 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

55 ms

style.min.css

style.min.css

94 ms

classic-themes.min.css

classic-themes.min.css

121 ms

styles.css

styles.css

162 ms

style.min.css

style.min.css

206 ms

style.min.css

style.min.css

251 ms

theme.min.css

theme.min.css

279 ms

style.css

style.css

309 ms

frontend-lite.min.css

frontend-lite.min.css

347 ms

post-126.css

post-126.css

378 ms

elementor-icons.min.css

elementor-icons.min.css

412 ms

frontend-lite.min.css

frontend-lite.min.css

452 ms

global.css

global.css

503 ms

post-1117.css

post-1117.css

538 ms

all.min.css

all.min.css

578 ms

v4-shims.min.css

v4-shims.min.css

614 ms

post-440.css

post-440.css

800 ms

post-44.css

post-44.css

837 ms

style.css

style.css

866 ms

css

css

39 ms

fontawesome.min.css

fontawesome.min.css

920 ms

solid.min.css

solid.min.css

963 ms

brands.min.css

brands.min.css

991 ms

jquery.min.js

jquery.min.js

1034 ms

jquery-migrate.min.js

jquery-migrate.min.js

1065 ms

v4-shims.min.js

v4-shims.min.js

1093 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

1103 ms

animations.min.css

animations.min.css

1090 ms

index.js

index.js

1110 ms

index.js

index.js

1089 ms

hello-frontend.min.js

hello-frontend.min.js

1153 ms

scripts.js

scripts.js

1158 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1163 ms

elfsight-instagram-feed.js

elfsight-instagram-feed.js

1177 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1163 ms

webpack.runtime.min.js

webpack.runtime.min.js

1157 ms

frontend-modules.min.js

frontend-modules.min.js

1157 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1160 ms

wp-polyfill.min.js

wp-polyfill.min.js

1117 ms

hooks.min.js

hooks.min.js

1092 ms

i18n.min.js

i18n.min.js

1051 ms

frontend.min.js

frontend.min.js

1007 ms

waypoints.min.js

waypoints.min.js

1012 ms

core.min.js

core.min.js

984 ms

frontend.min.js

frontend.min.js

956 ms

elements-handlers.min.js

elements-handlers.min.js

914 ms

repeater.js

repeater.js

888 ms

jquery.sticky.min.js

jquery.sticky.min.js

853 ms

nisco-logo-300x80.png

nisco-logo-300x80.png

186 ms

header-1.jpg

header-1.jpg

186 ms

header-2v3.jpg

header-2v3.jpg

185 ms

header-3.jpg

header-3.jpg

175 ms

4-2.jpg

4-2.jpg

176 ms

header-5v2.jpg

header-5v2.jpg

199 ms

header-6.jpg

header-6.jpg

178 ms

header-7.jpg

header-7.jpg

211 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

56 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

85 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

86 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

86 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

84 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

84 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

84 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

87 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

85 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

44 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

43 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

44 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

48 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

48 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

49 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

49 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

50 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

50 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

50 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

51 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

53 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

52 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

52 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

51 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

51 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

53 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

56 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

57 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

57 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

56 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

57 ms

fa-brands-400.woff

fa-brands-400.woff

154 ms

Accessibility Review

niscocanada.com accessibility score

96

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

Links do not have a discernible name

Best Practices

niscocanada.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

niscocanada.com 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

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 Niscocanada.com 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 Niscocanada.com 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

niscocanada.com

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