Tools & Wizards About Us
perma.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

perma.jp

ロリポップ！レンタルサーバー

Page Load Speed

9 sec in total

First Response

567 ms

Resources Loaded

8 sec

Page Rendered

411 ms

perma.jp screenshot

About Website

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

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

Visit perma.jp

Key Findings

We analyzed Perma.jp page load time and found that the first response time was 567 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

perma.jp performance score

0

Network Requests Diagram

perma.jp

567 ms

lolipop.jp

1252 ms

default.css

344 ms

common.css

638 ms

background.css

520 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Perma.jp, 52% (71 requests) were made to Lolipop.jp and 9% (12 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

783.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

  • Original 169.1 kB
  • After minification 159.0 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 144.1 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, Perma 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.2 kB

  • Original 268.9 kB
  • After minification 268.2 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.2 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. Perma.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 66 (57%)

Requests Now

116

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perma. 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

perma.jp

perma.jp

567 ms

lolipop.jp

lolipop.jp

1252 ms

default.css

default.css

344 ms

common.css

common.css

638 ms

background.css

background.css

520 ms

text_m.css

text_m.css

521 ms

home.css

home.css

689 ms

lightbox.css

lightbox.css

532 ms

owl.carousel.css

owl.carousel.css

535 ms

jquery.min.js

jquery.min.js

25 ms

base.js

base.js

702 ms

lightbox.min.js

lightbox.min.js

617 ms

owl.carousel.min.js

owl.carousel.min.js

739 ms

home.js

home.js

616 ms

scrollreveal.min.js

scrollreveal.min.js

677 ms

pixel.js

pixel.js

673 ms

mixpanel.js

mixpanel.js

714 ms

fbds.js

fbds.js

288 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

183 ms

bg_night.gif

bg_night.gif

188 ms

close.png

close.png

193 ms

loading.gif

loading.gif

290 ms

prev.png

prev.png

317 ms

next.png

next.png

325 ms

bg_content_side.png

bg_content_side.png

358 ms

bg_main_bottom.gif

bg_main_bottom.gif

362 ms

bg_main_1column.png

bg_main_1column.png

364 ms

bg_submenu_top.gif

bg_submenu_top.gif

448 ms

h2_home_title.png

h2_home_title.png

817 ms

megaphone.svg

megaphone.svg

497 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

535 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

540 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

543 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

608 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

670 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

888 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

720 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1257 ms

h3_home_title.png

h3_home_title.png

1086 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1205 ms

line_dot_11.gif

line_dot_11.gif

900 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1155 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1241 ms

obj_home_feature_support.png

obj_home_feature_support.png

1436 ms

h3_home_functions.png

h3_home_functions.png

1246 ms

obj_home_functions_list.png

obj_home_functions_list.png

1492 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1386 ms

btn_infomation_more.png

btn_infomation_more.png

1422 ms

badge_light.png

badge_light.png

160 ms

line_dot_02.gif

line_dot_02.gif

1347 ms

icon_star.gif

icon_star.gif

1375 ms

widgets.js

widgets.js

67 ms

btn_h_serch.png

btn_h_serch.png

1480 ms

line_dot_08.gif

line_dot_08.gif

1454 ms

dc.js

dc.js

58 ms

btn_pagetop.gif

btn_pagetop.gif

1440 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1632 ms

27 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1606 ms

obj_header_banner_text.png

obj_header_banner_text.png

1705 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

20 ms

__utm.gif

__utm.gif

28 ms

89 ms

btn_header_order.png

btn_header_order.png

1799 ms

bg_header_simple.png

bg_header_simple.png

1975 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1626 ms

obj_order_count_text.png

obj_order_count_text.png

1609 ms

obj_numbers.png

obj_numbers.png

1570 ms

menu_btn.png

menu_btn.png

1776 ms

menu_dot.gif

menu_dot.gif

1658 ms

arrow_menu.gif

arrow_menu.gif

1691 ms

obj_logo_ppb.png

obj_logo_ppb.png

1633 ms

pixel

pixel

297 ms

Pug

Pug

101 ms

sync.ad-stir.com

sync.ad-stir.com

610 ms

sync

sync

1164 ms

is

is

1097 ms

headerstyle.min.css

headerstyle.min.css

176 ms

sync

sync

18 ms

pixel

pixel

32 ms

sd

sd

8 ms

google

google

153 ms

tag.js

tag.js

72 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

7 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

995 ms

obj_next_item_icon.png

obj_next_item_icon.png

1031 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1250 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1245 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1290 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1352 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

15 ms

tag

tag

36 ms

jot

jot

97 ms

mapuser

mapuser

151 ms

lolipop.jp

lolipop.jp

1707 ms

lolipop.jp

lolipop.jp

1924 ms

lolipop.jp

lolipop.jp

2204 ms

lolipop.jp

lolipop.jp

2569 ms

lolipop.jp

lolipop.jp

736 ms

nr-892.min.js

nr-892.min.js

56 ms

roundtrip.js

roundtrip.js

131 ms

btn.png

btn.png

33 ms

conversion_async.js

conversion_async.js

38 ms

39 ms

logo201601.png

logo201601.png

45 ms

open_footer.png

open_footer.png

425 ms

close_footer.png

close_footer.png

118 ms

35 ms

conversion.js

conversion.js

986 ms

15936ac739

15936ac739

111 ms

73 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

118 ms

fbevents.hashing.js

fbevents.hashing.js

75 ms

out

out

11 ms

41 ms

out

out

7 ms

out

out

20 ms

out

out

19 ms

out

out

19 ms

out

out

20 ms

out

out

35 ms

out

out

35 ms

out

out

33 ms

out

out

33 ms

u.php

u.php

67 ms

sync

sync

27 ms

pixel

pixel

48 ms

31 ms

sd

sd

46 ms

sd

sd

16 ms

377928.gif

377928.gif

16 ms

27 ms

in

in

4 ms

tap.php

tap.php

17 ms

in

in

7 ms

SEO Factors

perma.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 Perma.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 Perma.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

perma.jp

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