6.3 sec in total
979 ms
4.3 sec
1 sec
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.caWe analyzed Purepave.ca page load time and found that the first response time was 979 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
purepave.ca performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value14.4 s
0/100
25%
Value14.4 s
1/100
10%
Value1,290 ms
18/100
30%
Value0.023
100/100
15%
Value22.5 s
1/100
10%
979 ms
71 ms
116 ms
108 ms
196 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 67% of them (70 requests) were addressed to the original Purepave.ca, 10% (10 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Purepave.ca.
Page size can be reduced by 295.7 kB (7%)
4.2 MB
3.9 MB
In fact, the total size of Purepave.ca main page is 4.2 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. 85% 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 117.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 117.2 kB or 83% of the original size.
Potential reduce by 98.0 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.
Potential reduce by 57.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 57.4 kB or 19% of the original size.
Potential reduce by 23.1 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. Purepave.ca has all CSS files already compressed.
Number of requests can be reduced by 57 (65%)
88
31
The browser has sent 88 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 35 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
purepave.ca
979 ms
gtm.js
71 ms
js
116 ms
style.min.css
108 ms
blocks.style.build.css
196 ms
styles.css
234 ms
style.css
246 ms
wpnw-public.css
234 ms
css
30 ms
font-awesome.min.css
241 ms
grid-system.css
234 ms
style.css
270 ms
element-testimonial.css
253 ms
magnific.css
254 ms
css
39 ms
responsive.css
311 ms
flickity.css
254 ms
skin-material.css
260 ms
widget-nectar-posts.css
308 ms
js_composer.min.css
352 ms
salient-dynamic-styles.css
359 ms
css
14 ms
frontend-gtag.min.js
278 ms
jquery.min.js
281 ms
jquery-migrate.min.js
312 ms
js
66 ms
8034391.js
151 ms
css
59 ms
iconsmind.css
317 ms
animate.min.css
471 ms
css
58 ms
mpp-frontend.js
473 ms
index.js
473 ms
index.js
473 ms
20426005.js
99 ms
salient-social.js
475 ms
jquery.easing.js
473 ms
jquery.mousewheel.js
576 ms
priority.js
582 ms
transit.js
582 ms
waypoints.js
583 ms
imagesLoaded.min.js
581 ms
hoverintent.js
581 ms
magnific.js
960 ms
touchswipe.min.js
959 ms
caroufredsel.min.js
964 ms
flickity.min.js
965 ms
js
51 ms
js
90 ms
superfish.js
914 ms
init.js
969 ms
js_composer_front.min.js
952 ms
analytics.js
277 ms
js
236 ms
hotjar-2254685.js
611 ms
PurePave-logo-teal-grey-website-header.png
777 ms
PurePave-logo-white-webiste-2.png
757 ms
ismail-addar-PQYaFb9Z-UI-unsplash.jpg
1362 ms
iphone-hor.png
1431 ms
1200px-Toronto_City_of.svg_.png
1430 ms
Unknown.png
1481 ms
city-of-ottawa-logo-vector.png
1480 ms
logo-jaguar-b5b95da0dbe970581680b12f0936b540.png
1430 ms
NRC.png
1583 ms
Screen-Shot-2021-08-05-at-10.21.01-AM.png
1548 ms
DreamPave-logo-colour.png
1588 ms
Ville-de-Montreal_logo-1-690x219-1.jpg
1548 ms
image.png
1640 ms
669 ms
salient-dynamic-styles.css
1488 ms
Screen-Shot-2021-06-02-at-1.14.49-PM.png
1705 ms
Screen-Shot-2020-07-14-at-1.02.10-PM.png
1895 ms
Screen-Shot-2020-10-15-at-9.34.49-AM-300x266.png
1583 ms
Geri-2-300x162.jpg
1534 ms
5-aspen-after-1-300x228.jpg
1536 ms
52-Fernwood-300x250.jpg
1583 ms
Driveway4-225x300.jpg
1583 ms
2-Hiawatha-Close-Up-300x249.jpg
1588 ms
S6uyw4BMUTPHjx4wWyWtFCc.ttf
398 ms
S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf
478 ms
S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf
1141 ms
S6u8w4BMUTPHjxsAXC-vNiXg7Q.ttf
1141 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iqzbXWjQeQ.ttf
1140 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iqzbXWjQeQ.ttf
1141 ms
icomoon.woff
1521 ms
invitebox.js
368 ms
loader.js
1162 ms
fontawesome-webfont.svg
1405 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf
881 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf
881 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf
941 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVcUwaEQXjM.ttf
942 ms
collect
195 ms
collectedforms.js
968 ms
banner.js
1001 ms
8034391.js
982 ms
iconsmind.ttf
1617 ms
modules.a4fd7e5489291affcf56.js
935 ms
photo-1528892952291-009c663ce843
803 ms
photo-1614786269829-d24616faf56d
243 ms
Screen-Shot-2020-07-15-at-12.56.57-PM.png
584 ms
Screen-Shot-2020-11-19-at-10.34.16-AM-1.png
619 ms
PHOTO-2020-08-05-17-02-05-3.jpg
582 ms
Chelsea-1.jpg
670 ms
fontawesome-webfont.woff
54 ms
purepave.ca accessibility score
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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
purepave.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
purepave.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
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: