Tools & Wizards About Us
lovesick.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lovesick.jp

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

Page Load Speed

10.3 sec in total

First Response

539 ms

Resources Loaded

9.4 sec

Page Rendered

312 ms

lovesick.jp screenshot

About Website

Visit lovesick.jp now to see the best up-to-date Lovesick content for India and also check out these interesting facts you probably never knew about lovesick.jp

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

Visit lovesick.jp

Key Findings

We analyzed Lovesick.jp page load time and found that the first response time was 539 ms and then it took 9.7 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

lovesick.jp performance score

0

Network Requests Diagram

lovesick.jp

539 ms

lolipop.jp

1425 ms

default.css

302 ms

common.css

618 ms

background.css

481 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lovesick.jp, 56% (71 requests) were made to Lolipop.jp and 4% (5 requests) were made to Cache.img.gmo.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

784.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lovesick.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. 35% 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.3 kB

  • Original 168.3 kB
  • After minification 158.2 kB
  • After compression 25.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. 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.3 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, Lovesick 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.5 kB
  • After minification 231.8 kB
  • After compression 159.5 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. Lovesick.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 Lovesick. 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

lovesick.jp

lovesick.jp

539 ms

lolipop.jp

lolipop.jp

1425 ms

default.css

default.css

302 ms

common.css

common.css

618 ms

background.css

background.css

481 ms

text_m.css

text_m.css

513 ms

home.css

home.css

684 ms

lightbox.css

lightbox.css

538 ms

owl.carousel.css

owl.carousel.css

545 ms

jquery.min.js

jquery.min.js

61 ms

base.js

base.js

831 ms

lightbox.min.js

lightbox.min.js

847 ms

owl.carousel.min.js

owl.carousel.min.js

1034 ms

home.js

home.js

850 ms

scrollReveal.min.js

scrollReveal.min.js

845 ms

pixel.js

pixel.js

1002 ms

mixpanel.js

mixpanel.js

849 ms

fbds.js

fbds.js

86 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

126 ms

bg_night.gif

bg_night.gif

429 ms

close.png

close.png

426 ms

loading.gif

loading.gif

445 ms

prev.png

prev.png

462 ms

next.png

next.png

453 ms

bg_content_side.png

bg_content_side.png

583 ms

bg_main_bottom.gif

bg_main_bottom.gif

589 ms

bg_main_1column.png

bg_main_1column.png

615 ms

bg_submenu_top.gif

bg_submenu_top.gif

636 ms

h2_home_title.png

h2_home_title.png

1004 ms

megaphone.svg

megaphone.svg

651 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

742 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

751 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

788 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

807 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

832 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1054 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

912 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1632 ms

h3_home_title.png

h3_home_title.png

1775 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1646 ms

line_dot_11.gif

line_dot_11.gif

1273 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1477 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1446 ms

obj_home_feature_support.png

obj_home_feature_support.png

1755 ms

h3_home_functions.png

h3_home_functions.png

1618 ms

obj_home_functions_list.png

obj_home_functions_list.png

1842 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1809 ms

btn_infomation_more.png

btn_infomation_more.png

1824 ms

badge_light.png

badge_light.png

130 ms

widgets.js

widgets.js

81 ms

line_dot_02.gif

line_dot_02.gif

1773 ms

129 ms

47 ms

dc.js

dc.js

63 ms

icon_star.gif

icon_star.gif

1644 ms

btn_h_serch.png

btn_h_serch.png

1679 ms

line_dot_08.gif

line_dot_08.gif

1701 ms

btn_pagetop.gif

btn_pagetop.gif

1924 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2175 ms

__utm.gif

__utm.gif

17 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

21 ms

__utm.gif

__utm.gif

31 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2006 ms

obj_header_banner_text.png

obj_header_banner_text.png

2268 ms

btn_header_order.png

btn_header_order.png

2169 ms

bg_header_simple.png

bg_header_simple.png

2455 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1983 ms

obj_order_count_text.png

obj_order_count_text.png

2007 ms

obj_numbers.png

obj_numbers.png

1991 ms

menu_btn.png

menu_btn.png

2173 ms

menu_dot.gif

menu_dot.gif

2074 ms

arrow_menu.gif

arrow_menu.gif

2030 ms

obj_logo_ppb.png

obj_logo_ppb.png

2119 ms

pixel

pixel

153 ms

pixel

pixel

54 ms

Pug

Pug

58 ms

sync.ad-stir.com

sync.ad-stir.com

628 ms

sync

sync

50 ms

sync

sync

745 ms

is

is

755 ms

headerstyle.min.css

headerstyle.min.css

159 ms

google

google

153 ms

sd

sd

28 ms

tag.js

tag.js

44 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

6 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

1479 ms

obj_next_item_icon.png

obj_next_item_icon.png

1547 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1917 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1793 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1822 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1844 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

21 ms

tag

tag

58 ms

jot

jot

86 ms

lolipop.jp

lolipop.jp

1338 ms

lolipop.jp

lolipop.jp

2470 ms

lolipop.jp

lolipop.jp

1605 ms

lolipop.jp

lolipop.jp

2146 ms

lolipop.jp

lolipop.jp

1077 ms

nr-768.min.js

nr-768.min.js

45 ms

roundtrip.js

roundtrip.js

405 ms

btn.png

btn.png

33 ms

conversion_async.js

conversion_async.js

47 ms

45 ms

logo201601.png

logo201601.png

51 ms

open_footer.png

open_footer.png

80 ms

close_footer.png

close_footer.png

112 ms

15936ac739

15936ac739

123 ms

49 ms

conversion.js

conversion.js

961 ms

40 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

94 ms

out

out

20 ms

tr

tr

26 ms

out

out

11 ms

30 ms

u.php

u.php

68 ms

sd

sd

64 ms

sd

sd

48 ms

pixel

pixel

21 ms

sync

sync

17 ms

in

in

6 ms

377928.gif

377928.gif

11 ms

tap.php

tap.php

12 ms

conversion.js

conversion.js

952 ms

in

in

6 ms

SEO Factors

lovesick.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 Lovesick.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 Lovesick.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

lovesick.jp

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