Tools & Wizards About Us
fencescape.ca screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

fencescape.ca

Premium Fence Contractor & Retailer | FenceScape Ottawa

Page Load Speed

2.5 sec in total

First Response

94 ms

Resources Loaded

1.5 sec

Page Rendered

992 ms

fencescape.ca screenshot

About Website

Click here to check amazing Fence Scape content. Otherwise, check out these important facts you probably never knew about fencescape.ca

FenceScape is Ottawa’s Trusted Contractor and Retailer for All Your Fence Design & Installation Needs. From Wood & PVC to Hybrid Fences, We’ve Got You Covered.

Visit fencescape.ca

Key Findings

We analyzed Fencescape.ca page load time and found that the first response time was 94 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fencescape.ca performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

fencescape.ca

94 ms

fencescape.ca

208 ms

gtm.js

86 ms

owl.carousel.min.css

71 ms

owl.theme.default.min.css

110 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 82% of them (118 requests) were addressed to the original Fencescape.ca, 8% (12 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (523 ms) belongs to the original domain Fencescape.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 398.2 kB (15%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fencescape.ca main page is 2.7 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 257.4 kB

  • Original 311.3 kB
  • After minification 304.5 kB
  • After compression 53.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 257.4 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 47.6 kB

  • Original 1.8 MB
  • After minification 1.7 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. Fence Scape images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 65.7 kB

  • Original 460.9 kB
  • After minification 460.9 kB
  • After compression 395.3 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.7 kB or 14% of the original size.

CSS Optimization

-19%

Potential reduce by 27.5 kB

  • Original 147.8 kB
  • After minification 147.8 kB
  • After compression 120.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. Fencescape.ca needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

125

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fencescape.ca

fencescape.ca

94 ms

fencescape.ca

fencescape.ca

208 ms

gtm.js

gtm.js

86 ms

owl.carousel.min.css

owl.carousel.min.css

71 ms

owl.theme.default.min.css

owl.theme.default.min.css

110 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

50 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

116 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

117 ms

woocommerce-layout.css

woocommerce-layout.css

117 ms

woocommerce.css

woocommerce.css

119 ms

style.min.css

style.min.css

121 ms

frontend.css

frontend.css

140 ms

style.css

style.css

142 ms

style.min.css

style.min.css

143 ms

theme.min.css

theme.min.css

146 ms

elementor-icons.min.css

elementor-icons.min.css

143 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

165 ms

swiper.min.css

swiper.min.css

150 ms

post-10.css

post-10.css

155 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

218 ms

post-2.css

post-2.css

163 ms

post-12.css

post-12.css

162 ms

post-65.css

post-65.css

178 ms

formreset.min.css

formreset.min.css

184 ms

formsmain.min.css

formsmain.min.css

223 ms

readyclass.min.css

readyclass.min.css

228 ms

browsers.min.css

browsers.min.css

230 ms

css

css

47 ms

fontawesome.min.css

fontawesome.min.css

236 ms

regular.min.css

regular.min.css

231 ms

solid.min.css

solid.min.css

231 ms

brands.min.css

brands.min.css

232 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

233 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

234 ms

wp-polyfill.min.js

wp-polyfill.min.js

300 ms

hooks.min.js

hooks.min.js

248 ms

w.js

w.js

33 ms

language-cookie.js

language-cookie.js

252 ms

jquery.min.js

jquery.min.js

283 ms

jquery-migrate.min.js

jquery-migrate.min.js

257 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

256 ms

s-202410.js

s-202410.js

41 ms

swiper-bundle.min.js

swiper-bundle.min.js

31 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

15 ms

e-202410.js

e-202410.js

13 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

248 ms

swiper-bundle.min.js

swiper-bundle.min.js

13 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

219 ms

widget-carousel.min.css

widget-carousel.min.css

177 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

180 ms

wc-blocks.css

wc-blocks.css

232 ms

post-4583.css

post-4583.css

229 ms

animations.min.css

animations.min.css

229 ms

js

js

51 ms

add-to-cart.min.js

add-to-cart.min.js

210 ms

js.cookie.min.js

js.cookie.min.js

209 ms

woocommerce.min.js

woocommerce.min.js

209 ms

blog-custom.js

blog-custom.js

210 ms

jquery.json.min.js

jquery.json.min.js

211 ms

gravityforms.min.js

gravityforms.min.js

208 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

204 ms

owl.carousel.js

owl.carousel.js

216 ms

sourcebuster.min.js

sourcebuster.min.js

209 ms

order-attribution.min.js

order-attribution.min.js

311 ms

react.min.js

react.min.js

308 ms

deprecated.min.js

deprecated.min.js

297 ms

dom.min.js

dom.min.js

258 ms

react-dom.min.js

react-dom.min.js

310 ms

escape-html.min.js

escape-html.min.js

246 ms

element.min.js

element.min.js

305 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

304 ms

i18n.min.js

i18n.min.js

304 ms

keycodes.min.js

keycodes.min.js

302 ms

priority-queue.min.js

priority-queue.min.js

302 ms

compose.min.js

compose.min.js

379 ms

private-apis.min.js

private-apis.min.js

367 ms

redux-routine.min.js

redux-routine.min.js

367 ms

data.min.js

data.min.js

365 ms

lodash.min.js

lodash.min.js

362 ms

wc-blocks-registry.js

wc-blocks-registry.js

356 ms

url.min.js

url.min.js

501 ms

api-fetch.min.js

api-fetch.min.js

478 ms

wc-settings.js

wc-settings.js

479 ms

data-controls.min.js

data-controls.min.js

474 ms

html-entities.min.js

html-entities.min.js

475 ms

notices.min.js

notices.min.js

471 ms

g.gif

g.gif

43 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

464 ms

wc-blocks-data.js

wc-blocks-data.js

464 ms

dom-ready.min.js

dom-ready.min.js

460 ms

a11y.min.js

a11y.min.js

459 ms

primitives.min.js

primitives.min.js

463 ms

warning.min.js

warning.min.js

461 ms

blocks-components.js

blocks-components.js

523 ms

blocks-checkout.js

blocks-checkout.js

520 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

516 ms

css2

css2

15 ms

frontend.js

frontend.js

503 ms

cart_widget.min.js

cart_widget.min.js

501 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

500 ms

imagesloaded.min.js

imagesloaded.min.js

503 ms

fbevents.js

fbevents.js

159 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

400 ms

webpack.runtime.min.js

webpack.runtime.min.js

400 ms

frontend-modules.min.js

frontend-modules.min.js

401 ms

frontend.min.js

frontend.min.js

461 ms

5aU19_a8oxmIfJpbERySixhc9V0.woff

5aU19_a8oxmIfJpbERySixhc9V0.woff

138 ms

5aU19_a8oxmIfJpbERKSixhc9V11uQ.woff

5aU19_a8oxmIfJpbERKSixhc9V11uQ.woff

280 ms

5aU19_a8oxmIfJpbER2Sixhc9V11uQ.woff

5aU19_a8oxmIfJpbER2Sixhc9V11uQ.woff

392 ms

5aU69_a8oxmIdGl4AjGwgDI.woff

5aU69_a8oxmIdGl4AjGwgDI.woff

321 ms

5aU69_a8oxmIdGd4AjGwgDJm_A.woff

5aU69_a8oxmIdGd4AjGwgDJm_A.woff

319 ms

5aU69_a8oxmIdGh4AjGwgDJm_A.woff

5aU69_a8oxmIdGh4AjGwgDJm_A.woff

322 ms

5aU19_a8oxmIfMJaERySixhc9V0.woff

5aU19_a8oxmIfMJaERySixhc9V0.woff

320 ms

5aU19_a8oxmIfMJaERKSixhc9V11uQ.woff

5aU19_a8oxmIfMJaERKSixhc9V11uQ.woff

388 ms

5aU19_a8oxmIfMJaER2Sixhc9V11uQ.woff

5aU19_a8oxmIfMJaER2Sixhc9V11uQ.woff

324 ms

5aU19_a8oxmIfNJdERySixhc9V0.woff

5aU19_a8oxmIfNJdERySixhc9V0.woff

322 ms

5aU19_a8oxmIfNJdERKSixhc9V11uQ.woff

5aU19_a8oxmIfNJdERKSixhc9V11uQ.woff

323 ms

5aU19_a8oxmIfNJdER2Sixhc9V11uQ.woff

5aU19_a8oxmIfNJdER2Sixhc9V11uQ.woff

387 ms

waypoints.min.js

waypoints.min.js

455 ms

core.min.js

core.min.js

402 ms

frontend.min.js

frontend.min.js

403 ms

elements-handlers.min.js

elements-handlers.min.js

401 ms

jquery.sticky.min.js

jquery.sticky.min.js

402 ms

fencescape-logo.svg

fencescape-logo.svg

403 ms

en.png

en.png

405 ms

eicons.woff

eicons.woff

451 ms

fa-regular-400.woff

fa-regular-400.woff

359 ms

fa-solid-900.woff

fa-solid-900.woff

360 ms

fr.png

fr.png

328 ms

Shape-5.png

Shape-5.png

358 ms

logo-copy-2.png

logo-copy-2.png

358 ms

fa-brands-400.woff

fa-brands-400.woff

286 ms

fenscape-video-fallback.jpg

fenscape-video-fallback.jpg

357 ms

Image_1.jpeg

Image_1.jpeg

354 ms

Image_4.jpeg

Image_4.jpeg

354 ms

Image_2.jpeg

Image_2.jpeg

301 ms

Image_3.jpeg

Image_3.jpeg

320 ms

Group-4.svg

Group-4.svg

309 ms

shutterstock_380917492-min-1024x542.png

shutterstock_380917492-min-1024x542.png

333 ms

fencescape-logo-white.svg

fencescape-logo-white.svg

310 ms

Group-644.svg

Group-644.svg

318 ms

shop_image-min.jpg

shop_image-min.jpg

330 ms

g.gif

g.gif

12 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

33 ms

Accessibility Review

fencescape.ca accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Links do not have a discernible name

Best Practices

fencescape.ca 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

fencescape.ca SEO score

78

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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

fencescape.ca

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