Tools & Wizards About Us
vivian.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vivian.jp

ロリポップ！レンタルサーバー | 利用実績170万人突破！無料SSLあり

Page Load Speed

10.8 sec in total

First Response

536 ms

Resources Loaded

9.9 sec

Page Rendered

373 ms

vivian.jp screenshot

About Website

Click here to check amazing Vivian content for Japan. Otherwise, check out these important facts you probably never knew about vivian.jp

ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ！」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。

Visit vivian.jp

Key Findings

We analyzed Vivian.jp page load time and found that the first response time was 536 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

vivian.jp performance score

0

Network Requests Diagram

vivian.jp

536 ms

lolipop.jp

1212 ms

default.css

329 ms

common.css

637 ms

background.css

500 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vivian.jp, 53% (71 requests) were made to Lolipop.jp and 9% (12 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.1 kB (36%)

Content Size

1.2 MB

After Optimization

784.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vivian.jp 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. 40% of websites need less resources to load. Images take 707.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 143.2 kB

  • Original 168.1 kB
  • After minification 158.0 kB
  • After compression 24.9 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 143.2 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 125.4 kB

  • Original 707.6 kB
  • After minification 582.1 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. Obviously, Vivian needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-31%

Potential reduce by 73.0 kB

  • Original 232.4 kB
  • After minification 231.6 kB
  • After compression 159.4 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 73.0 kB or 31% of the original size.

CSS Optimization

-85%

Potential reduce by 98.4 kB

  • Original 116.5 kB
  • After minification 86.2 kB
  • After compression 18.0 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. Vivian.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (57%)

Requests Now

115

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vivian.jp

vivian.jp

536 ms

lolipop.jp

lolipop.jp

1212 ms

default.css

default.css

329 ms

common.css

common.css

637 ms

background.css

background.css

500 ms

text_m.css

text_m.css

509 ms

home.css

home.css

683 ms

lightbox.css

lightbox.css

563 ms

owl.carousel.css

owl.carousel.css

567 ms

jquery.min.js

jquery.min.js

82 ms

base.js

base.js

712 ms

lightbox.min.js

lightbox.min.js

525 ms

owl.carousel.min.js

owl.carousel.min.js

777 ms

home.js

home.js

627 ms

scrollReveal.min.js

scrollReveal.min.js

685 ms

pixel.js

pixel.js

710 ms

mixpanel.js

mixpanel.js

727 ms

fbds.js

fbds.js

323 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

149 ms

bg_body.gif

bg_body.gif

344 ms

close.png

close.png

237 ms

loading.gif

loading.gif

262 ms

prev.png

prev.png

329 ms

next.png

next.png

330 ms

bg_content_side.png

bg_content_side.png

411 ms

bg_main_bottom.gif

bg_main_bottom.gif

421 ms

bg_main_1column.png

bg_main_1column.png

409 ms

bg_submenu_top.gif

bg_submenu_top.gif

500 ms

h2_home_title.png

h2_home_title.png

837 ms

megaphone.svg

megaphone.svg

513 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

569 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

594 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

607 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

669 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

687 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

885 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

777 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1342 ms

h3_home_title.png

h3_home_title.png

1225 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1229 ms

line_dot_11.gif

line_dot_11.gif

962 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1227 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1228 ms

obj_home_feature_support.png

obj_home_feature_support.png

1510 ms

h3_home_functions.png

h3_home_functions.png

1373 ms

obj_home_functions_list.png

obj_home_functions_list.png

1538 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1374 ms

btn_infomation_more.png

btn_infomation_more.png

1361 ms

line_dot_02.gif

line_dot_02.gif

1525 ms

badge_light.png

badge_light.png

179 ms

icon_star.gif

icon_star.gif

1454 ms

widgets.js

widgets.js

170 ms

btn_h_serch.png

btn_h_serch.png

1469 ms

line_dot_08.gif

line_dot_08.gif

1420 ms

39 ms

dc.js

dc.js

90 ms

btn_pagetop.gif

btn_pagetop.gif

1526 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1665 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1674 ms

__utm.gif

__utm.gif

24 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

32 ms

101 ms

obj_header_banner_text.png

obj_header_banner_text.png

1814 ms

btn_header_order.png

btn_header_order.png

2254 ms

bg_header_simple.png

bg_header_simple.png

2616 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2282 ms

obj_order_count_text.png

obj_order_count_text.png

2053 ms

obj_numbers.png

obj_numbers.png

2038 ms

menu_btn.png

menu_btn.png

2310 ms

menu_dot.gif

menu_dot.gif

2148 ms

arrow_menu.gif

arrow_menu.gif

2136 ms

obj_logo_ppb.png

obj_logo_ppb.png

2152 ms

pixel

pixel

153 ms

Pug

Pug

81 ms

sync.ad-stir.com

sync.ad-stir.com

639 ms

sync

sync

90 ms

sync

sync

708 ms

is

is

790 ms

headerstyle.min.css

headerstyle.min.css

160 ms

pixel

pixel

17 ms

google

google

153 ms

sd

sd

30 ms

tag.js

tag.js

72 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

39 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2294 ms

obj_next_item_icon.png

obj_next_item_icon.png

2309 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2498 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2459 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2479 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2488 ms

tag

tag

35 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

50 ms

jot

jot

95 ms

lolipop.jp

lolipop.jp

2521 ms

lolipop.jp

lolipop.jp

2797 ms

lolipop.jp

lolipop.jp

3175 ms

lolipop.jp

lolipop.jp

3353 ms

lolipop.jp

lolipop.jp

1837 ms

nr-768.min.js

nr-768.min.js

122 ms

roundtrip.js

roundtrip.js

43 ms

btn.png

btn.png

35 ms

conversion_async.js

conversion_async.js

46 ms

29 ms

logo201601.png

logo201601.png

54 ms

open_footer.png

open_footer.png

88 ms

close_footer.png

close_footer.png

133 ms

61 ms

conversion.js

conversion.js

902 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

5 ms

out

out

9 ms

tr

tr

50 ms

out

out

15 ms

out

out

44 ms

out

out

45 ms

out

out

46 ms

out

out

52 ms

out

out

51 ms

out

out

57 ms

out

out

57 ms

out

out

57 ms

99 ms

15936ac739

15936ac739

141 ms

76 ms

u.php

u.php

66 ms

sync

sync

31 ms

sd

sd

60 ms

sd

sd

52 ms

in

in

10 ms

377928.gif

377928.gif

6 ms

tap.php

tap.php

462 ms

in

in

6 ms

conversion.js

conversion.js

1018 ms

SEO Factors

vivian.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivian.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Vivian.jp 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

vivian.jp

Open Graph data is detected on the main page of Vivian. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: