7.5 sec in total
606 ms
4.7 sec
2.1 sec
Visit ignitebarrie.ca now to see the best up-to-date Ignite Barrie content and also check out these interesting facts you probably never knew about ignitebarrie.ca
Shop for best cannabis and smoking accessories at Ignite Barrie. Get the best selection of bongs, pipes, vaporizers, smoking & dab accessories
Visit ignitebarrie.caWe analyzed Ignitebarrie.ca page load time and found that the first response time was 606 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ignitebarrie.ca performance score
name
value
score
weighting
Value12.6 s
0/100
10%
Value21.8 s
0/100
25%
Value38.3 s
0/100
10%
Value35,660 ms
0/100
30%
Value0.152
75/100
15%
Value53.8 s
0/100
10%
606 ms
159 ms
331 ms
240 ms
323 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 69% of them (95 requests) were addressed to the original Ignitebarrie.ca, 23% (32 requests) were made to C0.wp.com and 1% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ignitebarrie.ca.
Page size can be reduced by 290.7 kB (24%)
1.2 MB
945.5 kB
In fact, the total size of Ignitebarrie.ca main page is 1.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. Only a small number of websites need less resources to load. CSS take 401.8 kB which makes up the majority of the site volume.
Potential reduce by 261.5 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 261.5 kB or 87% of the original size.
Potential reduce by 13.9 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. Ignite Barrie images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 10.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. Ignitebarrie.ca has all CSS files already compressed.
Number of requests can be reduced by 123 (97%)
127
4
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ignite Barrie. 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 55 to 1 for CSS and as a result speed up the page load time.
ignitebarrie.ca
606 ms
wp-emoji-release.min.js
159 ms
style.css
331 ms
style.min.css
240 ms
mediaelementplayer-legacy.min.css
323 ms
wp-mediaelement.min.css
323 ms
wc-blocks-vendors-style.css
320 ms
wc-blocks-style.css
411 ms
frontend.css
549 ms
badges.css
477 ms
index.css
564 ms
index.css
650 ms
frontend.css
654 ms
owl.carousel.min.css
669 ms
animate.css
687 ms
magnific-popup.css
677 ms
woocommerce-mailchimp-newsletter.css
705 ms
woocommerce-layout.css
403 ms
woocommerce.css
492 ms
wt-smart-coupon-public.css
738 ms
dashicons.min.css
497 ms
xoo-wsc-public.css
756 ms
style.min.css
723 ms
style.css
805 ms
all.min.css
758 ms
v4-shims.min.css
764 ms
public.css
868 ms
jet-menu-general.css
935 ms
style.css
936 ms
sv-wc-payment-gateway-payment-form.min.css
949 ms
jet-elements.css
963 ms
jet-elements-skin.css
929 ms
elementor-icons.min.css
994 ms
frontend.min.css
1156 ms
font-awesome.min.css
996 ms
frontend.min.css
1238 ms
post-10233.css
1027 ms
frontend.min.css
1043 ms
all.min.css
1220 ms
v4-shims.min.css
1190 ms
flatpickr.min.css
1354 ms
she-header-style.css
1360 ms
post-38599.css
1362 ms
general.min.css
1407 ms
css
497 ms
jetpack.css
427 ms
jquery.min.js
425 ms
jquery-migrate.min.js
495 ms
js
590 ms
s-202241.js
534 ms
jquery.blockUI.min.js
461 ms
add-to-cart.min.js
502 ms
js.cookie.min.js
499 ms
woocommerce.min.js
501 ms
cart-fragments.min.js
501 ms
regenerator-runtime.min.js
507 ms
wp-polyfill.min.js
507 ms
hooks.min.js
519 ms
i18n.min.js
517 ms
wc-blocks-google-analytics.js
518 ms
underscore.min.js
518 ms
jquery.payment.min.js
530 ms
imagesloaded.min.js
522 ms
core.min.js
523 ms
wp-util.min.js
522 ms
jquery.zoom.min.js
528 ms
jquery.flexslider.min.js
528 ms
add-to-cart-variation.min.js
533 ms
single-product.min.js
532 ms
e-202241.js
498 ms
api.js
541 ms
post-11311.css
1294 ms
post-9338.css
1367 ms
fontawesome.min.css
1143 ms
solid.min.css
1006 ms
regular.min.css
944 ms
brands.min.css
927 ms
woocommerce-smallscreen.css
83 ms
post-11361.css
847 ms
post-38913.css
1053 ms
animations.min.css
1039 ms
rs6.css
1024 ms
frontend.js
1020 ms
owl.carousel.min.js
1024 ms
wt-smart-coupon-public.js
1022 ms
utils.min.js
1302 ms
she-header.js
1315 ms
v4-shims.min.js
1290 ms
script.js
1483 ms
frontend.js
1467 ms
colcade.js
1415 ms
rbtools.min.js
1608 ms
rs6.min.js
1597 ms
jquery.exitintent.min.js
1575 ms
jquery.magnific-popup.min.js
1527 ms
wcmnd-custom.js
1524 ms
mailchimp-woocommerce-public.min.js
1501 ms
wc-quick-view.js
1498 ms
frontend.min.js
1384 ms
vue.min.js
1382 ms
jet-menu-public-scripts.js
1308 ms
sv-wc-payment-gateway-payment-form.min.js
1293 ms
smush-lazy-load.min.js
1185 ms
general.min.js
1176 ms
xoo-wsc-public.js
1174 ms
search.min.js
1170 ms
enquire.min.js
1166 ms
savvior.min.js
1129 ms
jquery.smartmenus.min.js
1101 ms
url-polyfill.min.js
1088 ms
webpack-pro.runtime.min.js
1088 ms
webpack.runtime.min.js
1082 ms
frontend-modules.min.js
1081 ms
frontend.min.js
875 ms
waypoints.min.js
866 ms
frontend.min.js
869 ms
elements-handlers.min.js
866 ms
jet-elements.min.js
866 ms
widgets-scripts.js
842 ms
frontend.min.js
758 ms
flatpickr.min.js
681 ms
analytics.js
630 ms
a9999057edf1abaee264341f6.js
704 ms
b05f5155-ae93-414a-88cc-87c389c0fa02.png
784 ms
page-title.jpg
776 ms
fa-solid-900.woff
353 ms
fa-solid-900.woff
348 ms
fa-regular-400.woff
348 ms
fa-regular-400.woff
348 ms
jupiterx.woff
350 ms
star.woff
52 ms
fa-brands-400.woff
350 ms
fa-brands-400.woff
352 ms
ec.js
24 ms
7dee0dcae788fda52770a3670.js
294 ms
Woo-Side-Cart.ttf
161 ms
recaptcha__en.js
279 ms
ignitebarrie.ca accessibility score
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.
ignitebarrie.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ignitebarrie.ca SEO score
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 Ignitebarrie.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 Ignitebarrie.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.
ignitebarrie.ca
Open Graph data is detected on the main page of Ignite Barrie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: