Tools & Wizards About Us
indigovapor.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

indigovapor.com

AgeChecker.Net

Page Load Speed

2.6 sec in total

First Response

527 ms

Resources Loaded

1.6 sec

Page Rendered

448 ms

indigovapor.com screenshot

About Website

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

Experience the difference Indigo Vapor's eLiquid can make in your vaping experience! All flavors are crafted by us and blended by our staff.

Visit indigovapor.com

Key Findings

We analyzed Indigovapor.com page load time and found that the first response time was 527 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

indigovapor.com performance score

0

Network Requests Diagram

www.indigovapor.com

527 ms

styles.css

105 ms

modernizr.foundation.js

57 ms

jquery.min.js

46 ms

viewport.js

52 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Indigovapor.com, 51% (32 requests) were made to Cdn3.bigcommerce.com and 21% (13 requests) were made to Cdn4.bigcommerce.com. The less responsive or slowest element that took the longest time to load (527 ms) belongs to the original domain Indigovapor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 737.6 kB (37%)

Content Size

2.0 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 34.7 kB

  • Original 45.9 kB
  • After minification 43.3 kB
  • After compression 11.2 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 34.7 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 33.8 kB

  • Original 1.1 MB
  • After minification 1.0 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. Indigovapor images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 458.6 kB

  • Original 633.4 kB
  • After minification 527.3 kB
  • After compression 174.8 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 458.6 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 210.6 kB

  • Original 246.5 kB
  • After minification 196.3 kB
  • After compression 35.9 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. Indigovapor.com needs all CSS files to be minified and compressed as it can save up to 210.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (59%)

Requests Now

61

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.indigovapor.com

www.indigovapor.com

527 ms

styles.css

styles.css

105 ms

modernizr.foundation.js

modernizr.foundation.js

57 ms

jquery.min.js

jquery.min.js

46 ms

viewport.js

viewport.js

52 ms

jquery-ui.min.js

jquery-ui.min.js

91 ms

jquery.validate.js

jquery.validate.js

93 ms

product.functions.js

product.functions.js

82 ms

product.attributes.js

product.attributes.js

93 ms

quickview.js

quickview.js

83 ms

quickview.initialise.js

quickview.initialise.js

81 ms

jquery.form.js

jquery.form.js

90 ms

imodal.js

imodal.js

94 ms

si.js

si.js

101 ms

asv_seal.js

asv_seal.js

475 ms

quicksearch.js

quicksearch.js

89 ms

foundation.min.js

foundation.min.js

87 ms

common.js

common.js

87 ms

jquery.zoomie.js

jquery.zoomie.js

50 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

86 ms

jquery.fittext.js

jquery.fittext.js

85 ms

template.js

template.js

84 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

92 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

90 ms

jquery.validate.js

jquery.validate.js

114 ms

jquery.form.js

jquery.form.js

84 ms

product.attributes.js

product.attributes.js

86 ms

product.functions.js

product.functions.js

73 ms

product.js

product.js

72 ms

bc_pinstrumentation.min.js

bc_pinstrumentation.min.js

63 ms

visitor.js

visitor.js

66 ms

widgets.js

widgets.js

24 ms

seal.js

seal.js

75 ms

css

css

44 ms

analytics.js

analytics.js

74 ms

analytics.min.js

analytics.min.js

75 ms

beacon_api.js

beacon_api.js

44 ms

shutterstockblackpaintswatch3_1441319822__42696.jpg

shutterstockblackpaintswatch3_1441319822__42696.jpg

40 ms

smarticon

smarticon

176 ms

Spring16.jpg

Spring16.jpg

147 ms

Paint_Swatch.jpg

Paint_Swatch.jpg

21 ms

Shipping_Increases011816.jpg

Shipping_Increases011816.jpg

169 ms

Tesla160Crop__20807.1441215424.365.365.jpg

Tesla160Crop__20807.1441215424.365.365.jpg

144 ms

Tip2_Crop__39112.1448481014.365.365.jpg

Tip2_Crop__39112.1448481014.365.365.jpg

154 ms

BatteredBerry__65634.1443464113.365.365.jpg

BatteredBerry__65634.1443464113.365.365.jpg

141 ms

TeslaWoodCrop160W__87337.1441215557.365.365.jpg

TeslaWoodCrop160W__87337.1441215557.365.365.jpg

168 ms

Eureka_Rball__14133.1440344632.365.365.jpg

Eureka_Rball__14133.1440344632.365.365.jpg

168 ms

eLeaf40W_TC__02366.1441280488.365.365.jpg

eLeaf40W_TC__02366.1441280488.365.365.jpg

155 ms

BottomOTB__56743.1443464067.365.365.jpg

BottomOTB__56743.1443464067.365.365.jpg

164 ms

VortexCrop__10424.1441216302.365.365.jpg

VortexCrop__10424.1441216302.365.365.jpg

169 ms

ccardlogos.png

ccardlogos.png

164 ms

collect

collect

85 ms

fornax.min.js

fornax.min.js

44 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

77 ms

ASV_compliance_certificate.jpg

ASV_compliance_certificate.jpg

22 ms

ASV_shield.png

ASV_shield.png

22 ms

secure90x72.gif

secure90x72.gif

56 ms

jquery.min.js

jquery.min.js

149 ms

right-arrow.png

right-arrow.png

85 ms

index.php

index.php

141 ms

left-arrow.png

left-arrow.png

33 ms

widgets-ba0216eeacc7e4f2714a3ef157111951.css

widgets-ba0216eeacc7e4f2714a3ef157111951.css

32 ms

tab.js

tab.js

108 ms

SEO Factors

indigovapor.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 Indigovapor.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 Indigovapor.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

indigovapor.com

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