Tools & Wizards About Us
vapefatty.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vapefatty.com

IIS7

Page Load Speed

4.5 sec in total

First Response

926 ms

Resources Loaded

3.2 sec

Page Rendered

422 ms

vapefatty.com screenshot

About Website

Click here to check amazing Vapefatty content for United States. Otherwise, check out these important facts you probably never knew about vapefatty.com

Visit vapefatty.com

Key Findings

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

Performance Metrics

vapefatty.com performance score

0

Network Requests Diagram

www.vapefatty.com

926 ms

wp-emoji-release.min.js

87 ms

emc2pdc.css

116 ms

fonts.css

117 ms

animations.css

116 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 86% of them (51 requests) were addressed to the original Vapefatty.com, 7% (4 requests) were made to Cdn.ywxi.net and 3% (2 requests) were made to Verify.authorize.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Vapefatty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 634.5 kB (18%)

Content Size

3.5 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vapefatty.com main page is 3.5 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. 40% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 58.0 kB

  • Original 70.0 kB
  • After minification 62.3 kB
  • After compression 12.0 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. This page needs HTML code to be minified as it can gain 7.7 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 68.7 kB

  • Original 2.7 MB
  • After minification 2.7 MB

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. Vapefatty images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 294.1 kB

  • Original 422.1 kB
  • After minification 408.3 kB
  • After compression 128.0 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 294.1 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 213.7 kB

  • Original 251.1 kB
  • After minification 190.4 kB
  • After compression 37.4 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. Vapefatty.com needs all CSS files to be minified and compressed as it can save up to 213.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.vapefatty.com

www.vapefatty.com

926 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

87 ms

emc2pdc.css

emc2pdc.css

116 ms

fonts.css

fonts.css

117 ms

animations.css

animations.css

116 ms

foundation.css

foundation.css

218 ms

style.css

style.css

152 ms

css

css

24 ms

wishlist.css

wishlist.css

158 ms

front-compulsory.css

front-compulsory.css

152 ms

jquery.js

jquery.js

192 ms

jquery-migrate.min.js

jquery-migrate.min.js

188 ms

wishlist.js

wishlist.js

187 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

101 ms

add-to-cart.min.js

add-to-cart.min.js

100 ms

seal.js

seal.js

91 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

76 ms

woocommerce.min.js

woocommerce.min.js

76 ms

jquery.cookie.min.js

jquery.cookie.min.js

77 ms

cart-fragments.min.js

cart-fragments.min.js

104 ms

yith-autocomplete.min.js

yith-autocomplete.min.js

187 ms

modernizr.js

modernizr.js

186 ms

flatsome-plugins.js

flatsome-plugins.js

256 ms

flatsome-theme.js

flatsome-theme.js

194 ms

flatsome-woocommerce.js

flatsome-woocommerce.js

190 ms

comment-reply.min.js

comment-reply.min.js

195 ms

wp-embed.min.js

wp-embed.min.js

220 ms

devbridge-jquery-autocomplete.min.js

devbridge-jquery-autocomplete.min.js

242 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

320 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

320 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

322 ms

jquery_cke.js

jquery_cke.js

321 ms

emc2pdc.js

emc2pdc.js

321 ms

vapefattytrans.jpg

vapefattytrans.jpg

1554 ms

logo.jpg

logo.jpg

554 ms

dummy.gif

dummy.gif

513 ms

chubby-gorilla-splash.jpg

chubby-gorilla-splash.jpg

517 ms

uncle-junks-fog-cabin-a-new-dawn-1-5-1-300x300.jpg

uncle-junks-fog-cabin-a-new-dawn-1-5-1-300x300.jpg

513 ms

wpspin_light.gif

wpspin_light.gif

514 ms

JAZZYER-BOBA-300x300.jpg

JAZZYER-BOBA-300x300.jpg

514 ms

high-voltage-tesla-1-5-300x300.jpg

high-voltage-tesla-1-5-300x300.jpg

515 ms

bfb-straight-outta-the-toaster-1-300x300.jpg

bfb-straight-outta-the-toaster-1-300x300.jpg

516 ms

chubby-gorilla-unicorn-bottle-1-3-3-300x300.jpg

chubby-gorilla-unicorn-bottle-1-3-3-300x300.jpg

515 ms

dead-prezidents-nixon-1-5-1-300x300.jpg

dead-prezidents-nixon-1-5-1-300x300.jpg

515 ms

flawless-hot-mess-copy-1-300x300.jpg

flawless-hot-mess-copy-1-300x300.jpg

517 ms

legend-e-soda-cactus-breeze-1-300x300.png

legend-e-soda-cactus-breeze-1-300x300.png

519 ms

RapidSSL_SEAL-90x50.gif

RapidSSL_SEAL-90x50.gif

517 ms

icomoon.woff

icomoon.woff

504 ms

secure90x72.gif

secure90x72.gif

9 ms

1.js

1.js

55 ms

host.js

host.js

386 ms

www.vapefatty.com

www.vapefatty.com

581 ms

tm-float-bg-right-bottom.png

tm-float-bg-right-bottom.png

59 ms

ajax

ajax

318 ms

float2-right.png

float2-right.png

237 ms

fancybox-x.png

fancybox-x.png

37 ms

fancybox.png

fancybox.png

39 ms

fancybox-y.png

fancybox-y.png

44 ms

blank.gif

blank.gif

39 ms

SEO Factors

vapefatty.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vapefatty.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), while the claimed language is English. Our system also found out that Vapefatty.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

vapefatty.com

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