21.3 sec in total
6.8 sec
14.1 sec
432 ms
Click here to check amazing Spliffin content for United States. Otherwise, check out these important facts you probably never knew about spliffin.com
Visit spliffin.comWe analyzed Spliffin.com page load time and found that the first response time was 6.8 sec and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
spliffin.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.4 s
100/100
25%
Value1.3 s
100/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value1.8 s
100/100
10%
6754 ms
5833 ms
69 ms
135 ms
132 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 82% of them (50 requests) were addressed to the original Spliffin.com, 8% (5 requests) were made to Use.typekit.net and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Spliffin.com.
Page size can be reduced by 582.6 kB (30%)
1.9 MB
1.3 MB
In fact, the total size of Spliffin.com main page is 1.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 25.6 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 25.6 kB or 76% of the original size.
Potential reduce by 39.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. Spliffin images are well optimized though.
Potential reduce by 295.5 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 295.5 kB or 68% of the original size.
Potential reduce by 222.2 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. Spliffin.com needs all CSS files to be minified and compressed as it can save up to 222.2 kB or 84% of the original size.
Number of requests can be reduced by 27 (48%)
56
29
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spliffin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
spliffin.com
6754 ms
www.spliffin.com
5833 ms
wp-emoji-release.min.js
69 ms
styles.css
135 ms
sb-instagram.css
132 ms
font-awesome.min.css
252 ms
styles.min.css
144 ms
bootstrap.css
201 ms
style.css
139 ms
jquery-ui.min.css
134 ms
jquery.js
321 ms
jquery-migrate.min.js
196 ms
bootstrap.min.js
216 ms
scripts.js
215 ms
modernizr.full.min.js
215 ms
ikq4cyf.js
186 ms
flexslider.css
257 ms
public.css
256 ms
jquery.form.min.js
266 ms
scripts.js
264 ms
sb-instagram.js
266 ms
core.min.js
409 ms
datepicker.min.js
408 ms
widget.min.js
411 ms
button.min.js
409 ms
spinner.min.js
409 ms
wp-embed.min.js
410 ms
jquery.flexslider-min.js
410 ms
ga.js
26 ms
www.spliffin.com
200 ms
__utm.gif
23 ms
analytics.js
67 ms
close.png
346 ms
loading.gif
340 ms
prev.png
342 ms
next.png
338 ms
spl-logo.png
336 ms
mail-spliffin.png
338 ms
facebook2-spliffin.png
341 ms
instagram-spliffin.png
341 ms
twitter-spliffin.png
342 ms
Banner-girl-1b.jpg
399 ms
Hatslider4.jpg
400 ms
Banner-girl-2b.jpg
577 ms
July15_04.png
946 ms
tagline2.png
342 ms
button.png
342 ms
2014_CertifiedCannabis-Concentrate_small.png
337 ms
sclabs_2k13_logo_seal_outlined_small.png
333 ms
norml_business_network.png
390 ms
spliffin-crown.png
389 ms
products-order4.jpg
658 ms
products-2-hardware.jpg
532 ms
age-verify.jpg
420 ms
XcYKtgZATg1406ZeSQh8Z9zCS_IF8zHzEq8VBqNkttIffVn4ggMWeMJ6Mk6f5MS.woff
282 ms
PIZQlLjHSeaL0EK42302EFzFXA5lIHGqCwIsmsdtZw3ffV14ggMWeMJ6Mk6f5Mb.woff
284 ms
ajax-loader.gif
134 ms
collect
26 ms
kCuvRNUImcEZxX_Cye4vi5vc3S44ajslM98S9ZWBVPSffVd4ggMWeMJ6Mk6f5Mt.woff
66 ms
bg_direction_nav.png
130 ms
p.gif
130 ms
spliffin.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
spliffin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
spliffin.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spliffin.com 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 Spliffin.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.
spliffin.com
Open Graph description is not detected on the main page of Spliffin. 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: