Tools & Wizards About Us
smoketokes.ca screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 68

    SEO

    Google-friendlier than
    27% of websites

smoketokes.ca

Wholesale Bongs Suppliers Canada, Wholesale Smoking Accessories Suppliers, Canadian Bong Distributors - Smoke Tokes

Page Load Speed

4.9 sec in total

First Response

396 ms

Resources Loaded

3.1 sec

Page Rendered

1.4 sec

smoketokes.ca screenshot

About Website

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

Smoke Tokes carries wholesale smoking accessories including wholesale bongs, wholesale pipes, wholesale bubblers, wholesale grinders, wholesale dab rigs, and many more smoking goods at cheap prices.

Visit smoketokes.ca

Key Findings

We analyzed Smoketokes.ca page load time and found that the first response time was 396 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

smoketokes.ca performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value30.5 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value7,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.205

60/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

smoketokes.ca

396 ms

jquery-2.1.1.min.js

238 ms

bootstrap.min.css

250 ms

bootstrap.min.js

178 ms

font-awesome.min.css

212 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 33% of them (31 requests) were addressed to the original Smoketokes.ca, 47% (44 requests) were made to Allinone.maplecraft.ca and 14% (13 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Allinone.maplecraft.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 977.4 kB (11%)

Content Size

9.2 MB

After Optimization

8.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smoketokes.ca main page is 9.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 8.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 143.1 kB

  • Original 190.8 kB
  • After minification 189.0 kB
  • After compression 47.7 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 143.1 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 748.8 kB

  • Original 8.7 MB
  • After minification 7.9 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. Smoke Tokes images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 62.8 kB

  • Original 242.9 kB
  • After minification 212.8 kB
  • After compression 180.1 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 62.8 kB or 26% of the original size.

CSS Optimization

-33%

Potential reduce by 22.7 kB

  • Original 69.4 kB
  • After minification 69.4 kB
  • After compression 46.8 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. Smoketokes.ca needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (42%)

Requests Now

89

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 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 29 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

smoketokes.ca

smoketokes.ca

396 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

238 ms

bootstrap.min.css

bootstrap.min.css

250 ms

bootstrap.min.js

bootstrap.min.js

178 ms

font-awesome.min.css

font-awesome.min.css

212 ms

css

css

33 ms

stylesheet.css

stylesheet.css

179 ms

toastr.min.css

toastr.min.css

206 ms

custom.js

custom.js

341 ms

swiper.min.css

swiper.min.css

336 ms

opencart.css

opencart.css

358 ms

swiper.jquery.js

swiper.jquery.js

423 ms

owl.carousel.css

owl.carousel.css

411 ms

owl.theme.css

owl.theme.css

392 ms

owl.carousel.min.js

owl.carousel.min.js

494 ms

magnific-popup.css

magnific-popup.css

492 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

522 ms

jquery.lazy.min.js

jquery.lazy.min.js

543 ms

common.js

common.js

573 ms

toastr.min.js

toastr.min.js

580 ms

js

js

60 ms

WebResource.axd

WebResource.axd

644 ms

ScriptResource.axd

ScriptResource.axd

672 ms

ScriptResource.axd

ScriptResource.axd

643 ms

SmokeTokes_1034.jpg

SmokeTokes_1034.jpg

234 ms

SmokeTokes_1033.jpg

SmokeTokes_1033.jpg

229 ms

SmokeTokes_1031.jpg

SmokeTokes_1031.jpg

229 ms

SmokeTokes_1030.jpg

SmokeTokes_1030.jpg

223 ms

SmokeTokes_1029.jpg

SmokeTokes_1029.jpg

221 ms

SmokeTokes_1027.jpg

SmokeTokes_1027.jpg

466 ms

SmokeTokes_27.jpg

SmokeTokes_27.jpg

377 ms

SmokeTokes_26.jpg

SmokeTokes_26.jpg

380 ms

SmokeTokes_25.jpg

SmokeTokes_25.jpg

379 ms

SmokeTokes_24.jpg

SmokeTokes_24.jpg

381 ms

SmokeTokes_23.jpg

SmokeTokes_23.jpg

379 ms

SmokeTokes_22.jpg

SmokeTokes_22.jpg

612 ms

SmokeTokes_21.jpg

SmokeTokes_21.jpg

609 ms

SmokeTokes_20.jpg

SmokeTokes_20.jpg

698 ms

82.jpg

82.jpg

532 ms

101.jpg

101.jpg

673 ms

205.jpg

205.jpg

613 ms

4393.jpg

4393.jpg

863 ms

73.jpg

73.jpg

738 ms

207.jpg

207.jpg

699 ms

3361.jpg

3361.jpg

710 ms

206.jpg

206.jpg

800 ms

152.jpg

152.jpg

914 ms

107.jpg

107.jpg

994 ms

74.jpg

74.jpg

862 ms

193.jpg

193.jpg

880 ms

93.jpg

93.jpg

969 ms

129.jpg

129.jpg

1016 ms

209.jpg

209.jpg

1013 ms

210.jpg

210.jpg

965 ms

211.jpg

211.jpg

1273 ms

162.jpg

162.jpg

1157 ms

195.jpg

195.jpg

1192 ms

212.jpg

212.jpg

1258 ms

3244.jpg

3244.jpg

1174 ms

3290.jpg

3290.jpg

1171 ms

smoketokes_logo.png

smoketokes_logo.png

205 ms

icon.png

icon.png

204 ms

location.png

location.png

205 ms

phone.png

phone.png

130 ms

email.png

email.png

267 ms

analytics.js

analytics.js

22 ms

collect

collect

18 ms

Poppins-Regular.ttf

Poppins-Regular.ttf

321 ms

fontawesome-webfont3e6e.woff

fontawesome-webfont3e6e.woff

223 ms

Poppins-Medium.ttf

Poppins-Medium.ttf

352 ms

3298.jpg

3298.jpg

1316 ms

4392.jpg

4392.jpg

1122 ms

4394.jpg

4394.jpg

1211 ms

4396.jpg

4396.jpg

1279 ms

4397.jpg

4397.jpg

1344 ms

Poppins-SemiBold.ttf

Poppins-SemiBold.ttf

356 ms

default

default

308 ms

4398.jpg

4398.jpg

1206 ms

4399.jpg

4399.jpg

1219 ms

4400.jpg

4400.jpg

1275 ms

nr-spa-1216.min.js

nr-spa-1216.min.js

29 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

51 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

76 ms

twk-event-polyfill.js

twk-event-polyfill.js

72 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

67 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

310 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

309 ms

twk-main.js

twk-main.js

104 ms

twk-vendor.js

twk-vendor.js

156 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

80 ms

twk-chunk-common.js

twk-chunk-common.js

99 ms

twk-runtime.js

twk-runtime.js

101 ms

twk-app.js

twk-app.js

119 ms

NRJS-e5007b2355e2e5639cc

NRJS-e5007b2355e2e5639cc

123 ms

Accessibility Review

smoketokes.ca accessibility score

69

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

smoketokes.ca best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

smoketokes.ca SEO score

68

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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 neither this language nor any other was claimed in <html> or <meta> tags. 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.

Social Sharing Optimization

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: