Tools & Wizards About Us
hungry.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hungry.jp

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

Page Load Speed

10.9 sec in total

First Response

555 ms

Resources Loaded

10 sec

Page Rendered

376 ms

hungry.jp screenshot

About Website

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

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

Visit hungry.jp

Key Findings

We analyzed Hungry.jp page load time and found that the first response time was 555 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

hungry.jp performance score

0

Network Requests Diagram

hungry.jp

555 ms

lolipop.jp

1368 ms

default.css

331 ms

common.css

628 ms

background.css

475 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hungry.jp, 55% (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 (3.8 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 523.8 kB (40%)

Content Size

1.3 MB

After Optimization

784.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

-50%

Potential reduce by 156.6 kB

  • Original 316.0 kB
  • After minification 315.3 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 156.6 kB or 50% 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. Hungry.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 Hungry. 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

hungry.jp

hungry.jp

555 ms

lolipop.jp

lolipop.jp

1368 ms

default.css

default.css

331 ms

common.css

common.css

628 ms

background.css

background.css

475 ms

text_m.css

text_m.css

501 ms

home.css

home.css

506 ms

lightbox.css

lightbox.css

512 ms

owl.carousel.css

owl.carousel.css

522 ms

jquery.min.js

jquery.min.js

66 ms

base.js

base.js

660 ms

lightbox.min.js

lightbox.min.js

641 ms

owl.carousel.min.js

owl.carousel.min.js

697 ms

home.js

home.js

640 ms

scrollReveal.min.js

scrollReveal.min.js

639 ms

pixel.js

pixel.js

788 ms

mixpanel.js

mixpanel.js

656 ms

fbds.js

fbds.js

270 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

247 ms

bg_night.gif

bg_night.gif

305 ms

close.png

close.png

305 ms

loading.gif

loading.gif

306 ms

prev.png

prev.png

335 ms

next.png

next.png

333 ms

bg_content_side.png

bg_content_side.png

383 ms

bg_main_bottom.gif

bg_main_bottom.gif

457 ms

bg_main_1column.png

bg_main_1column.png

455 ms

bg_submenu_top.gif

bg_submenu_top.gif

458 ms

h2_home_title.png

h2_home_title.png

799 ms

megaphone.svg

megaphone.svg

493 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

551 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

625 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

628 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

632 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

650 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

886 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

796 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1314 ms

h3_home_title.png

h3_home_title.png

1318 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1119 ms

line_dot_11.gif

line_dot_11.gif

967 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1114 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1221 ms

obj_home_feature_support.png

obj_home_feature_support.png

1485 ms

h3_home_functions.png

h3_home_functions.png

1310 ms

obj_home_functions_list.png

obj_home_functions_list.png

1431 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1392 ms

btn_infomation_more.png

btn_infomation_more.png

1427 ms

badge_light.png

badge_light.png

294 ms

widgets.js

widgets.js

92 ms

line_dot_02.gif

line_dot_02.gif

1372 ms

icon_star.gif

icon_star.gif

1340 ms

btn_h_serch.png

btn_h_serch.png

1416 ms

line_dot_08.gif

line_dot_08.gif

1434 ms

btn_pagetop.gif

btn_pagetop.gif

1424 ms

dc.js

dc.js

76 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1632 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1613 ms

58 ms

__utm.gif

__utm.gif

35 ms

23 ms

__utm.gif

__utm.gif

28 ms

__utm.gif

__utm.gif

35 ms

__utm.gif

__utm.gif

36 ms

obj_header_banner_text.png

obj_header_banner_text.png

1607 ms

btn_header_order.png

btn_header_order.png

1824 ms

bg_header_simple.png

bg_header_simple.png

1925 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1740 ms

obj_order_count_text.png

obj_order_count_text.png

1625 ms

obj_numbers.png

obj_numbers.png

1596 ms

menu_btn.png

menu_btn.png

1828 ms

menu_dot.gif

menu_dot.gif

1623 ms

arrow_menu.gif

arrow_menu.gif

3062 ms

obj_logo_ppb.png

obj_logo_ppb.png

3056 ms

pixel

pixel

151 ms

pixel

pixel

53 ms

Pug

Pug

57 ms

sync.ad-stir.com

sync.ad-stir.com

615 ms

sync

sync

73 ms

sync

sync

1062 ms

is

is

1112 ms

headerstyle.min.css

headerstyle.min.css

205 ms

sd

sd

7 ms

pixel

pixel

22 ms

google

google

181 ms

tag.js

tag.js

59 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

7 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2393 ms

obj_next_item_icon.png

obj_next_item_icon.png

2395 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2731 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2570 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2693 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2696 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

18 ms

tag

tag

92 ms

jot

jot

90 ms

lolipop.jp

lolipop.jp

2657 ms

lolipop.jp

lolipop.jp

3800 ms

lolipop.jp

lolipop.jp

2755 ms

lolipop.jp

lolipop.jp

2950 ms

lolipop.jp

lolipop.jp

1300 ms

nr-768.min.js

nr-768.min.js

112 ms

roundtrip.js

roundtrip.js

46 ms

btn.png

btn.png

33 ms

conversion_async.js

conversion_async.js

48 ms

20 ms

logo201601.png

logo201601.png

51 ms

open_footer.png

open_footer.png

87 ms

close_footer.png

close_footer.png

118 ms

49 ms

conversion.js

conversion.js

850 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

5 ms

out

out

13 ms

tr

tr

13 ms

out

out

44 ms

out

out

51 ms

85 ms

15936ac739

15936ac739

134 ms

u.php

u.php

55 ms

sync

sync

39 ms

58 ms

sd

sd

50 ms

sd

sd

24 ms

in

in

6 ms

377928.gif

377928.gif

6 ms

tap.php

tap.php

285 ms

in

in

5 ms

conversion.js

conversion.js

1002 ms

SEO Factors

hungry.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 Hungry.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 Hungry.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

hungry.jp

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