Tools & Wizards About Us
pecori.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pecori.jp

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

Page Load Speed

11.3 sec in total

First Response

498 ms

Resources Loaded

10.4 sec

Page Rendered

349 ms

pecori.jp screenshot

About Website

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

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

Visit pecori.jp

Key Findings

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

pecori.jp performance score

0

Network Requests Diagram

pecori.jp

498 ms

lolipop.jp

1400 ms

default.css

339 ms

common.css

630 ms

background.css

511 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pecori.jp, 54% (71 requests) were made to Lolipop.jp and 5% (7 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3 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 Pecori.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, Pecori 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. Pecori.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 Pecori. 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

pecori.jp

pecori.jp

498 ms

lolipop.jp

lolipop.jp

1400 ms

default.css

default.css

339 ms

common.css

common.css

630 ms

background.css

background.css

511 ms

text_m.css

text_m.css

512 ms

home.css

home.css

677 ms

lightbox.css

lightbox.css

526 ms

owl.carousel.css

owl.carousel.css

530 ms

jquery.min.js

jquery.min.js

63 ms

base.js

base.js

735 ms

lightbox.min.js

lightbox.min.js

638 ms

owl.carousel.min.js

owl.carousel.min.js

756 ms

home.js

home.js

648 ms

scrollReveal.min.js

scrollReveal.min.js

647 ms

pixel.js

pixel.js

649 ms

mixpanel.js

mixpanel.js

751 ms

fbds.js

fbds.js

235 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

126 ms

bg_night.gif

bg_night.gif

217 ms

close.png

close.png

268 ms

loading.gif

loading.gif

283 ms

prev.png

prev.png

367 ms

next.png

next.png

366 ms

bg_content_side.png

bg_content_side.png

367 ms

bg_main_bottom.gif

bg_main_bottom.gif

372 ms

bg_main_1column.png

bg_main_1column.png

425 ms

bg_submenu_top.gif

bg_submenu_top.gif

460 ms

h2_home_title.png

h2_home_title.png

867 ms

megaphone.svg

megaphone.svg

534 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

538 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

548 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

582 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

637 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

703 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

873 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

723 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1695 ms

h3_home_title.png

h3_home_title.png

1932 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1740 ms

line_dot_11.gif

line_dot_11.gif

1420 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1751 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1590 ms

obj_home_feature_support.png

obj_home_feature_support.png

1945 ms

h3_home_functions.png

h3_home_functions.png

2239 ms

obj_home_functions_list.png

obj_home_functions_list.png

2387 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2242 ms

btn_infomation_more.png

btn_infomation_more.png

2244 ms

badge_light.png

badge_light.png

168 ms

line_dot_02.gif

line_dot_02.gif

2165 ms

widgets.js

widgets.js

233 ms

icon_star.gif

icon_star.gif

2154 ms

btn_h_serch.png

btn_h_serch.png

2315 ms

line_dot_08.gif

line_dot_08.gif

2310 ms

56 ms

dc.js

dc.js

79 ms

btn_pagetop.gif

btn_pagetop.gif

2210 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2400 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2400 ms

obj_header_banner_text.png

obj_header_banner_text.png

2493 ms

139 ms

__utm.gif

__utm.gif

43 ms

__utm.gif

__utm.gif

32 ms

__utm.gif

__utm.gif

41 ms

__utm.gif

__utm.gif

40 ms

btn_header_order.png

btn_header_order.png

2606 ms

bg_header_simple.png

bg_header_simple.png

2981 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2821 ms

obj_order_count_text.png

obj_order_count_text.png

2780 ms

obj_numbers.png

obj_numbers.png

2714 ms

menu_btn.png

menu_btn.png

2890 ms

menu_dot.gif

menu_dot.gif

2710 ms

arrow_menu.gif

arrow_menu.gif

2813 ms

obj_logo_ppb.png

obj_logo_ppb.png

2774 ms

pixel

pixel

295 ms

pixel

pixel

56 ms

Pug

Pug

70 ms

sync.ad-stir.com

sync.ad-stir.com

625 ms

sync

sync

54 ms

sync

sync

1044 ms

is

is

1186 ms

headerstyle.min.css

headerstyle.min.css

212 ms

sd

sd

4 ms

pixel

pixel

24 ms

google

google

178 ms

tag.js

tag.js

54 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2047 ms

obj_next_item_icon.png

obj_next_item_icon.png

2064 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2315 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2338 ms

tag

tag

43 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2326 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

52 ms

jot

jot

99 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2168 ms

lolipop.jp

lolipop.jp

1448 ms

lolipop.jp

lolipop.jp

2234 ms

lolipop.jp

lolipop.jp

1589 ms

lolipop.jp

lolipop.jp

1782 ms

lolipop.jp

lolipop.jp

692 ms

nr-768.min.js

nr-768.min.js

57 ms

roundtrip.js

roundtrip.js

165 ms

btn.png

btn.png

28 ms

conversion_async.js

conversion_async.js

45 ms

31 ms

logo201601.png

logo201601.png

60 ms

open_footer.png

open_footer.png

70 ms

close_footer.png

close_footer.png

110 ms

49 ms

conversion.js

conversion.js

926 ms

15936ac739

15936ac739

138 ms

53 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

154 ms

out

out

15 ms

tr

tr

46 ms

57 ms

out

out

10 ms

out

out

52 ms

out

out

56 ms

out

out

64 ms

u.php

u.php

98 ms

sync

sync

43 ms

sd

sd

313 ms

20 ms

sd

sd

17 ms

pixel

pixel

20 ms

377928.gif

377928.gif

12 ms

in

in

6 ms

conversion.js

conversion.js

1484 ms

tap.php

tap.php

457 ms

in

in

7 ms

SEO Factors

pecori.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 Pecori.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 Pecori.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

pecori.jp

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