1.1 sec in total
93 ms
930 ms
114 ms
Visit smoketoken.com now to see the best up-to-date Smoke Token content for United States and also check out these interesting facts you probably never knew about smoketoken.com
The largest smoke shop in the southeast! Specializing in functional glass pipes, vapes, smoking accessories, and much more!
Visit smoketoken.comWe analyzed Smoketoken.com page load time and found that the first response time was 93 ms and then it took 1 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.
smoketoken.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value6.0 s
13/100
25%
Value6.5 s
38/100
10%
Value4,480 ms
0/100
30%
Value0.063
97/100
15%
Value16.1 s
6/100
10%
93 ms
75 ms
79 ms
117 ms
121 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Smoketoken.com, 74% (31 requests) were made to Static.parastorage.com and 12% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (526 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.2 MB (77%)
2.9 MB
659.8 kB
In fact, the total size of Smoketoken.com main page is 2.9 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. 70% of websites need less resources to load. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.4 kB or 80% of the original size.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 44.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. Smoketoken.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 29 (73%)
40
11
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smoke Token. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
smoketoken.com
93 ms
www.smoketoken.com
75 ms
bt
79 ms
require.min.js
117 ms
main-r.min.js
121 ms
viewer.css
68 ms
UpgradeBrowser.js
71 ms
ugc-viewer
38 ms
dynamicmodel
30 ms
2443dd_11f629aa6f34437a64f9fd2d9d587ddb_467.json.z
324 ms
2443dd_8bb8476f3e8c763d4f201f19e555149b_350.json.z
526 ms
bt
127 ms
skins.min.js
125 ms
components.min.js
301 ms
utils.min.js
66 ms
core.min.js
303 ms
react-with-addons.min.js
119 ms
lodash.min.js
44 ms
TweenMax.min.js
119 ms
layout.min.js
119 ms
tpa.min.js
310 ms
fonts.min.js
125 ms
animations.min.js
119 ms
swfobject.min.js
119 ms
mousetrap.min.js
120 ms
tweenEngine.min.js
120 ms
DrawSVGPlugin.min.js
306 ms
react-dom.min.js
119 ms
ScrollToPlugin.min.js
120 ms
widgets.min.js
120 ms
experiment.js
121 ms
render.min.js
121 ms
wixappsCore.min.js
295 ms
wixappsClassics.min.js
290 ms
wixappsBuilder.min.js
294 ms
zepto.min.js
292 ms
color.min.js
294 ms
bt
211 ms
dc.js
173 ms
react-dom-server.min.js
135 ms
latin.css
20 ms
bt
78 ms
smoketoken.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
smoketoken.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
Page has valid source maps
smoketoken.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smoketoken.com 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 Smoketoken.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.
smoketoken.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: