Tools & Wizards About Us
savorvaporusa.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

savorvaporusa.com

Sublime Eliquid | Premium eJuices

Page Load Speed

5.1 sec in total

First Response

1.4 sec

Resources Loaded

3.5 sec

Page Rendered

231 ms

savorvaporusa.com screenshot

About Website

Welcome to savorvaporusa.com homepage info - get ready to check Savorvaporusa best content right away, or after learning these important things about savorvaporusa.com

Latest Posts There are a lot of widgets bundled with Page Builder. You can use them to bring your pages to life.

Visit savorvaporusa.com

Key Findings

We analyzed Savorvaporusa.com page load time and found that the first response time was 1.4 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

savorvaporusa.com performance score

0

Network Requests Diagram

savorvaporusa.com

1360 ms

wp-emoji-release.min.js

168 ms

front.css

128 ms

style.css

134 ms

dashicons.min.css

262 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 92% of them (60 requests) were addressed to the original Savorvaporusa.com, 5% (3 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Savorvaporusa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 383.6 kB (31%)

Content Size

1.2 MB

After Optimization

845.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Savorvaporusa.com main page is 1.2 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. 35% of websites need less resources to load. Images take 777.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 35.4 kB

  • Original 44.2 kB
  • After minification 43.3 kB
  • After compression 8.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 35.4 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 58.8 kB

  • Original 777.6 kB
  • After minification 718.8 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. Savorvaporusa images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 168.3 kB

  • Original 234.4 kB
  • After minification 208.1 kB
  • After compression 66.1 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 168.3 kB or 72% of the original size.

CSS Optimization

-70%

Potential reduce by 121.0 kB

  • Original 172.6 kB
  • After minification 162.8 kB
  • After compression 51.7 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. Savorvaporusa.com needs all CSS files to be minified and compressed as it can save up to 121.0 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (53%)

Requests Now

62

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Savorvaporusa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

savorvaporusa.com

savorvaporusa.com

1360 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

168 ms

front.css

front.css

128 ms

style.css

style.css

134 ms

dashicons.min.css

dashicons.min.css

262 ms

desktop_style.css

desktop_style.css

155 ms

woocommerce-layout.css

woocommerce-layout.css

190 ms

woocommerce.css

woocommerce.css

317 ms

styles.min.css

styles.min.css

196 ms

css

css

31 ms

owl.carousel.css

owl.carousel.css

235 ms

main.css

main.css

224 ms

styles.css

styles.css

248 ms

style.css

style.css

330 ms

css

css

34 ms

css

css

44 ms

quick-count.css

quick-count.css

282 ms

jquery.js

jquery.js

528 ms

jquery-migrate.min.js

jquery-migrate.min.js

300 ms

front_end_script.js

front_end_script.js

320 ms

rotator.js

rotator.js

343 ms

modernizr.custom.js

modernizr.custom.js

354 ms

menu.js

menu.js

387 ms

jqFancyTransitions.1.8.min.js

jqFancyTransitions.1.8.min.js

387 ms

gd-recaptcha.css

gd-recaptcha.css

398 ms

quick-count-load-frontend.js

quick-count-load-frontend.js

330 ms

add-to-cart.min.js

add-to-cart.min.js

350 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

393 ms

woocommerce.min.js

woocommerce.min.js

384 ms

jquery.cookie.min.js

jquery.cookie.min.js

382 ms

cart-fragments.min.js

cart-fragments.min.js

395 ms

toucheffects.js

toucheffects.js

404 ms

owl.carousel.js

owl.carousel.js

522 ms

angelleye-frontend.js

angelleye-frontend.js

454 ms

wp-embed.min.js

wp-embed.min.js

456 ms

header.png

header.png

164 ms

header-bottom.png

header-bottom.png

260 ms

sliderbottom.png

sliderbottom.png

164 ms

tempera-slide2.jpg

tempera-slide2.jpg

450 ms

tempera-slide1.jpg

tempera-slide1.jpg

229 ms

tempera-slide-3.jpg

tempera-slide-3.jpg

228 ms

featured-image1.jpg

featured-image1.jpg

181 ms

featured-image2.jpg

featured-image2.jpg

164 ms

featured-image3.jpg

featured-image3.jpg

204 ms

lsep.png

lsep.png

226 ms

featured-image1.png

featured-image1.png

270 ms

featured-image2.png

featured-image2.png

282 ms

featured-image3.png

featured-image3.png

281 ms

Peach-Cobbler-90x90.jpg

Peach-Cobbler-90x90.jpg

305 ms

Peach-90x90.jpg

Peach-90x90.jpg

329 ms

mojito-90x90.jpg

mojito-90x90.jpg

344 ms

mango-tango-90x90.jpg

mango-tango-90x90.jpg

340 ms

mango-90x90.jpg

mango-90x90.jpg

343 ms

footer.png

footer.png

378 ms

youtubeicon.png

youtubeicon.png

393 ms

gplusicon.png

gplusicon.png

394 ms

picassaicon.png

picassaicon.png

407 ms

liicon.png

liicon.png

397 ms

feedicon.png

feedicon.png

452 ms

d5logofooter.png

d5logofooter.png

456 ms

Cvwn58PR0rYLGpoTMF4KMA.ttf

Cvwn58PR0rYLGpoTMF4KMA.ttf

128 ms

HrI4ZJpJ3Fh0wa5ofYMK8S3USBnSvpkopQaUR-2r7iU.ttf

HrI4ZJpJ3Fh0wa5ofYMK8S3USBnSvpkopQaUR-2r7iU.ttf

127 ms

admin-ajax.php

admin-ajax.php

1397 ms

savorvaporusa.com

savorvaporusa.com

1169 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

100 ms

SEO Factors

savorvaporusa.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Savorvaporusa.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 Savorvaporusa.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.

Social Sharing Optimization

savorvaporusa.com

Open Graph description is not detected on the main page of Savorvaporusa. 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: