1.6 sec in total
208 ms
1.2 sec
179 ms
Visit salvia.net now to see the best up-to-date Salvia content for United States and also check out these interesting facts you probably never knew about salvia.net
Welcome to the information website on the mysterious plant Salvia divinorum
Visit salvia.netWe analyzed Salvia.net page load time and found that the first response time was 208 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.
salvia.net performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value11.6 s
0/100
25%
Value7.7 s
25/100
10%
Value190 ms
91/100
30%
Value0.004
100/100
15%
Value7.7 s
46/100
10%
208 ms
203 ms
85 ms
74 ms
68 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 33% of them (16 requests) were addressed to the original Salvia.net, 17% (8 requests) were made to Apis.google.com and 8% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (316 ms) belongs to the original domain Salvia.net.
Page size can be reduced by 371.5 kB (68%)
548.1 kB
176.5 kB
In fact, the total size of Salvia.net main page is 548.1 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. 50% of websites need less resources to load. Javascripts take 371.2 kB which makes up the majority of the site volume.
Potential reduce by 14.7 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 14.7 kB or 68% of the original size.
Potential reduce by 88 B
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. Salvia images are well optimized though.
Potential reduce by 250.7 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 250.7 kB or 68% of the original size.
Potential reduce by 106.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. Salvia.net needs all CSS files to be minified and compressed as it can save up to 106.1 kB or 88% of the original size.
Number of requests can be reduced by 24 (53%)
45
21
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Salvia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
salvia.net
208 ms
www.salvia.net
203 ms
style.css
85 ms
all.js
74 ms
129514127
68 ms
plusone.js
133 ms
widgets.js
102 ms
piwik.js
315 ms
site_bg_2.gif
117 ms
header_boven.jpg
211 ms
header_onder.jpg
210 ms
links_achter.jpg
210 ms
vlagfr.gif
209 ms
vlagnl.gif
209 ms
vlaguk.gif
209 ms
vlagde.gif
312 ms
vlagpt.gif
312 ms
menu_bg.gif
311 ms
text_onder.jpg
316 ms
salvia_flower.gif
312 ms
player.js
149 ms
player.css
102 ms
ga.js
124 ms
vuid.min.js
112 ms
85 ms
xd_arbiter.php
91 ms
xd_arbiter.php
215 ms
cb=gapi.loaded_0
59 ms
cb=gapi.loaded_1
59 ms
fastbutton
151 ms
__utm.gif
63 ms
proxy.html
81 ms
558779830.jpg
125 ms
postmessageRelay
56 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
41 ms
print.css
109 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
114 ms
piwik.php
302 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
130 ms
3193398744-postmessagerelay.js
57 ms
rpc:shindig_random.js
36 ms
like.php
42 ms
qeKvIRsJabD.js
130 ms
LVx-xkvaJ0b.png
142 ms
cb=gapi.loaded_0
14 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
37 ms
jot
91 ms
salvia.net 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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
salvia.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Salvia.net 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 Salvia.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
salvia.net
Open Graph description is not detected on the main page of Salvia. 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: