Tools & Wizards About Us
hiho.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hiho.jp

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

Page Load Speed

11.4 sec in total

First Response

529 ms

Resources Loaded

10.5 sec

Page Rendered

397 ms

hiho.jp screenshot

About Website

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

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

Visit hiho.jp

Key Findings

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

hiho.jp performance score

0

Network Requests Diagram

hiho.jp

529 ms

lolipop.jp

1216 ms

default.css

327 ms

common.css

641 ms

background.css

488 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 Hiho.jp, 53% (71 requests) were made to Lolipop.jp and 8% (11 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 477.7 kB (38%)

Content Size

1.3 MB

After Optimization

784.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hiho.jp main page is 1.3 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.3 kB

  • Original 168.3 kB
  • After minification 158.1 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, Hiho 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

-41%

Potential reduce by 110.5 kB

  • Original 270.0 kB
  • After minification 269.3 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 110.5 kB or 41% 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. Hiho.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 Hiho. 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

hiho.jp

hiho.jp

529 ms

lolipop.jp

lolipop.jp

1216 ms

default.css

default.css

327 ms

common.css

common.css

641 ms

background.css

background.css

488 ms

text_m.css

text_m.css

500 ms

home.css

home.css

518 ms

lightbox.css

lightbox.css

516 ms

owl.carousel.css

owl.carousel.css

538 ms

jquery.min.js

jquery.min.js

58 ms

base.js

base.js

575 ms

lightbox.min.js

lightbox.min.js

576 ms

owl.carousel.min.js

owl.carousel.min.js

627 ms

home.js

home.js

626 ms

scrollReveal.min.js

scrollReveal.min.js

943 ms

pixel.js

pixel.js

629 ms

mixpanel.js

mixpanel.js

951 ms

fbds.js

fbds.js

312 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

135 ms

bg_night.gif

bg_night.gif

454 ms

close.png

close.png

461 ms

loading.gif

loading.gif

470 ms

prev.png

prev.png

468 ms

next.png

next.png

1455 ms

bg_content_side.png

bg_content_side.png

1422 ms

bg_main_bottom.gif

bg_main_bottom.gif

1426 ms

bg_main_1column.png

bg_main_1column.png

1451 ms

bg_submenu_top.gif

bg_submenu_top.gif

1452 ms

h2_home_title.png

h2_home_title.png

1783 ms

megaphone.svg

megaphone.svg

1584 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

1588 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

2435 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

2438 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

2454 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

2441 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

2446 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

2454 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

3108 ms

h3_home_title.png

h3_home_title.png

2985 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

2922 ms

line_dot_11.gif

line_dot_11.gif

2609 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

3278 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

3090 ms

obj_home_feature_support.png

obj_home_feature_support.png

3298 ms

h3_home_functions.png

h3_home_functions.png

3423 ms

obj_home_functions_list.png

obj_home_functions_list.png

3600 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

3438 ms

btn_infomation_more.png

btn_infomation_more.png

3436 ms

badge_light.png

badge_light.png

115 ms

line_dot_02.gif

line_dot_02.gif

3398 ms

icon_star.gif

icon_star.gif

3402 ms

widgets.js

widgets.js

188 ms

btn_h_serch.png

btn_h_serch.png

3516 ms

dc.js

dc.js

73 ms

line_dot_08.gif

line_dot_08.gif

3497 ms

btn_pagetop.gif

btn_pagetop.gif

3500 ms

35 ms

__utm.gif

__utm.gif

26 ms

__utm.gif

__utm.gif

25 ms

__utm.gif

__utm.gif

33 ms

__utm.gif

__utm.gif

53 ms

108 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

3387 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

3350 ms

obj_header_banner_text.png

obj_header_banner_text.png

3462 ms

pixel

pixel

151 ms

Pug

Pug

88 ms

sync.ad-stir.com

sync.ad-stir.com

617 ms

sync

sync

71 ms

sync

sync

949 ms

is

is

1264 ms

headerstyle.min.css

headerstyle.min.css

174 ms

pixel

pixel

29 ms

sd

sd

5 ms

google

google

160 ms

tag.js

tag.js

41 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

44 ms

btn_header_order.png

btn_header_order.png

2701 ms

bg_header_simple.png

bg_header_simple.png

2941 ms

tag

tag

46 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2602 ms

obj_order_count_text.png

obj_order_count_text.png

2622 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

54 ms

obj_numbers.png

obj_numbers.png

2529 ms

menu_btn.png

menu_btn.png

2807 ms

jot

jot

100 ms

menu_dot.gif

menu_dot.gif

2460 ms

arrow_menu.gif

arrow_menu.gif

1857 ms

obj_logo_ppb.png

obj_logo_ppb.png

1845 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

1900 ms

obj_next_item_icon.png

obj_next_item_icon.png

1958 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2159 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2183 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2076 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1803 ms

lolipop.jp

lolipop.jp

1201 ms

lolipop.jp

lolipop.jp

1771 ms

lolipop.jp

lolipop.jp

1441 ms

lolipop.jp

lolipop.jp

1802 ms

lolipop.jp

lolipop.jp

1018 ms

nr-768.min.js

nr-768.min.js

68 ms

roundtrip.js

roundtrip.js

172 ms

btn.png

btn.png

33 ms

conversion_async.js

conversion_async.js

42 ms

38 ms

logo201601.png

logo201601.png

49 ms

open_footer.png

open_footer.png

78 ms

close_footer.png

close_footer.png

111 ms

conversion.js

conversion.js

938 ms

15936ac739

15936ac739

128 ms

49 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

136 ms

out

out

6 ms

tr

tr

38 ms

36 ms

out

out

5 ms

out

out

10 ms

out

out

32 ms

out

out

32 ms

out

out

32 ms

out

out

31 ms

out

out

31 ms

out

out

31 ms

u.php

u.php

75 ms

sync

sync

27 ms

sd

sd

16 ms

sd

sd

113 ms

pixel

pixel

15 ms

23 ms

in

in

10 ms

377928.gif

377928.gif

6 ms

tap.php

tap.php

57 ms

conversion.js

conversion.js

999 ms

in

in

3 ms

SEO Factors

hiho.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 Hiho.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 Hiho.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

hiho.jp

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