Tools & Wizards About Us
punyu.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

punyu.jp

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

Page Load Speed

14 sec in total

First Response

523 ms

Resources Loaded

13 sec

Page Rendered

483 ms

punyu.jp screenshot

About Website

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

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

Visit punyu.jp

Key Findings

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

punyu.jp performance score

0

Network Requests Diagram

punyu.jp

523 ms

lolipop.jp

1408 ms

default.css

327 ms

common.css

1022 ms

background.css

866 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 441.1 kB (37%)

Content Size

1.2 MB

After Optimization

762.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

  • Original 169.7 kB
  • After minification 159.6 kB
  • After compression 25.2 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 144.5 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, Punyu 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

-35%

Potential reduce by 72.7 kB

  • Original 209.9 kB
  • After minification 209.2 kB
  • After compression 137.2 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 72.7 kB or 35% 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. Punyu.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 69 (58%)

Requests Now

120

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

punyu.jp

punyu.jp

523 ms

lolipop.jp

lolipop.jp

1408 ms

default.css

default.css

327 ms

common.css

common.css

1022 ms

background.css

background.css

866 ms

text_m.css

text_m.css

1828 ms

home.css

home.css

1832 ms

lightbox.css

lightbox.css

1838 ms

owl.carousel.css

owl.carousel.css

1847 ms

jquery.min.js

jquery.min.js

25 ms

base.js

base.js

1872 ms

lightbox.min.js

lightbox.min.js

2672 ms

owl.carousel.min.js

owl.carousel.min.js

2846 ms

home.js

home.js

2683 ms

scrollreveal.min.js

scrollreveal.min.js

2683 ms

pixel.js

pixel.js

630 ms

mixpanel.js

mixpanel.js

2691 ms

fbds.js

fbds.js

1282 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

144 ms

bg_body.gif

bg_body.gif

969 ms

close.png

close.png

1127 ms

loading.gif

loading.gif

1131 ms

prev.png

prev.png

1140 ms

next.png

next.png

1136 ms

bg_content_side.png

bg_content_side.png

1155 ms

bg_main_bottom.gif

bg_main_bottom.gif

1295 ms

bg_main_1column.png

bg_main_1column.png

1295 ms

bg_submenu_top.gif

bg_submenu_top.gif

1304 ms

h2_home_title.png

h2_home_title.png

1636 ms

megaphone.svg

megaphone.svg

1310 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

1336 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

1461 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

1461 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

1469 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

1485 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1693 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

1625 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

2156 ms

h3_home_title.png

h3_home_title.png

2303 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

2165 ms

line_dot_11.gif

line_dot_11.gif

1814 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1985 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

2050 ms

obj_home_feature_support.png

obj_home_feature_support.png

2320 ms

h3_home_functions.png

h3_home_functions.png

2161 ms

obj_home_functions_list.png

obj_home_functions_list.png

2413 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2375 ms

btn_infomation_more.png

btn_infomation_more.png

2377 ms

badge_light.png

badge_light.png

111 ms

widgets.js

widgets.js

144 ms

line_dot_02.gif

line_dot_02.gif

2300 ms

28 ms

dc.js

dc.js

87 ms

icon_star.gif

icon_star.gif

2320 ms

__utm.gif

__utm.gif

20 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

21 ms

__utm.gif

__utm.gif

29 ms

btn_h_serch.png

btn_h_serch.png

1537 ms

line_dot_08.gif

line_dot_08.gif

1555 ms

btn_pagetop.gif

btn_pagetop.gif

1553 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1562 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1814 ms

obj_header_banner_text.png

obj_header_banner_text.png

1704 ms

btn_header_order.png

btn_header_order.png

1955 ms

94 ms

bg_header_simple.png

bg_header_simple.png

2031 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1674 ms

obj_order_count_text.png

obj_order_count_text.png

1696 ms

obj_numbers.png

obj_numbers.png

1690 ms

menu_btn.png

menu_btn.png

1853 ms

menu_dot.gif

menu_dot.gif

1685 ms

arrow_menu.gif

arrow_menu.gif

1708 ms

obj_logo_ppb.png

obj_logo_ppb.png

1702 ms

pixel

pixel

324 ms

pixel

pixel

77 ms

Pug

Pug

80 ms

getuid

getuid

85 ms

sync.ad-stir.com

sync.ad-stir.com

667 ms

sync

sync

1024 ms

is

is

1167 ms

headerstyle.min.css

headerstyle.min.css

213 ms

sync

sync

7 ms

pixel

pixel

14 ms

google

google

187 ms

sd

sd

24 ms

tag.js

tag.js

195 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

29 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

1593 ms

obj_next_item_icon.png

obj_next_item_icon.png

1597 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1952 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1766 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1778 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2007 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

48 ms

tag

tag

30 ms

jot

jot

103 ms

lolipop.jp

lolipop.jp

3171 ms

mapuser

mapuser

155 ms

lolipop.jp

lolipop.jp

3988 ms

lolipop.jp

lolipop.jp

4251 ms

lolipop.jp

lolipop.jp

3645 ms

lolipop.jp

lolipop.jp

1984 ms

nr-892.min.js

nr-892.min.js

60 ms

roundtrip.js

roundtrip.js

44 ms

btn.png

btn.png

36 ms

conversion_async.js

conversion_async.js

57 ms

36 ms

logo201601.png

logo201601.png

46 ms

open_footer.png

open_footer.png

80 ms

close_footer.png

close_footer.png

110 ms

15936ac739

15936ac739

122 ms

46 ms

conversion.js

conversion.js

853 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

186 ms

40 ms

fbevents.hashing.js

fbevents.hashing.js

81 ms

out

out

11 ms

34 ms

seg

seg

88 ms

out

out

6 ms

out

out

30 ms

out

out

28 ms

out

out

29 ms

out

out

28 ms

out

out

27 ms

out

out

27 ms

out

out

30 ms

u.php

u.php

69 ms

sd

sd

61 ms

pxj

pxj

17 ms

sd

sd

50 ms

44 ms

Pug

Pug

39 ms

in

in

25 ms

tap.php

tap.php

28 ms

28 ms

377928.gif

377928.gif

8 ms

conversion.js

conversion.js

980 ms

in

in

6 ms

SEO Factors

punyu.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 Punyu.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 Punyu.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

punyu.jp

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