PIERROT.JP 株式会社ぴえろ 公式サイト

pierrot.jp Website Information

Daily Unique Visits: 7,162

Daily Page Views: 35,810

Income Per Day: $90

Estimated Value: $54,000

This website is located in Japan and is using following IP address 118.238.6.59. See the complete list of popular websites hosted in Japan.

pierrot.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

Website pierrot.jp is using the following name servers:

  • blueberry.pierrot.co.jp
  • dischidia.pierrot.co.jp
  • ns1.nuro.jp
  • ns2.nuro.jp

and is probably hosted by SO-NET So-net Entertainment Corporation, JP. See the full list of other websites hosted by SO-NET So-net Entertainment Corporation, JP.

The highest website pierrot.jp position in Alexa rank database was 26366 and the lowest rank position was 978367. Current position of pierrot.jp in Alexa rank database is 190250.

Desktop speed score of pierrot.jp (50/100) is better than the results of 23.83% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of pierrot.jp (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.

Mobile speed score of pierrot.jp (46/100) is better than the results of 27.13% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

pierrot.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


pierrot.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]

Domain Information: [ドメイン情報]
[Domain Name] PIERROT.JP

[登録者名] 株式会社ぴえろ
[Registrant] PIERROT Co.,Ltd.

[Name Server] blueberry.pierrot.co.jp
[Name Server] dischidia.pierrot.co.jp
[Signing Key]

[登録年月日] 2001/03/26
[有効期限] 2022/03/31
[状態] Active
[最終更新] 2021/04/01 01:05:10 (JST)

Contact Information: [公開連絡窓口]
[名前] 石塚 勇一
[Name] Yuuichi Ishizuka
[Email] ishizuka@pierrot.co.jp
[Web Page]
[郵便番号] 181-0013
[住所] 東京都三鷹市下連雀 2−29−13
[Postal Address] Tokyo
2-129-13,Shimorenjaku,Mitaka-city
[電話番号] 0422-70-6401
[FAX番号] 0422-24-0452

pierrot.jp server information

Servers Location

pierrot.jp desktop page speed rank

Last tested: 2017-04-30


Desktop Speed Bad
50/100

pierrot.jp Desktop Speed Test Quick Summary


priority - 100Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 980.3KiB (74% reduction).

Compressing http://pierrot.jp/slide/images/pazzdrax.jpg could save 159.2KiB (73% reduction).
Compressing http://pierrot.jp/slide/images/yuhaku25th.jpg could save 156.6KiB (79% reduction).
Compressing http://pierrot.jp/slide/images/boruto_tv.jpg could save 141.4KiB (72% reduction).
Compressing http://pierrot.jp/slide/images/sosei.jpg could save 130.6KiB (74% reduction).
Compressing http://pierrot.jp/slide/images/naruto2.jpg could save 116.4KiB (73% reduction).
Compressing http://pierrot.jp/slide/images/eldlive.jpg could save 107.2KiB (71% reduction).
Compressing http://pierrot.jp/banner/AJ2017banner.jpg could save 48.7KiB (82% reduction).
Compressing http://pierrot.jp/banner/yuhaku25th.jpg could save 32.8KiB (75% reduction).
Compressing http://pierrot.jp/banner/magicgirl_banner.jpg could save 32.5KiB (77% reduction).
Compressing http://pierrot.jp/banner/pierrotolshop.jpg could save 26.4KiB (76% reduction).
Compressing https://pbs.twimg.com/profile_images/1921209786/pierrot_logo_normal.jpg could save 5.9KiB (83% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_04.jpg could save 4.2KiB (69% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_03.jpg could save 4KiB (71% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_01.jpg could save 3KiB (69% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_02.jpg could save 2.4KiB (64% reduction).
Compressing http://pierrot.jp/images/index/others_panel.png could save 1.5KiB (46% reduction).
Compressing http://pierrot.jp/images/index/top_blog_panel.png could save 1.3KiB (48% reduction).
Compressing http://pierrot.jp/images/index/top_link_panel.png could save 1.1KiB (45% reduction).
Compressing http://pierrot.jp/images/template/pierrot_logo.png could save 1.1KiB (26% reduction).
Compressing https://pbs.twimg.com/profile_images/575477314626043906/_cKG-izP_normal.png could save 1,022B (17% reduction).
Compressing https://pbs.twimg.com/profile_images/848000628156637184/hsFG5P42_normal.jpg could save 978B (50% reduction).
Compressing http://pierrot.jp/images/index/top_news_panel.png could save 800B (45% reduction).
Compressing http://pierrot2.com/blog/wp-content/plugins/user-a…id=4&random=1448524834 could save 601B (35% reduction).
Compressing http://pierrot2.com/blog/wp-content/plugins/user-a…id=2&random=1443406744 could save 575B (31% reduction).

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://pierrot.jp/js/jquery.min.js
http://pierrot.jp/js/jquery-migrate.min.js
http://pierrot.jp/js/jquery.superbox-min.js
http://pierrot.jp/js/smoothmenu.js
http://pierrot.jp/js/jquery.nanoscroller.js

Optimize CSS Delivery of the following:

http://pierrot.jp/css/style.css
http://pierrot.jp/css/smoothmenu.css
http://pierrot.jp/css/jquery.superbox.css
http://pierrot.jp/css/nanoscroller.css
http://pierrot.jp/css/twitter.css

priority - 1Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://cdn.syndication.twimg.com/widgets/timeline…e_codes=true&t=1659549 (5 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 10.5KiB (85% reduction).

Compressing http://pierrot2.com/blog/whatnew could save 10.5KiB (85% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 7.1KiB (49% reduction).

Minifying http://pierrot.jp/slide/js/jquery.featureCarousel.js could save 4.2KiB (57% reduction) after compression.
Minifying http://pierrot.jp/js/smoothmenu.js could save 1.4KiB (45% reduction) after compression.
Minifying http://pierrot.jp/js/jquery.nanoscroller.js could save 1.4KiB (37% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 696B (17% reduction).

Minifying http://pierrot.jp/ could save 696B (17% reduction) after compression.

pierrot.jp Desktop Resource Breakdown

Total Resources75
Number of Hosts9
Static Resources65
JavaScript Resources10
CSS Resources8

pierrot.jp mobile page speed rank

Last tested: 2017-04-30


Mobile Speed Bad
46/100

pierrot.jp Mobile Speed Test Quick Summary


priority - 101Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 989.4KiB (73% reduction).

Compressing http://pierrot.jp/slide/images/pazzdrax.jpg could save 159.2KiB (73% reduction).
Compressing http://pierrot.jp/slide/images/yuhaku25th.jpg could save 156.6KiB (79% reduction).
Compressing http://pierrot.jp/slide/images/boruto_tv.jpg could save 141.4KiB (72% reduction).
Compressing http://pierrot.jp/slide/images/sosei.jpg could save 130.6KiB (74% reduction).
Compressing http://pierrot.jp/slide/images/naruto2.jpg could save 116.4KiB (73% reduction).
Compressing http://pierrot.jp/slide/images/eldlive.jpg could save 107.2KiB (71% reduction).
Compressing http://pierrot.jp/banner/AJ2017banner.jpg could save 48.7KiB (82% reduction).
Compressing http://pierrot.jp/banner/yuhaku25th.jpg could save 32.8KiB (75% reduction).
Compressing http://pierrot.jp/banner/magicgirl_banner.jpg could save 32.5KiB (77% reduction).
Compressing http://pierrot.jp/banner/pierrotolshop.jpg could save 26.4KiB (76% reduction).
Compressing https://pbs.twimg.com/profile_images/1921209786/pierrot_logo_bigger.jpg could save 14KiB (88% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_04.jpg could save 4.2KiB (69% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_03.jpg could save 4KiB (71% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_01.jpg could save 3KiB (69% reduction).
Compressing http://pierrot.jp/images/template/contents_mainmenu_02.jpg could save 2.4KiB (64% reduction).
Compressing https://pbs.twimg.com/profile_images/575477314626043906/_cKG-izP_bigger.png could save 1.9KiB (17% reduction).
Compressing http://pierrot.jp/images/index/others_panel.png could save 1.5KiB (46% reduction).
Compressing http://pierrot.jp/images/index/top_blog_panel.png could save 1.3KiB (48% reduction).
Compressing http://pierrot.jp/images/index/top_link_panel.png could save 1.1KiB (45% reduction).
Compressing http://pierrot.jp/images/template/pierrot_logo.png could save 1.1KiB (26% reduction).
Compressing https://pbs.twimg.com/profile_images/848000628156637184/hsFG5P42_bigger.jpg could save 1KiB (37% reduction).
Compressing http://pierrot.jp/images/index/top_news_panel.png could save 800B (45% reduction).
Compressing http://pierrot2.com/blog/wp-content/plugins/user-a…id=4&random=1448524834 could save 601B (35% reduction).
Compressing http://pierrot2.com/blog/wp-content/plugins/user-a…id=2&random=1443406744 could save 575B (31% reduction).

priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://pierrot.jp/js/jquery.min.js
http://pierrot.jp/js/jquery-migrate.min.js
http://pierrot.jp/js/jquery.superbox-min.js
http://pierrot.jp/js/smoothmenu.js
http://pierrot.jp/js/jquery.nanoscroller.js

Optimize CSS Delivery of the following:

http://pierrot.jp/css/style.css
http://pierrot.jp/css/smoothmenu.css
http://pierrot.jp/css/jquery.superbox.css
http://pierrot.jp/css/nanoscroller.css
http://pierrot.jp/css/twitter.css

priority - 2Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://cdn.syndication.twimg.com/widgets/timeline…e_codes=true&t=1659546 (5 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 10.5KiB (85% reduction).

Compressing http://pierrot2.com/blog/whatnew could save 10.5KiB (85% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 7.1KiB (49% reduction).

Minifying http://pierrot.jp/slide/js/jquery.featureCarousel.js could save 4.2KiB (57% reduction) after compression.
Minifying http://pierrot.jp/js/smoothmenu.js could save 1.4KiB (45% reduction) after compression.
Minifying http://pierrot.jp/js/jquery.nanoscroller.js could save 1.4KiB (37% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 696B (17% reduction).

Minifying http://pierrot.jp/ could save 696B (17% reduction) after compression.

pierrot.jp Mobile Resource Breakdown

Total Resources75
Number of Hosts9
Static Resources65
JavaScript Resources10
CSS Resources8

pierrot.jp mobile page usability

Last tested: 2017-04-30


Mobile Usability Medium
65/100

pierrot.jp Mobile Usability Test Quick Summary


priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

ENGLISH renders only 6 pixels tall (16 CSS pixels).

2016.12.27 and 5 others render only 5 pixels tall (13 CSS pixels).

祝言日和 そして、3話目と4話目が一緒になるブログ… and 4 others render only 4 pixels tall (11 CSS pixels).

‎@studiopierrot renders only 5 pixels tall (12 CSS pixels).

さんの renders only 5 pixels tall (12 CSS pixels).

ツイート renders only 6 pixels tall (16 CSS pixels).

株式会社ぴえろ and 1 others render only 5 pixels tall (14 CSS pixels).

@studiopierrot and 1 others render only 5 pixels tall (13 CSS pixels).

【ぴえろ公式サイト更新】4月…」の作品情報を公開しました。 and 1 others render only 5 pixels tall (12 CSS pixels).

pierrot.jp renders only 5 pixels tall (12 CSS pixels).

Apr03日 renders only 5 pixels tall (12 CSS pixels).

Copyright © 20…errot Co.,Ltd. renders only 5 pixels tall (12 CSS pixels).

サイトのご利用に際して and 1 others render only 4 pixels tall (11 CSS pixels).

| renders only 4 pixels tall (11 CSS pixels).

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 6Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/archives/"></a> and 2 others are close to other tap targets.

The tap target <a href="http://pierrot2.com/blog/"> is close to 1 other tap targets.

The tap target <div class="carousel-feature"></div> and 1 others are close to other tap targets.

The tap target <a href="/archives/tv_l…15/tv_102.html"></a> and 1 others are close to other tap targets.

The tap target <a href=""></a> and 5 others are close to other tap targets.

The tap target <a href="http://pierrot…/archives/1247">TVアニメ『NARUTO』完結!</a> and 5 others are close to other tap targets.

The tap target <div class="pane"></div> is close to 1 other tap targets.

The tap target <div class="slider"> is close to 1 other tap targets.

The tap target <a href="https://twitte…96855014006784" class="TweetAction Tw…art web-intent"></a> is close to 2 other tap targets.

The tap target <a href="#" class="TweetAction Tw…-showShareMenu"></a> is close to 2 other tap targets.

The tap target <a href="https://twitte…/studiopierrot" class="TweetAuthor-li…ty u-linkBlend">株式会社ぴえろ…@studiopierrot</a> is close to 1 other tap targets.

pierrot.jp HTML validation

Errors

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 76 Column: 39 - 103
"... href="/"><img src="/images/spacer.gif" width="220" height="70" border="0"></a></..." Line: 85 Column: 50 - 87
"...="#">話題作  <img src="/images/template/right.png"></a> ..." Line: 124 Column: 51 - 88
"..."#">採用情報  <img src="/images/template/right.png"></a> ..." Line: 165 Column: 21 - 64
"...="panel2"><img src="/images/index/top_blog_panel.png"> </div..." Line: 177 Column: 20 - 63
"...s="panel"><img src="/images/index/top_news_panel.png"></div>..." Line: 243 Column: 20 - 61
"...s="panel"><img src="/images/index/others_panel.png"></div>..." Line: 244 Column: 79 - 125
"...="_blank"><img src="banner/others/mami_twitter_link.png"></a></..." Line: 250 Column: 20 - 63
"...s="panel"><img src="/images/index/top_link_panel.png"></div>..." Line: 253 Column: 61 - 94
"...="_blank"><img src="/banner/yuhaku25th.jpg"></a></..." Line: 254 Column: 68 - 107
"...="_blank"><img src="/banner/magicgirl_banner.jpg"></a></..." Line: 255 Column: 79 - 114
"...="_blank"><img src="/banner/banner310x74.gif"></a></..." Line: 258 Column: 77 - 114
"...="_blank"><img src="/banner/nunoani_banner.jpg"></a></..." Line: 259 Column: 77 - 112
"...="_blank"><img src="/banner/AJ2018banner.jpg"></a></..." Line: 260 Column: 61 - 99
"...="_blank"><img src="/banner/mami35th_banner.jpg"></a></..."

No “li” element in scope but a “li” end tag seen.

Line: 117 Column: 1 - 5
"...ul> </li> </li> <li c..."

Element “a” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 138 Column: 1 - 32
"...l> </li> <a href="http://en.pierrot.jp/"><li cl..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 152 Column: 1 - 117
"...sition"> <iframe src="/slide/index.html" height=300 width=940 name="news_info" id="news_info" frameborder="no" scrolling="no">ぴえろ作品ス..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 152 Column: 1 - 117
"...sition"> <iframe src="/slide/index.html" height=300 width=940 name="news_info" id="news_info" frameborder="no" scrolling="no">ぴえろ作品ス..."

Text not allowed in element “iframe” in this context.

Line: 152 Column: 118 - 129
"...ling="no">ぴえろ作品スライドショー</ifra..."

Attribute “width” not allowed on element “a” at this point.

Line: 185 Column: 1 - 198
"...tter" > <a class="twitter-timeline" href="https://twitter.com/studiopierrot" width="460px" height="242px" data-widget-id="306694411591499776" data-border-color="#ffffff" data-chrome="nofooter transparent">@studi..."

Attribute “height” not allowed on element “a” at this point.

Line: 185 Column: 1 - 198
"...tter" > <a class="twitter-timeline" href="https://twitter.com/studiopierrot" width="460px" height="242px" data-widget-id="306694411591499776" data-border-color="#ffffff" data-chrome="nofooter transparent">@studi..."

Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

Line: 205 Column: 1 - 7
"...-></div> <style> </st..."

Duplicate ID “banner_fl”.

Line: 252 Column: 1 - 20
"...v> </div> <div id="banner_fl"> <div ..." Line: 257 Column: 1 - 20
"...v> </div> <div id="banner_fl"> <div ..."

Bad value “superbox[iframe][560x1100]” for attribute “rel” on element “a”: The string “superbox[iframe][560x1100]” is not a registered keyword.

Line: 270 Column: 38 - 118
"...際して</a> | <a href="http://pierrot2.com/blog/inquiry_info" rel="superbox[iframe][560x1100]">お問い合わせ..."

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 76 Column: 39 - 103
"... href="/"><img src="/images/spacer.gif" width="220" height="70" border="0"></a></..."

The first occurrence of ID “banner_fl” was here.

Line: 249 Column: 1 - 20
"...info_fl"> <div id="banner_fl"> <div ..." Line: 249 Column: 1 - 20
"...info_fl"> <div id="banner_fl"> <div ..."

pierrot.jp similar domains

Similar domains:
www.pierrot.com
www.pierrot.net
www.pierrot.org
www.pierrot.info
www.pierrot.biz
www.pierrot.us
www.pierrot.mobi
www.ierrot.jp
www.pierrot.jp
www.oierrot.jp
www.poierrot.jp
www.opierrot.jp
www.lierrot.jp
www.plierrot.jp
www.lpierrot.jp
www.perrot.jp
www.puerrot.jp
www.piuerrot.jp
www.puierrot.jp
www.pjerrot.jp
www.pijerrot.jp
www.pjierrot.jp
www.pkerrot.jp
www.pikerrot.jp
www.pkierrot.jp
www.poerrot.jp
www.pioerrot.jp
www.pirrot.jp
www.piwrrot.jp
www.piewrrot.jp
www.piwerrot.jp
www.pisrrot.jp
www.piesrrot.jp
www.piserrot.jp
www.pidrrot.jp
www.piedrrot.jp
www.piderrot.jp
www.pirrrot.jp
www.pierrrot.jp
www.pirerrot.jp
www.pierot.jp
www.pieerot.jp
www.piererot.jp
www.pieerrot.jp
www.piedrot.jp
www.pierdrot.jp
www.piefrot.jp
www.pierfrot.jp
www.piefrrot.jp
www.pietrot.jp
www.piertrot.jp
www.pietrrot.jp
www.piereot.jp
www.pierreot.jp
www.pierdot.jp
www.pierrdot.jp
www.pierfot.jp
www.pierrfot.jp
www.piertot.jp
www.pierrtot.jp
www.pierrt.jp
www.pierrit.jp
www.pierroit.jp
www.pierriot.jp
www.pierrkt.jp
www.pierrokt.jp
www.pierrkot.jp
www.pierrlt.jp
www.pierrolt.jp
www.pierrlot.jp
www.pierrpt.jp
www.pierropt.jp
www.pierrpot.jp
www.pierro.jp
www.pierror.jp
www.pierrotr.jp
www.pierrort.jp
www.pierrof.jp
www.pierrotf.jp
www.pierroft.jp
www.pierrog.jp
www.pierrotg.jp
www.pierrogt.jp
www.pierroy.jp
www.pierroty.jp
www.pierroyt.jp

pierrot.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


pierrot.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.