Tools & Wizards About Us
armordecking.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

armordecking.com

Armor Decking - All Your Decking Needs in Surrey, BC

Page Load Speed

1 sec in total

First Response

66 ms

Resources Loaded

626 ms

Page Rendered

341 ms

armordecking.com screenshot

About Website

Welcome to armordecking.com homepage info - get ready to check Armor Decking best content right away, or after learning these important things about armordecking.com

Armor Decking offers designer vinyl decking at affordable prices. Located in Surrey, BC, Canada, contact us for all your decking needs.

Visit armordecking.com

Key Findings

We analyzed Armordecking.com page load time and found that the first response time was 66 ms and then it took 967 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

armordecking.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

armordecking.com

66 ms

www.armordecking.com

64 ms

public.css

7 ms

style.min.css

8 ms

theme.min.css

16 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 68% of them (40 requests) were addressed to the original Armordecking.com, 17% (10 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Cdn.actionlocalwebsites.com. The less responsive or slowest element that took the longest time to load (368 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.9 kB (4%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Armordecking.com main page is 1.6 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 54.8 kB

  • Original 67.4 kB
  • After minification 65.3 kB
  • After compression 12.6 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 54.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 226 B

  • Original 1.3 MB
  • After minification 1.3 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. Armor Decking images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 11.1 kB

  • Original 125.7 kB
  • After minification 125.4 kB
  • After compression 114.6 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

-1%

Potential reduce by 730 B

  • Original 89.0 kB
  • After minification 88.9 kB
  • After compression 88.2 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. Armordecking.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (83%)

Requests Now

46

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

armordecking.com

armordecking.com

66 ms

www.armordecking.com

www.armordecking.com

64 ms

public.css

public.css

7 ms

style.min.css

style.min.css

8 ms

theme.min.css

theme.min.css

16 ms

header-footer.min.css

header-footer.min.css

18 ms

frontend.min.css

frontend.min.css

37 ms

post-3.css

post-3.css

15 ms

elementor-icons.min.css

elementor-icons.min.css

16 ms

swiper.min.css

swiper.min.css

40 ms

e-swiper.min.css

e-swiper.min.css

24 ms

frontend.min.css

frontend.min.css

25 ms

global.css

global.css

21 ms

post-8.css

post-8.css

25 ms

post-90.css

post-90.css

25 ms

post-95.css

post-95.css

38 ms

css

css

50 ms

fontawesome.min.css

fontawesome.min.css

40 ms

solid.min.css

solid.min.css

39 ms

jquery.min.js

jquery.min.js

40 ms

jquery-migrate.min.js

jquery-migrate.min.js

39 ms

public.js

public.js

43 ms

widget-icon-list.min.css

widget-icon-list.min.css

38 ms

widget-image.min.css

widget-image.min.css

42 ms

widget-heading.min.css

widget-heading.min.css

42 ms

widget-text-editor.min.css

widget-text-editor.min.css

43 ms

widget-spacer.min.css

widget-spacer.min.css

43 ms

widget-google_maps.min.css

widget-google_maps.min.css

42 ms

hello-frontend.min.js

hello-frontend.min.js

43 ms

jquery.sticky.min.js

jquery.sticky.min.js

43 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

42 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

44 ms

webpack.runtime.min.js

webpack.runtime.min.js

44 ms

frontend-modules.min.js

frontend-modules.min.js

43 ms

hooks.min.js

hooks.min.js

44 ms

i18n.min.js

i18n.min.js

44 ms

frontend.min.js

frontend.min.js

44 ms

core.min.js

core.min.js

44 ms

frontend.min.js

frontend.min.js

45 ms

elements-handlers.min.js

elements-handlers.min.js

44 ms

cropped-image-1.png

cropped-image-1.png

147 ms

wpwdya.js

wpwdya.js

101 ms

IMG_9215-1.jpg

IMG_9215-1.jpg

287 ms

IMG_9204-1.jpg

IMG_9204-1.jpg

193 ms

IMG_9214-1.jpg

IMG_9214-1.jpg

196 ms

IMG_9210-1.jpg

IMG_9210-1.jpg

338 ms

embed

embed

368 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

22 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWAosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWAosBO5Xk.ttf

27 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

34 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUyosBO5Xk.ttf

42 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyo8BO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyo8BO5Xk.ttf

43 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVspcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVspcBO5Xk.ttf

42 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

42 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUypcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUypcBO5Xk.ttf

44 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUbpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUbpcBO5Xk.ttf

42 ms

fa-solid-900.woff

fa-solid-900.woff

7 ms

8AtqGs-wOpGRTBq66LWdHLk.ttf

8AtqGs-wOpGRTBq66LWdHLk.ttf

43 ms

js

js

28 ms

Accessibility Review

armordecking.com accessibility score

100

Accessibility Issues

Best Practices

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

SEO Factors

armordecking.com SEO score

100

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

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

armordecking.com

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