1.8 sec in total
390 ms
1.3 sec
133 ms
Click here to check amazing Spliffmag content. Otherwise, check out these important facts you probably never knew about spliffmag.com
Visit spliffmag.comWe analyzed Spliffmag.com page load time and found that the first response time was 390 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 25% of websites can load faster.
spliffmag.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.4 s
66/100
25%
Value3.1 s
93/100
10%
Value330 ms
75/100
30%
Value0.053
98/100
15%
Value4.0 s
87/100
10%
390 ms
394 ms
438 ms
221 ms
222 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Spliffmag.com, 28% (10 requests) were made to Google.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (462 ms) relates to the external source Afternic.com.
Page size can be reduced by 441.2 kB (57%)
773.0 kB
331.8 kB
In fact, the total size of Spliffmag.com main page is 773.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 567.1 kB which makes up the majority of the site volume.
Potential reduce by 48.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 48.8 kB or 72% of the original size.
Potential reduce by 1.1 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. Spliffmag images are well optimized though.
Potential reduce by 391.3 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 391.3 kB or 69% of the original size.
Number of requests can be reduced by 24 (71%)
34
10
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spliffmag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
SpliffMag.com
390 ms
jquery-1.7.1.min.js
394 ms
jquery-ui-1.8.18.custom.min.js
438 ms
constants.js
221 ms
main.js
222 ms
ajax.js
222 ms
datetime.js
160 ms
jquery.validate.min.js
220 ms
jquery.validate.custom.js
275 ms
jquery.placeholder.min.js
293 ms
hash.js
296 ms
common_an.js
369 ms
tdfs-inner.css
332 ms
jqueryui-customized.css
462 ms
challenge
58 ms
analytics.js
23 ms
seal
50 ms
tdfs-pro-csr-f.png
172 ms
recaptcha.js
13 ms
afternic.png
198 ms
collect
28 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
19 ms
button-submit-bg.png
77 ms
static
220 ms
elqCfg.min.js
34 ms
refresh.gif
28 ms
audio.gif
5 ms
text.gif
9 ms
help.gif
10 ms
sprite.png
6 ms
reload
38 ms
afternic.png
58 ms
image
19 ms
nr-885.min.js
16 ms
vms.js
86 ms
d89ec68706
45 ms
spliffmag.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
spliffmag.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
spliffmag.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spliffmag.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Spliffmag.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.
spliffmag.com
Open Graph description is not detected on the main page of Spliffmag. 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: