Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

180smoke.ca

Best Vape Shop Online Canada | Free Shipping over $49 | 180 Smoke

Page Load Speed

1.4 sec in total

First Response

12 ms

Resources Loaded

1.1 sec

Page Rendered

348 ms

180smoke.ca screenshot

About Website

Visit 180smoke.ca now to see the best up-to-date 180 Smoke content for Canada and also check out these interesting facts you probably never knew about 180smoke.ca

180Smoke is the #1 Vape Shop in Canada. We offer Free Shipping over $49 and competitive prices. Check us out! We have the widest selection of products.

Visit 180smoke.ca

Key Findings

We analyzed 180smoke.ca page load time and found that the first response time was 12 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

180smoke.ca performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value2,980 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.698

7/100

15%

TTI (Time to Interactive)

Value12.4 s

14/100

10%

Network Requests Diagram

180smoke.ca

12 ms

www.180smoke.ca

219 ms

css

36 ms

css

68 ms

styles.css

30 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 180smoke.ca, 72% (83 requests) were made to Cdn.180smoke.ca and 6% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (273 ms) relates to the external source Apis.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (67%)

Content Size

1.8 MB

After Optimization

596.6 kB

In fact, the total size of 180smoke.ca main page is 1.8 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. 80% 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. Javascripts take 803.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 191.7 kB

  • Original 223.0 kB
  • After minification 166.6 kB
  • After compression 31.4 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. This page needs HTML code to be minified as it can gain 56.5 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 191.7 kB or 86% of the original size.

Image Optimization

-14%

Potential reduce by 42.2 kB

  • Original 297.5 kB
  • After minification 255.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. Obviously, 180 Smoke needs image optimization as it can save up to 42.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 571.0 kB

  • Original 803.9 kB
  • After minification 803.9 kB
  • After compression 232.9 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 571.0 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 406.4 kB

  • Original 483.4 kB
  • After minification 385.0 kB
  • After compression 77.0 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. 180smoke.ca needs all CSS files to be minified and compressed as it can save up to 406.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (57%)

Requests Now

105

After Optimization

45

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

Accessibility Review

180smoke.ca accessibility score

76

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

180smoke.ca best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

180smoke.ca SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 180smoke.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 180smoke.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

Open Graph description is not detected on the main page of 180 Smoke. 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: