Tools & Wizards About Us
pinoko.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pinoko.jp

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

Page Load Speed

14.9 sec in total

First Response

605 ms

Resources Loaded

10.7 sec

Page Rendered

3.6 sec

pinoko.jp screenshot

About Website

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

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

Visit pinoko.jp

Key Findings

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

pinoko.jp performance score

0

Network Requests Diagram

pinoko.jp

605 ms

lolipop.jp

1441 ms

default.css

774 ms

common.css

914 ms

background.css

769 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 Pinoko.jp, 57% (70 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.8 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

778.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pinoko.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. 50% of websites need less resources to load. Images take 702.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 142.1 kB

  • Original 166.7 kB
  • After minification 156.3 kB
  • After compression 24.6 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 142.1 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 125.4 kB

  • Original 702.8 kB
  • After minification 577.4 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, Pinoko 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.4 kB

  • Original 269.1 kB
  • After minification 268.4 kB
  • After compression 158.7 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.4 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. Pinoko.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 63 (56%)

Requests Now

113

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pinoko. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pinoko.jp

pinoko.jp

605 ms

lolipop.jp

lolipop.jp

1441 ms

default.css

default.css

774 ms

common.css

common.css

914 ms

background.css

background.css

769 ms

text_m.css

text_m.css

865 ms

home.css

home.css

783 ms

lightbox.css

lightbox.css

868 ms

owl.carousel.css

owl.carousel.css

1724 ms

jquery.min.js

jquery.min.js

81 ms

base.js

base.js

2092 ms

lightbox.min.js

lightbox.min.js

2065 ms

owl.carousel.min.js

owl.carousel.min.js

2166 ms

home.js

home.js

2090 ms

scrollReveal.min.js

scrollReveal.min.js

2063 ms

pixel.js

pixel.js

699 ms

mixpanel.js

mixpanel.js

2164 ms

fbds.js

fbds.js

1022 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

576 ms

bg_night.gif

bg_night.gif

1157 ms

close.png

close.png

1155 ms

loading.gif

loading.gif

1155 ms

prev.png

prev.png

1154 ms

next.png

next.png

1154 ms

bg_content_side.png

bg_content_side.png

1155 ms

bg_main_bottom.gif

bg_main_bottom.gif

1513 ms

bg_main_1column.png

bg_main_1column.png

1513 ms

bg_submenu_top.gif

bg_submenu_top.gif

1497 ms

h2_home_title.png

h2_home_title.png

1590 ms

megaphone.svg

megaphone.svg

1528 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

1513 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

1591 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

1606 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

1588 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

1606 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1590 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

1781 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

2359 ms

h3_home_title.png

h3_home_title.png

2102 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

2059 ms

line_dot_11.gif

line_dot_11.gif

1753 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

2090 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

2145 ms

obj_home_feature_support.png

obj_home_feature_support.png

2432 ms

h3_home_functions.png

h3_home_functions.png

2358 ms

obj_home_functions_list.png

obj_home_functions_list.png

2513 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2316 ms

line_dot_02.gif

line_dot_02.gif

2481 ms

icon_star.gif

icon_star.gif

2480 ms

btn_h_serch.png

btn_h_serch.png

2453 ms

widgets.js

widgets.js

509 ms

line_dot_08.gif

line_dot_08.gif

2400 ms

btn_pagetop.gif

btn_pagetop.gif

2399 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2378 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2823 ms

dc.js

dc.js

350 ms

563 ms

499 ms

obj_header_banner_text.png

obj_header_banner_text.png

2207 ms

btn_header_order.png

btn_header_order.png

2302 ms

__utm.gif

__utm.gif

273 ms

__utm.gif

__utm.gif

170 ms

__utm.gif

__utm.gif

169 ms

__utm.gif

__utm.gif

169 ms

bg_header_simple.png

bg_header_simple.png

2559 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1894 ms

obj_order_count_text.png

obj_order_count_text.png

1964 ms

obj_numbers.png

obj_numbers.png

1986 ms

menu_btn.png

menu_btn.png

2126 ms

menu_dot.gif

menu_dot.gif

1998 ms

arrow_menu.gif

arrow_menu.gif

2060 ms

obj_logo_ppb.png

obj_logo_ppb.png

2072 ms

pixel

pixel

150 ms

Pug

Pug

671 ms

sync.ad-stir.com

sync.ad-stir.com

1185 ms

sync

sync

1489 ms

is

is

1675 ms

headerstyle.min.css

headerstyle.min.css

347 ms

pixel

pixel

361 ms

sync

sync

330 ms

tag.js

tag.js

615 ms

button.b059c0eb61ea902a882e5c5b3c66a17a.js

button.b059c0eb61ea902a882e5c5b3c66a17a.js

215 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

902 ms

obj_next_item_icon.png

obj_next_item_icon.png

972 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1149 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1172 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1217 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1312 ms

google

google

261 ms

follow_button.baa54ded21a982344c4ced326592f3de.ja.html

follow_button.baa54ded21a982344c4ced326592f3de.ja.html

97 ms

sd

sd

436 ms

tag

tag

242 ms

lolipop.jp

lolipop.jp

1077 ms

lolipop.jp

lolipop.jp

1217 ms

lolipop.jp

lolipop.jp

1491 ms

lolipop.jp

lolipop.jp

1337 ms

jot

jot

221 ms

lolipop.jp

lolipop.jp

1145 ms

nr-768.min.js

nr-768.min.js

238 ms

roundtrip.js

roundtrip.js

283 ms

btn.png

btn.png

81 ms

conversion_async.js

conversion_async.js

314 ms

156 ms

logo201601.png

logo201601.png

107 ms

open_footer.png

open_footer.png

166 ms

close_footer.png

close_footer.png

202 ms

15936ac739

15936ac739

345 ms

conversion.js

conversion.js

1723 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

111 ms

95 ms

out

out

30 ms

tr

tr

28 ms

65 ms

out

out

45 ms

125 ms

u.php

u.php

126 ms

sd

sd

368 ms

sd

sd

247 ms

Pug

Pug

215 ms

in

in

34 ms

377928.gif

377928.gif

19 ms

tap.php

tap.php

249 ms

in

in

6 ms

SEO Factors

pinoko.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 Pinoko.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 Pinoko.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

pinoko.jp

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