Tools & Wizards About Us
purepave.ca screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

purepave.ca

Permeable Pavers Toronto | Permeable Pavement Leader in Canada

Page Load Speed

12.4 sec in total

First Response

38 ms

Resources Loaded

12.2 sec

Page Rendered

77 ms

purepave.ca screenshot

About Website

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

Purepave Permeable Pavers Toronto are engineered for Canadian winters. Funded by the NRC, our permeable pavement are scientifically tested.

Visit purepave.ca

Key Findings

We analyzed Purepave.ca page load time and found that the first response time was 38 ms and then it took 12.3 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

purepave.ca performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value6,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.256

48/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

purepave.ca

38 ms

www.purepave.com

1708 ms

minified.js

57 ms

focus-within-polyfill.js

50 ms

polyfill.min.js

56 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Purepave.ca, 43% (26 requests) were made to Static.wixstatic.com and 23% (14 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (10.3 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 817.9 kB (61%)

Content Size

1.3 MB

After Optimization

512.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Purepave.ca main page is 1.3 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. 40% of websites need less resources to load. HTML takes 932.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 767.3 kB

  • Original 932.5 kB
  • After minification 930.6 kB
  • After compression 165.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 767.3 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 2.4 kB

  • Original 61.9 kB
  • After minification 59.5 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. Purepave images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 48.2 kB

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

Requests Breakdown

Number of requests can be reduced by 15 (32%)

Requests Now

47

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purepave.ca

purepave.ca

38 ms

www.purepave.com

www.purepave.com

1708 ms

minified.js

minified.js

57 ms

focus-within-polyfill.js

focus-within-polyfill.js

50 ms

polyfill.min.js

polyfill.min.js

56 ms

js

js

196 ms

8875.e26292eb.bundle.min.js

8875.e26292eb.bundle.min.js

32 ms

thunderbolt-commons.b7a35b00.bundle.min.js

thunderbolt-commons.b7a35b00.bundle.min.js

163 ms

main.d98de0fd.bundle.min.js

main.d98de0fd.bundle.min.js

164 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

159 ms

lodash.min.js

lodash.min.js

163 ms

react.production.min.js

react.production.min.js

159 ms

react-dom.production.min.js

react-dom.production.min.js

215 ms

browser-deprecation.bundle.es5.js

browser-deprecation.bundle.es5.js

228 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

228 ms

PurePave-logo-teal-grey-website-header.png

PurePave-logo-teal-grey-website-header.png

2851 ms

bundle.min.js

bundle.min.js

231 ms

PurePave-logo-teal-grey-website-header_e.png

PurePave-logo-teal-grey-website-header_e.png

2949 ms

bdecd1_6b7b6c6a56624f428561f707c2e57880~mv2.jpg

bdecd1_6b7b6c6a56624f428561f707c2e57880~mv2.jpg

2952 ms

nrc_edited.png

nrc_edited.png

2950 ms

canadian-construction-association-cca-logo-vector-1.png

canadian-construction-association-cca-logo-vector-1.png

4827 ms

Untitled-design-6_edited.png

Untitled-design-6_edited.png

3497 ms

1200px-Toronto_City_of_edited.png

1200px-Toronto_City_of_edited.png

2956 ms

RRO-ENG-1-removebg-preview_edited.png

RRO-ENG-1-removebg-preview_edited.png

6864 ms

1712242553_edited.png

1712242553_edited.png

3487 ms

2560px-Logo_Montr%C3%A9al_edited.png

2560px-Logo_Montr%C3%A9al_edited.png

3119 ms

bdecd1_295a53a71dec4d6888ad1f43c19b698f~mv2.png

bdecd1_295a53a71dec4d6888ad1f43c19b698f~mv2.png

5407 ms

Screenshot%202024-05-05%20at%206_edited.jpg

Screenshot%202024-05-05%20at%206_edited.jpg

3363 ms

Screenshot%202024-05-05%20at%206_50_edited.jpg

Screenshot%202024-05-05%20at%206_50_edited.jpg

3594 ms

Screenshot%202024-05-05%20at%206_edited.jpg

Screenshot%202024-05-05%20at%206_edited.jpg

6967 ms

Screenshot%202024-05-05%20at%206_50_edited.jpg

Screenshot%202024-05-05%20at%206_50_edited.jpg

6936 ms

Screenshot%202024-05-05%20at%206_edited.jpg

Screenshot%202024-05-05%20at%206_edited.jpg

3749 ms

Screenshot%202024-05-05%20at%206_50_edited.jpg

Screenshot%202024-05-05%20at%206_50_edited.jpg

6509 ms

Screenshot%202024-05-05%20at%206_edited.jpg

Screenshot%202024-05-05%20at%206_edited.jpg

5100 ms

Screenshot%202024-05-05%20at%206_50_edited.jpg

Screenshot%202024-05-05%20at%206_50_edited.jpg

6521 ms

GreenMarble-Walkingonly_edited.jpg

GreenMarble-Walkingonly_edited.jpg

5597 ms

BrownMarble-walkingonly_edited.png

BrownMarble-walkingonly_edited.png

5883 ms

BlackGranite-Glow_edited.jpg

BlackGranite-Glow_edited.jpg

6164 ms

GreyMarble-walkingonly_edited.jpg

GreyMarble-walkingonly_edited.jpg

7623 ms

IMG_5986_edited.jpg

IMG_5986_edited.jpg

6701 ms

Screenshot%202024-08-13%20at%206_15_edited.jpg

Screenshot%202024-08-13%20at%206_15_edited.jpg

10314 ms

IMG_9478E4E45B4E-1_edited_edited.jpg

IMG_9478E4E45B4E-1_edited_edited.jpg

6911 ms

js

js

167 ms

analytics.js

analytics.js

271 ms

210 ms

205 ms

205 ms

204 ms

200 ms

199 ms

236 ms

237 ms

228 ms

231 ms

231 ms

225 ms

collect

collect

22 ms

deprecation-en.v5.html

deprecation-en.v5.html

9 ms

bolt-performance

bolt-performance

28 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

9 ms

Accessibility Review

purepave.ca accessibility score

90

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

Links do not have a discernible name

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.

Best Practices

purepave.ca best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

purepave.ca SEO score

92

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

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

purepave.ca

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