Tools & Wizards About Us
vivexin.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vivexin.com

Vivexin - Anti Aging Skin Cream

Page Load Speed

2.6 sec in total

First Response

156 ms

Resources Loaded

1.8 sec

Page Rendered

638 ms

vivexin.com screenshot

About Website

Click here to check amazing Vivexin content. Otherwise, check out these important facts you probably never knew about vivexin.com

Vivexin has succeeded at creating an intensive eye cream to effectively combat not one but three of the most aggravating beauty problems dark under eye circles, fine lines, wrinkles, and appearance of...

Visit vivexin.com

Key Findings

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

Performance Metrics

vivexin.com performance score

0

Network Requests Diagram

vivexin.com

156 ms

www.vivexin.com

198 ms

redirection-mobile_1.js

111 ms

default.css

131 ms

style.css

131 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 73% of them (60 requests) were addressed to the original Vivexin.com, 9% (7 requests) were made to Seal.buysafe.com and 4% (3 requests) were made to Tags.mediaforge.com. The less responsive or slowest element that took the longest time to load (971 ms) belongs to the original domain Vivexin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.7 kB (13%)

Content Size

893.4 kB

After Optimization

780.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 18.8 kB

  • Original 26.3 kB
  • After minification 25.1 kB
  • After compression 7.5 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 18.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 10.1 kB

  • Original 719.1 kB
  • After minification 709.0 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. Vivexin images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 74.8 kB

  • Original 135.5 kB
  • After minification 132.8 kB
  • After compression 60.6 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 74.8 kB or 55% of the original size.

CSS Optimization

-71%

Potential reduce by 8.9 kB

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 3.6 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. Vivexin.com needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (30%)

Requests Now

76

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vivexin.com

vivexin.com

156 ms

www.vivexin.com

www.vivexin.com

198 ms

redirection-mobile_1.js

redirection-mobile_1.js

111 ms

default.css

default.css

131 ms

style.css

style.css

131 ms

varA.css

varA.css

132 ms

styles.css

styles.css

168 ms

conversion.js

conversion.js

27 ms

rollover.js

rollover.js

68 ms

600

600

405 ms

speedwinds-nutrition-37005337.png

speedwinds-nutrition-37005337.png

106 ms

top-bottle-link.jpg

top-bottle-link.jpg

114 ms

02_01.jpg

02_01.jpg

154 ms

02_02.jpg

02_02.jpg

153 ms

02_03.jpg

02_03.jpg

209 ms

02_04.jpg

02_04.jpg

156 ms

02_06.jpg

02_06.jpg

178 ms

02_07.jpg

02_07.jpg

257 ms

before-after.jpg

before-after.jpg

317 ms

02_09.jpg

02_09.jpg

282 ms

02_10.jpg

02_10.jpg

283 ms

02_13.jpg

02_13.jpg

323 ms

02_17.jpg

02_17.jpg

353 ms

03_01.jpg

03_01.jpg

365 ms

03_03.jpg

03_03.jpg

440 ms

03_04.jpg

03_04.jpg

427 ms

03_05.jpg

03_05.jpg

571 ms

04_01_02.jpg

04_01_02.jpg

467 ms

f-a-q.jpg

f-a-q.jpg

479 ms

04_08.jpg

04_08.jpg

491 ms

guarantee.jpg

guarantee.jpg

547 ms

90-day.jpg

90-day.jpg

572 ms

bottom_03.jpg

bottom_03.jpg

657 ms

bottom_07.jpg

bottom_07.jpg

586 ms

bottom_08.jpg

bottom_08.jpg

651 ms

vivexin-6mo.jpg

vivexin-6mo.jpg

654 ms

vivexin-3mo.jpg

vivexin-3mo.jpg

679 ms

vivexin-1mo.jpg

vivexin-1mo.jpg

713 ms

trust-e.gif

trust-e.gif

712 ms

speedwinds-nutrition-37005337.js

speedwinds-nutrition-37005337.js

52 ms

clouds.jpg

clouds.jpg

736 ms

top_bg.jpg

top_bg.jpg

971 ms

clickhere.png

clickhere.png

753 ms

clickhere-hover.png

clickhere-hover.png

740 ms

02_05.jpg

02_05.jpg

793 ms

03_02.jpg

03_02.jpg

812 ms

04_01.jpg

04_01.jpg

925 ms

04_02.jpg

04_02.jpg

859 ms

ga.js

ga.js

7 ms

53 ms

04_03.jpg

04_03.jpg

827 ms

__utm.gif

__utm.gif

13 ms

04_04.jpg

04_04.jpg

842 ms

04_05.jpg

04_05.jpg

825 ms

04_06.jpg

04_06.jpg

908 ms

30 ms

04_05_02.jpg

04_05_02.jpg

891 ms

49 ms

04_07.jpg

04_07.jpg

878 ms

rollover.core.js

rollover.core.js

6 ms

ii.aspx

ii.aspx

10 ms

AltSealInfo.aspx

AltSealInfo.aspx

24 ms

bottom_01.jpg

bottom_01.jpg

850 ms

PersistentSeal_BRL.png

PersistentSeal_BRL.png

13 ms

bottom_02.jpg

bottom_02.jpg

900 ms

Static.aspx

Static.aspx

54 ms

bottom_04.jpg

bottom_04.jpg

883 ms

bottom_05.jpg

bottom_05.jpg

936 ms

6mo-button-hover.png

6mo-button-hover.png

894 ms

rollover_2008_01.png

rollover_2008_01.png

8 ms

600

600

177 ms

6mo-button.png

6mo-button.png

858 ms

3mo-button-hover.png

3mo-button-hover.png

849 ms

3mo-button.png

3mo-button.png

872 ms

1mo-button-hover.png

1mo-button-hover.png

871 ms

1mo-button.png

1mo-button.png

853 ms

visa-mc-amex-discover-echeck.gif

visa-mc-amex-discover-echeck.gif

883 ms

generic

generic

13 ms

tap.php

tap.php

4 ms

generic

generic

4 ms

cs

cs

88 ms

pixel

pixel

15 ms

SEO Factors

vivexin.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

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

Social Sharing Optimization

vivexin.com

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