2.8 sec in total
29 ms
2.4 sec
424 ms
Visit smoketokes.ca now to see the best up-to-date Smoke Tokes content and also check out these interesting facts you probably never knew about smoketokes.ca
Visit smoketokes.caWe analyzed Smoketokes.ca page load time and found that the first response time was 29 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
smoketokes.ca performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value14.6 s
0/100
25%
Value5.2 s
61/100
10%
Value260 ms
83/100
30%
Value0.868
4/100
15%
Value13.1 s
12/100
10%
29 ms
36 ms
859 ms
200 ms
190 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 39% of them (32 requests) were addressed to the original Smoketokes.ca, 38% (31 requests) were made to Apanel.mcidistro.com and 10% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Apanel.mcidistro.com.
Page size can be reduced by 302.9 kB (5%)
6.6 MB
6.3 MB
In fact, the total size of Smoketokes.ca main page is 6.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. 65% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 120.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 120.5 kB or 80% of the original size.
Potential reduce by 156.3 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. Smoke Tokes images are well optimized though.
Potential reduce by 25.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. This website has mostly compressed JavaScripts.
Potential reduce by 857 B
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. Smoketokes.ca has all CSS files already compressed.
Number of requests can be reduced by 28 (38%)
73
45
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smoke Tokes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
smoketokes.ca
29 ms
smoketokes.ca
36 ms
www.smoketokes.ca
859 ms
jquery-2.1.1.min.js
200 ms
bootstrap.min.css
190 ms
bootstrap.min.js
156 ms
font-awesome.min.css
150 ms
css
30 ms
stylesheet.css
179 ms
toastr.min.css
173 ms
custom.js
292 ms
swiper.min.css
293 ms
opencart.css
318 ms
swiper.jquery.js
313 ms
owl.carousel.css
328 ms
owl.theme.css
332 ms
owl.carousel.min.js
433 ms
magnific-popup.css
438 ms
jquery.magnific-popup.min.js
456 ms
jquery.lazy.min.js
448 ms
common.js
469 ms
toastr.min.js
468 ms
js
65 ms
api.js
35 ms
2196.jpg
209 ms
Footer_MapleGlass.png
411 ms
Footer_SpiderGlass.png
435 ms
Footer_Canada420.png
436 ms
Footer_CrownGlass.png
435 ms
Footer_Maze.png
362 ms
Footer_Dagger.png
360 ms
Footer_Bosk.png
436 ms
2193.jpg
336 ms
2188.jpg
380 ms
2181.jpg
392 ms
2178.jpg
382 ms
82.jpg
377 ms
73.jpg
372 ms
205.jpg
476 ms
4393.jpg
508 ms
6616.jpg
502 ms
4411.jpg
519 ms
4474.jpg
526 ms
101.jpg
523 ms
206.jpg
608 ms
207.jpg
632 ms
195.jpg
643 ms
107.jpg
639 ms
3290.jpg
656 ms
93.jpg
657 ms
210.jpg
754 ms
209.jpg
771 ms
74.jpg
770 ms
3244.jpg
777 ms
152.jpg
779 ms
3361.jpg
793 ms
3298.jpg
894 ms
162.jpg
892 ms
3312.jpg
910 ms
129.jpg
916 ms
4392.jpg
919 ms
6628.jpg
921 ms
smoketokes_logo.png
145 ms
icon.png
145 ms
location.png
146 ms
phone.png
144 ms
email.png
144 ms
Poppins-Regular.ttf
14 ms
fontawesome-webfont3e6e.woff
48 ms
Poppins-Medium.ttf
49 ms
Poppins-SemiBold.ttf
25 ms
fontawesome-webfont3e6e.ttf
24 ms
fontawesome-webfont3e6e.svg
38 ms
default
213 ms
recaptcha__en.js
60 ms
twk-event-polyfill.js
95 ms
twk-main.js
24 ms
twk-vendor.js
18 ms
twk-chunk-vendors.js
23 ms
twk-chunk-common.js
34 ms
twk-runtime.js
24 ms
twk-app.js
34 ms
smoketokes.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
Image elements do not have [alt] attributes
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
smoketokes.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
smoketokes.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smoketokes.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 Smoketokes.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.
smoketokes.ca
Open Graph description is not detected on the main page of Smoke Tokes. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: