Tools & Wizards About Us
heavy.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

heavy.jp

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

Page Load Speed

12.3 sec in total

First Response

500 ms

Resources Loaded

11.3 sec

Page Rendered

448 ms

heavy.jp screenshot

About Website

Welcome to heavy.jp homepage info - get ready to check Heavy best content for Japan right away, or after learning these important things about heavy.jp

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

Visit heavy.jp

Key Findings

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

heavy.jp performance score

0

Network Requests Diagram

heavy.jp

500 ms

lolipop.jp

1462 ms

default.css

362 ms

common.css

626 ms

background.css

487 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Heavy.jp, 57% (70 requests) were made to Lolipop.jp and 7% (8 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 388.6 kB (33%)

Content Size

1.2 MB

After Optimization

780.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heavy.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

-81%

Potential reduce by 101.8 kB

  • Original 125.1 kB
  • After minification 116.0 kB
  • After compression 23.3 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 101.8 kB or 81% 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, Heavy 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 88.3 kB

  • Original 104.1 kB
  • After minification 73.8 kB
  • After compression 15.8 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. Heavy.jp needs all CSS files to be minified and compressed as it can save up to 88.3 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heavy.jp

heavy.jp

500 ms

lolipop.jp

lolipop.jp

1462 ms

default.css

default.css

362 ms

common.css

common.css

626 ms

background.css

background.css

487 ms

text_m.css

text_m.css

501 ms

home.css

home.css

504 ms

lightbox.css

lightbox.css

548 ms

owl.carousel.css

owl.carousel.css

549 ms

jquery.min.js

jquery.min.js

65 ms

base.js

base.js

638 ms

lightbox.min.js

lightbox.min.js

530 ms

owl.carousel.min.js

owl.carousel.min.js

557 ms

home.js

home.js

571 ms

scrollReveal.min.js

scrollReveal.min.js

570 ms

pixel.js

pixel.js

746 ms

mixpanel.js

mixpanel.js

611 ms

fbds.js

fbds.js

130 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

282 ms

bg_night.gif

bg_night.gif

193 ms

close.png

close.png

273 ms

loading.gif

loading.gif

288 ms

prev.png

prev.png

287 ms

bg_content_side.png

bg_content_side.png

325 ms

bg_main_bottom.gif

bg_main_bottom.gif

360 ms

bg_main_1column.png

bg_main_1column.png

426 ms

bg_submenu_top.gif

bg_submenu_top.gif

463 ms

h2_home_title.png

h2_home_title.png

655 ms

megaphone.svg

megaphone.svg

459 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

492 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

527 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

595 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

617 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

648 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

652 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

694 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1266 ms

h3_home_title.png

h3_home_title.png

1085 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1201 ms

line_dot_11.gif

line_dot_11.gif

816 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1028 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1027 ms

obj_home_feature_support.png

obj_home_feature_support.png

1305 ms

h3_home_functions.png

h3_home_functions.png

2600 ms

obj_home_functions_list.png

obj_home_functions_list.png

2793 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2596 ms

btn_infomation_more.png

btn_infomation_more.png

2612 ms

badge_light.png

badge_light.png

91 ms

widgets.js

widgets.js

57 ms

line_dot_02.gif

line_dot_02.gif

2557 ms

icon_star.gif

icon_star.gif

3551 ms

btn_h_serch.png

btn_h_serch.png

3565 ms

line_dot_08.gif

line_dot_08.gif

3558 ms

btn_pagetop.gif

btn_pagetop.gif

3555 ms

28 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

3709 ms

dc.js

dc.js

65 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

3679 ms

obj_header_banner_text.png

obj_header_banner_text.png

3791 ms

__utm.gif

__utm.gif

14 ms

__utm.gif

__utm.gif

18 ms

__utm.gif

__utm.gif

27 ms

__utm.gif

__utm.gif

38 ms

24 ms

btn_header_order.png

btn_header_order.png

4320 ms

bg_header_simple.png

bg_header_simple.png

4555 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

4038 ms

obj_order_count_text.png

obj_order_count_text.png

4170 ms

obj_numbers.png

obj_numbers.png

4155 ms

menu_btn.png

menu_btn.png

4510 ms

menu_dot.gif

menu_dot.gif

4100 ms

arrow_menu.gif

arrow_menu.gif

4190 ms

obj_logo_ppb.png

obj_logo_ppb.png

4175 ms

pixel

pixel

161 ms

pixel

pixel

105 ms

Pug

Pug

124 ms

sync.ad-stir.com

sync.ad-stir.com

668 ms

sync

sync

76 ms

sync

sync

932 ms

is

is

1158 ms

tag.js

tag.js

61 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

3678 ms

obj_next_item_icon.png

obj_next_item_icon.png

3698 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

3987 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

3982 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

4034 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

4072 ms

sd

sd

6 ms

tag

tag

274 ms

pixel

pixel

20 ms

google

google

160 ms

lolipop.jp

lolipop.jp

2769 ms

lolipop.jp

lolipop.jp

1850 ms

lolipop.jp

lolipop.jp

1768 ms

lolipop.jp

lolipop.jp

1951 ms

lolipop.jp

lolipop.jp

1719 ms

nr-768.min.js

nr-768.min.js

49 ms

roundtrip.js

roundtrip.js

89 ms

conversion_async.js

conversion_async.js

49 ms

7 ms

15936ac739

15936ac739

111 ms

30 ms

conversion.js

conversion.js

814 ms

38 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

114 ms

out

out

17 ms

tr

tr

16 ms

out

out

19 ms

out

out

23 ms

out

out

29 ms

out

out

28 ms

out

out

28 ms

sync

sync

7 ms

u.php

u.php

40 ms

27 ms

sd

sd

37 ms

sd

sd

19 ms

pixel

pixel

32 ms

377928.gif

377928.gif

11 ms

in

in

6 ms

tap.php

tap.php

179 ms

conversion.js

conversion.js

990 ms

in

in

5 ms

SEO Factors

heavy.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 Heavy.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 Heavy.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

heavy.jp

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