8.5 sec in total
2.8 sec
5.2 sec
479 ms
Click here to check amazing Smokesafely content. Otherwise, check out these important facts you probably never knew about smokesafely.com
Visit smokesafely.comWe analyzed Smokesafely.com page load time and found that the first response time was 2.8 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
smokesafely.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.3 s
69/100
25%
Value3.9 s
82/100
10%
Value1,350 ms
17/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
2849 ms
100 ms
116 ms
88 ms
84 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Smokesafely.com, 6% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Smokesafely.com.
Page size can be reduced by 2.4 MB (69%)
3.4 MB
1.0 MB
In fact, the total size of Smokesafely.com main page is 3.4 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. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 67.8 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 67.8 kB or 78% of the original size.
Potential reduce by 219.2 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, Smokesafely needs image optimization as it can save up to 219.2 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 885.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 885.4 kB or 70% of the original size.
Potential reduce by 1.2 MB
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. Smokesafely.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 86% of the original size.
Number of requests can be reduced by 63 (69%)
91
28
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smokesafely. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
smokesafely.com
2849 ms
wp-emoji-release.min.js
100 ms
dashicons.min.css
116 ms
jquery-ui-dialog.min.css
88 ms
layerslider.css
84 ms
css
41 ms
styles.css
82 ms
settings.css
90 ms
css
56 ms
css
72 ms
css
74 ms
settings.css
123 ms
woocommerce-layout.css
129 ms
woocommerce.css
126 ms
styles.css
131 ms
style.css
182 ms
responsive.css
151 ms
icomoon.css
208 ms
js_composer.min.css
244 ms
woocommerce.css
177 ms
jquery.js
309 ms
jquery-migrate.min.js
205 ms
greensock.js
326 ms
layerslider.kreaturamedia.jquery.js
308 ms
layerslider.transitions.js
231 ms
lightbox.js
324 ms
jquery.themepunch.tools.min.js
374 ms
jquery.themepunch.essential.min.js
373 ms
jquery.themepunch.revolution.min.js
344 ms
add-to-cart.min.js
345 ms
woocommerce-add-to-cart.js
370 ms
css
77 ms
core.min.js
367 ms
widget.min.js
368 ms
mouse.min.js
367 ms
resizable.min.js
368 ms
draggable.min.js
369 ms
button.min.js
398 ms
position.min.js
401 ms
dialog.min.js
402 ms
wpdialog.min.js
401 ms
cfpop.js
123 ms
jsapi
28 ms
jquery.form.min.js
478 ms
scripts.js
409 ms
jquery.blockUI.min.js
410 ms
woocommerce.min.js
399 ms
jquery.cookie.min.js
399 ms
cart-fragments.min.js
396 ms
scripts.js
514 ms
jquery.scrollTo.js
370 ms
jquery.countdown.js
365 ms
map.js
364 ms
mediaelement.js
430 ms
jquery.flexslider.js
342 ms
jquery.validate.js
378 ms
jquery.easychart.js
352 ms
responsivecarousel.min.js
345 ms
jquery.owl.carousel.min.js
345 ms
menu.min.js
327 ms
autocomplete.min.js
253 ms
jquery.custom.js
299 ms
canvas-effects.js
259 ms
wp-embed.min.js
240 ms
js_composer_front.min.js
241 ms
preloader.gif
183 ms
Smoke-Safely-logo-2.png
627 ms
dummy.png
220 ms
joestick-large-150x150.jpg
624 ms
joe-stick-charger-150x150.jpg
625 ms
joe-stick-atomizer-150x150.jpg
631 ms
joe-stick-replacement-battery-150x150.jpg
631 ms
Lariat.png
633 ms
Menthol.png
634 ms
Cappuccino.png
636 ms
Pomegranate.png
637 ms
Payment2.png
637 ms
Smoke3.png
637 ms
SmokeBackground.jpg
564 ms
select-icon.png
559 ms
sourcesanspro-regular-webfont.woff
480 ms
Icomoon.svg
485 ms
fontawesome-webfont.svg
483 ms
fontawesome-webfont.woff
481 ms
sourcesanspro-bold-webfont.woff
481 ms
hbicons.woff
480 ms
SourceSansPro-Semibold.woff
481 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
52 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
51 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
458 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
51 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
168 ms
revolution.extension.slideanims.min.js
89 ms
revolution.extension.actions.min.js
86 ms
revolution.extension.layeranimation.min.js
89 ms
revolution.extension.navigation.min.js
89 ms
revolution.extension.parallax.min.js
89 ms
smokesafely.com
1275 ms
coloredbg.png
48 ms
Smoke52.jpg
41 ms
JoeStick.png
48 ms
revicons.woff
47 ms
woocommerce-smallscreen.css
42 ms
smokesafely.com accessibility score
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
smokesafely.com 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
Missing source maps for large first-party JavaScript
smokesafely.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smokesafely.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Smokesafely.com 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.
smokesafely.com
Open Graph description is not detected on the main page of Smokesafely. 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: