AlexaWhoisServer InformationDesktop SpeedMobile SpeedMobile UsabilityHTML ErrorsPingTraceroute

MY-PRO.CO.JP 舞プロモーション

my-pro.co.jp Website Information

Daily Unique Visits: 828

Daily Page Views: 1,656

Income Per Day: $5

Estimated Value: $1,200

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

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

Website my-pro.co.jp is using the following name servers:

  • ns-213.dns.jp-e1.cloudn-service.com
  • ns-215.dns.us-e1.cloudn-service.com
  • ns-214.dns.jp-w1.cloudn-service.com

and is probably hosted by OCN NTT Communications Corporation, JP. See the full list of other websites hosted by OCN NTT Communications Corporation, JP.

The highest website my-pro.co.jp position in Alexa rank database was 57029 and the lowest rank position was 999827. Current position of my-pro.co.jp in Alexa rank database is 866113.

Desktop speed score of my-pro.co.jp (78/100) is better than the results of 65.98% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of my-pro.co.jp (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.

Mobile speed score of my-pro.co.jp (67/100) is better than the results of 70.58% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

my-pro.co.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.

my-pro.co.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: [ドメイン情報]
a. [ドメイン名] MY-PRO.CO.JP
e. [そしきめい] かぶしきがいしゃ まいぷろもーしょん
f. [組織名] 株式会社舞プロモーション
g. [Organization] MY Promotion co.
k. [組織種別] 株式会社
l. [Organization Type] Company
m. [登録担当者] TO4587JP
n. [技術連絡担当者] FG031JP
p. [ネームサーバ] mwns1.customer.ne.jp
p. [ネームサーバ] mwns2.customer.ne.jp
s. [署名鍵]
[状態] Connected (2023/03/31)
[登録年月日] 2001/03/08
[接続年月日] 2001/03/15
[最終更新] 2022/04/01 01:03:19 (JST)

my-pro.co.jp server information

Servers Location

my-pro.co.jp desktop page speed rank

Last tested: 2016-05-15

Desktop Speed Medium
78/100

my-pro.co.jp Desktop Speed Test Quick Summary


priority - 10Optimize images

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

Optimize the following images to reduce their size by 96.2KiB (89% reduction).

Compressing and resizing http://my-pro.co.jp/img/my004.jpg could save 62.5KiB (97% reduction).
Compressing and resizing http://my-pro.co.jp/img/005.jpg could save 25.1KiB (98% reduction).
Losslessly compressing http://my-pro.co.jp/img/menubg.jpg could save 8.6KiB (49% reduction).

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

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

Remove render-blocking JavaScript:

http://my-pro.co.jp/jquery.js
http://my-pro.co.jp/vtip.js

Optimize CSS Delivery of the following:

http://my-pro.co.jp/css/vtip.css
http://my-pro.co.jp/css/basic.css

priority - 5Enable 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 44.8KiB (65% reduction).

Compressing http://my-pro.co.jp/jquery.js could save 35.3KiB (65% reduction).
Compressing http://my-pro.co.jp/ could save 7.3KiB (64% reduction).
Compressing http://my-pro.co.jp/css/basic.css could save 1.5KiB (64% reduction).
Compressing http://my-pro.co.jp/vtip.js could save 695B (60% reduction).

priority - 4Leverage 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:

http://my-pro.co.jp/css/basic.css (expiration not specified)
http://my-pro.co.jp/css/vtip.css (expiration not specified)
http://my-pro.co.jp/img/005.jpg (expiration not specified)
http://my-pro.co.jp/img/menu_logo.jpg (expiration not specified)
http://my-pro.co.jp/img/menubg.jpg (expiration not specified)
http://my-pro.co.jp/img/my004.jpg (expiration not specified)
http://my-pro.co.jp/jquery.js (expiration not specified)
http://my-pro.co.jp/vtip.js (expiration not specified)

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 1.9KiB (17% reduction).

Minifying http://my-pro.co.jp/ could save 1.9KiB (17% reduction).

my-pro.co.jp Desktop Resource Breakdown

Total Resources9
Number of Hosts1
Static Resources8
JavaScript Resources2
CSS Resources2

my-pro.co.jp mobile page speed rank

Last tested: 2019-11-30

Mobile Speed Medium
67/100

my-pro.co.jp Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://my-pro.co.jp/jquery.js
http://my-pro.co.jp/vtip.js

Optimize CSS Delivery of the following:

http://my-pro.co.jp/css/vtip.css
http://my-pro.co.jp/css/basic.css

priority - 7Optimize images

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

Optimize the following images to reduce their size by 65.5KiB (60% reduction).

Losslessly compressing http://my-pro.co.jp/img/my004.jpg could save 32.1KiB (50% reduction).
Losslessly compressing http://my-pro.co.jp/img/005.jpg could save 24.8KiB (97% reduction).
Losslessly compressing http://my-pro.co.jp/img/menubg.jpg could save 8.6KiB (49% reduction).

priority - 6Leverage 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:

http://my-pro.co.jp/css/basic.css (expiration not specified)
http://my-pro.co.jp/css/vtip.css (expiration not specified)
http://my-pro.co.jp/img/005.jpg (expiration not specified)
http://my-pro.co.jp/img/menu_logo.jpg (expiration not specified)
http://my-pro.co.jp/img/menubg.jpg (expiration not specified)
http://my-pro.co.jp/img/my004.jpg (expiration not specified)
http://my-pro.co.jp/jquery.js (expiration not specified)
http://my-pro.co.jp/vtip.js (expiration not specified)

priority - 5Enable 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 44.8KiB (65% reduction).

Compressing http://my-pro.co.jp/jquery.js could save 35.3KiB (65% reduction).
Compressing http://my-pro.co.jp/ could save 7.3KiB (64% reduction).
Compressing http://my-pro.co.jp/css/basic.css could save 1.5KiB (64% reduction).
Compressing http://my-pro.co.jp/vtip.js could save 695B (60% reduction).

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 1.9KiB (17% reduction).

Minifying http://my-pro.co.jp/ could save 1.9KiB (17% reduction).

my-pro.co.jp Mobile Resource Breakdown

Total Resources9
Number of Hosts1
Static Resources8
JavaScript Resources2
CSS Resources2

my-pro.co.jp mobile page usability

Last tested: 2019-11-30

Mobile Usability Bad
61/100

my-pro.co.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.

Actor & Actress and 2 others render only 7 pixels tall (19 CSS pixels).

B-301 Mansion-…x:03-3797-6461 renders only 4 pixels tall (11 CSS pixels).

ノゾエ征爾 and 13 others render only 6 pixels tall (16 CSS pixels).

原田美枝子 and 3 others render only 6 pixels tall (16 CSS pixels).

（脚本・演出・俳優） and 1 others render only 4 pixels tall (10 CSS pixels).

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

【スケジュール】 and 1 others render only 5 pixels tall (13 CSS pixels).

月に１回更新しています。上のメニュー and 2 others render only 5 pixels tall (12 CSS pixels).

Schedule renders only 5 pixels tall (12 CSS pixels).

昨年12月半ばに軽い肺炎を起…3時25分に永眠致しました。 and 3 others render only 5 pixels tall (12 CSS pixels).

蜷川幸雄 renders only 7 pixels tall (18 CSS pixels).

浅丘ルリ子 and 1 others render only 7 pixels tall (18 CSS pixels).

このホームページに掲載されて…無い転用・転載を禁止します。 and 1 others render only 4 pixels tall (11 CSS pixels).

priority - 14Size 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="http://www.my-…aa/yamaya.html" class="vtip">山谷初男</a> and 13 others are close to other tap targets.

The tap target <a href="http://www.my-…aa/harada.html" class="vtip">原田美枝子</a> and 2 others are close to other tap targets.

The tap target <a href="http://www.my-…/aa/nozoe.html" class="vtip">ノゾエ征爾（脚本・演出・俳優）</a> and 1 others are close to other tap targets.

The tap target <a href="http://www.my-…ics/index.html">TOPICS</a> is close to 1 other tap targets.

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 - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,101 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="imgmap">Staff Schedule…出・俳優）藤田俊太郎（演出）</div> falls outside the viewport.
The element <p class="title">TOPICS</p> falls outside the viewport.
The element <div>蜷川幸雄岸惠子浅丘ルリ子</div> falls outside the viewport.

my-pro.co.jp HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <htm..."

A document must not include more than one “meta” element with a “http-equiv” attribute whose value is “content-type”.

Line: 7 Column: 57 - 124
"..." /> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> ..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 8 Column: 7 - 57
"... /> <meta http-equiv="Content-Language" content="ja" /> ..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 9 Column: 7 - 73
"... /> <meta http-equiv="Content-Script-Type" content="text/javascript" /> ..."

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Line: 10 Column: 7 - 65
"... /> <meta http-equiv="Content-Style-Type" content="text/css" /> ..."

Bad value “imagetoolbar” for attribute “http-equiv” on element “meta”.

Line: 11 Column: 7 - 53
"... /> <meta http-equiv="imagetoolbar" content="no" /> <ti..."

The “align” attribute on the “img” element is obsolete. Use CSS instead.

Line: 29 Column: 5 - 86
"...map"> <img src="img/my004.jpg" alt="" height="52" width="140" align="left" border="0" /><map n..."

No space between attributes.

Line: 35 Column: - 71
"... title="スケジュール"class="vtip">Sc..." Line: 36 Column: - 65
"...l" title="俳優紹介"class="vtip" >A..." Line: 255 Column: - 276
"......" Line: 255 Column: - 454
"......"

The “align” attribute on the “div” element is obsolete. Use CSS instead.

Line: 40 Column: 1 - 20
"...><br><br> <div align="center"> <tabl..." Line: 252 Column: - 20
"......"

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Line: 43 Column: 5 - 15
"...able> <tr> <td width="10"> </td>..." Line: 44 Column: 22 - 16
"...10"> </td> <td width="100"><a hre..." Line: 44 Column: 148 - 163
"...></a></td><td width="100"><a hre..." Line: 44 Column: 296 - 311
"...></a></td><td width="100"><a hre..." Line: 44 Column: 444 - 459
"...></a></td><td width="100"><a hre..." Line: 44 Column: 594 - 609
"...></a></td><td width="100"><a hre..." Line: 46 Column: 5 - 15
"...</td> <tr> <td width="10"> </td>..." Line: 47 Column: 22 - 16
"...10"> </td> <td width="100"><a hre..." Line: 47 Column: 148 - 163
"...></a></td><td width="100"><a hre..." Line: 47 Column: 297 - 312
"...></a></td><td width="100"><a hre..." Line: 47 Column: 444 - 459
"...></a></td><td width="100"><a hre..." Line: 47 Column: 591 - 606
"...></td></a><td width="100"><a hre..." Line: 50 Column: 5 - 15
"...</tr> <tr> <td width="10"> </td>..." Line: 51 Column: 22 - 16
"...10"> </td> <td width="100"><a hre..." Line: 51 Column: 146 - 161
"...></a></td><td width="100"><a hre..." Line: 51 Column: 292 - 307
"...></a></td><td width="100"><a hre..." Line: 51 Column: 437 - 452
".../font></a><td width="100"><a hre..." Line: 51 Column: 591 - 606
"...</td></td><td width="100"><a hre..." Line: 51 Column: 735 - 750
".../font></a><td width="100"><a hre..." Line: 56 Column: 5 - 15
"...able> <tr> <td width="10"> </td>..." Line: 57 Column: 22 - 31
"...10"> </td> <td width="200" align="center"><a hre..." Line: 57 Column: 211 - 241
"...></a></td><td width="200" align="center"><a hre..." Line: 57 Column: 412 - 427
"...font></td><td width="100"> </td>..." Line: 57 Column: 434 - 449
"...00"> </td><td width="100"> </td>..." Line: 255 Column: - 31
"......" Line: 255 Column: - 207
"......" Line: 255 Column: - 381
"......"

The “font” element is obsolete. Use CSS instead.

Line: 44 Column: 108 - 127
"...="_blank"><font color="black">山谷初男</..." Line: 44 Column: 256 - 275
"...="_blank"><font color="black">六角精児</..." Line: 44 Column: 404 - 423
"...="_blank"><font color="black">筒井道隆</..." Line: 44 Column: 554 - 573
"...="_blank"><font color="black">高橋一生</..." Line: 44 Column: 702 - 719
"...="_blank"><font color="red">原田美枝子<..." Line: 47 Column: 108 - 127
"...="_blank"><font color="black">大門伍朗</..." Line: 47 Column: 257 - 276
"...="_blank"><font color="black">新川將人</..." Line: 47 Column: 404 - 423
"...="_blank"><font color="black">玉置孝匡</..." Line: 47 Column: 551 - 570
"...="_blank"><font color="black">広田亮平</..." Line: 47 Column: 700 - 717
"...="_blank"><font color="red">新海百合子<..." Line: 51 Column: 106 - 125
"...="_blank"><font color="black">不破万作</..." Line: 51 Column: 252 - 271
"...="_blank"><font color="black">妹尾正文</..." Line: 51 Column: 402 - 421
"...="_blank"><font color="black">竹口龍茶</..." Line: 51 Column: 546 - 565
"...="_blank"><font color="black">古畑新之</..." Line: 51 Column: 702 - 719
"...="_blank"><font color="red">蜷川みほ</..." Line: 51 Column: 844 - 861
"...="_blank"><font color="red">川上友里</..." Line: 57 Column: 123 - 142
"...="_blank"><font color="black">ノゾエ征爾<..." Line: 57 Column: 155 - 184
"...エ征爾</font><font size="-2" color="black">（脚本・演出..." Line: 57 Column: 334 - 353
"...="_blank"><font color="black">藤田俊太郎<..." Line: 57 Column: 366 - 395
"...俊太郎</font><font size="-2" color="black">（演出）</..." Line: 255 Column: - 156
"......" Line: 255 Column: - 331
"......" Line: 255 Column: - 509
"......"

End tag “td” seen, but there were open elements.

Line: 47 Column: 582 - 586
"...田亮平</font></td></a><t..." Line: 57 Column: 407 - 411
"...演出）</font></td><td wi..."

Unclosed element “a”.

Line: 47 Column: 460 - 550
"...dth="100"><a href="http://www.my-pro.co.jp/aa/hirota.html" title="広田亮平" class="vtip" target="_blank"><font ..." Line: 57 Column: 242 - 333
"...="center"><a href="http://www.my-pro.co.jp/aa/fujita.html" title="藤田俊太郎" class="vtip" target="_blank"><font ..."

Stray end tag “a”.

Line: 47 Column: 587 - 590
"...font></td></a><td wi..." Line: 47 Column: 587 - 590
"...font></td></a><td wi..."

Stray end tag “td”.

Line: 51 Column: 586 - 590
"...></a></td></td><td wi..." Line: 67 Column: 35 - 39
"...DATE 03/22</TD> <h2>..."

The “align” attribute on the “td” element is obsolete. Use CSS instead.

Line: 57 Column: 22 - 31
"...10"> </td> <td width="200" align="center"><a hre..." Line: 57 Column: 211 - 241
"...></a></td><td width="200" align="center"><a hre..." Line: 255 Column: - 31
"......" Line: 255 Column: - 207
"......" Line: 255 Column: - 381
"......"

Stray start tag “td”.

Line: 67 Column: 1 - 18
"...さい。<br /> <TD ALIGN="RIGHT">LASTUP..."

Saw “<!--” within a comment. Probable cause: Nested comment (not allowed).

Line: 225 Column: - 5
"... 講談社刊 </p> <!-- <div class="sa..." Line: 225 Column: - 6
"......" Line: 237 Column: - 5
"......" Line: 237 Column: - 6
"......"

Warnings

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

Line: 29 Column: 5 - 86
"...map"> <img src="img/my004.jpg" alt="" height="52" width="140" align="left" border="0" /><map n..." Line: 259 Column: - 81
"......"

A table row was 7 columns wide and exceeded the column count established by the first row (6).

Line: 52 Column: 883 - 5
"...</a>　</td> </tr> </tab..."

The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

Line: 225 Column: - 5
"... 講談社刊 </p> <!-- <div class="sa..." Line: 237 Column: - 5
"......"

This document appears to be written in Japanese. Consider adding “lang="ja"” (or variant) to the “html” start tag.

Line: 3 Column: 122 - 43
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <he..."

my-pro.co.jp similar domains

Similar domains:
www.my-pro.com
www.my-pro.net
www.my-pro.org
www.my-pro.info
www.my-pro.biz
www.my-pro.us
www.my-pro.mobi
www.y-pro.co.jp
www.my-pro.co.jp
www.ny-pro.co.jp
www.mny-pro.co.jp
www.nmy-pro.co.jp
www.jy-pro.co.jp
www.mjy-pro.co.jp
www.jmy-pro.co.jp
www.ky-pro.co.jp
www.mky-pro.co.jp
www.kmy-pro.co.jp
www.m-pro.co.jp
www.mt-pro.co.jp
www.myt-pro.co.jp
www.mty-pro.co.jp
www.mg-pro.co.jp
www.myg-pro.co.jp
www.mgy-pro.co.jp
www.mh-pro.co.jp
www.myh-pro.co.jp
www.mhy-pro.co.jp
www.mu-pro.co.jp
www.myu-pro.co.jp
www.muy-pro.co.jp
www.mypro.co.jp
www.my-ro.co.jp
www.my-oro.co.jp
www.my-poro.co.jp
www.my-opro.co.jp
www.my-lro.co.jp
www.my-plro.co.jp
www.my-lpro.co.jp
www.my-po.co.jp
www.my-peo.co.jp
www.my-preo.co.jp
www.my-pero.co.jp
www.my-pdo.co.jp
www.my-prdo.co.jp
www.my-pdro.co.jp
www.my-pfo.co.jp
www.my-prfo.co.jp
www.my-pfro.co.jp
www.my-pto.co.jp
www.my-prto.co.jp
www.my-ptro.co.jp
www.my-pr.co.jp
www.my-pri.co.jp
www.my-proi.co.jp
www.my-prio.co.jp
www.my-prk.co.jp
www.my-prok.co.jp
www.my-prko.co.jp
www.my-prl.co.jp
www.my-prol.co.jp
www.my-prlo.co.jp
www.my-prp.co.jp
www.my-prop.co.jp
www.my-prpo.co.jp

my-pro.co.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.

my-pro.co.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.