ITP.NE.JP iタウンページ


itp.ne.jp website information.

itp.ne.jp website servers are located in Japan and are responding from following IP address 202.217.73.233. Check the full list of most visited websites located in Japan.

itp.ne.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.

Following name servers are specified for itp.ne.jp domain:

  • ns1-06.azure-dns.com
  • ns2-06.azure-dns.net
  • ns3-06.azure-dns.org
  • ns4-06.azure-dns.info

and probably website itp.ne.jp is hosted by azure-dns.com web hosting company. Check the complete list of other most popular websites hosted by azure-dns.com hosting company.

According to Alexa traffic rank the highest website itp.ne.jp position was 8443 (in the world). The lowest Alexa rank position was 865148. Now website itp.ne.jp ranked in Alexa database as number 43539 (in the world).

Website itp.ne.jp Desktop speed measurement score (66/100) is better than the results of 44.27% of other sites shows that the page desktop performance can be improved.

itp.ne.jp Mobile usability score (97/100) is better than the results of 63.67% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of itp.ne.jp (62/100) is better than the results of 59.52% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-20-2019 43,539-23,892
Oct-19-2019 19,64730,571
Oct-18-2019 50,218-3,731
Oct-17-2019 46,48716,694
Oct-16-2019 63,181-42,185
Oct-15-2019 20,996-1,755
Oct-14-2019 19,2412,889

Advertisement

itp.ne.jp Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


itp.ne.jp whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


[ 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. [Domain Name] ITP.NE.JP
d. [Network Service Name] Internet TownPage Service
l. [Organization Type] Network Service
m. [Administrative Contact] RK5090JP
n. [Technical Contact] HK14099JP
p. [Name Server] ns.itp.ne.jp
p. [Name Server] ns3.skyarch.ne.jp
s. [Signing Key]
[State] Connected (2016/02/29)
[Registered Date] 1999/02/08
[Connected Date] 1999/04/14
[Last Update] 2015/03/01 01:02:45 (JST)

[ 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'. ]

Contact Information:
a. [JPNIC Handle] RK5090JP
c. [Last, First] Kawamoto, Ryoji
d. [E-Mail] ry.kawamoto@ntt-tp.co.jp
g. [Organization] NTT DIRECTORY SERVICES,CO.
l. [Division]
n. [Title]
o. [TEL]
p. [FAX]
y. [Reply Mail]
[Last Update] 2012/08/07 17:28:09 (JST)
form@dom.jprs.jp

[ 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'. ]

Contact Information:
a. [JPNIC Handle] HK14099JP
c. [Last, First] Kanno, Hirofumi
d. [E-Mail] hi.kanno@ntt-tp.co.jp
g. [Organization] NTT DIRECTORY SERVICES Co.
l. [Division]
n. [Title]
o. [TEL] 03-5776-4048
p. [FAX]
y. [Reply Mail]
[Last Update] 2012/08/07 17:30:21 (JST)
form@dom.jprs.jp

itp.ne.jp server information

Servers Location

itp.ne.jp desktop page speed rank

Last tested: 2016-06-14


Desktop Speed Medium
66/100

itp.ne.jp Desktop Speed Test Quick Summary


priority - 29 Leverage 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://bjimg.durasite.net/images/NTT-BJ/34481/29730top0014.jpg (expiration not specified)
http://itp.ne.jp/topics/img/cmk/160608.jpg (expiration not specified)
http://itp.thatsping.com/ping/custom_ping.js (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-N4QD6H (16.2 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://b03.nakanohito.jp/b1/bivalves.js (3 hours)
http://itp.ne.jp/css2/pc/cmn/desktop.css (3 days)
http://itp.ne.jp/css2/pc/cmn/small.css (3 days)
http://itp.ne.jp/css2/pc/cmn/style.css (3 days)
http://itp.ne.jp/css2/pc/cms/area_pickup.css (3 days)
http://itp.ne.jp/css2/pc/cms/ec-weekly.css (3 days)
http://itp.ne.jp/css2/pc/cms/footer.css (3 days)
http://itp.ne.jp/css2/pc/cms/import_pc.css (3 days)
http://itp.ne.jp/css2/pc/cms/module.css (3 days)
http://itp.ne.jp/css2/pc/cms/pref_map/prefmap.css (3 days)
http://itp.ne.jp/css2/pc/cms/slick-theme.css (3 days)
http://itp.ne.jp/css2/pc/cms/slick.css (3 days)
http://itp.ne.jp/css2/pc/cms/topmodule.css (3 days)
http://itp.ne.jp/img2/pc/SEARCHRESULT_1_HELP.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/areasubtop/tiiki12/common/area03.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/arrow.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/ec/slide-next.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/ec/slide-prev.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-beauty.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-business.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-ceremony.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-dentist.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-gourmet.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-health.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-hobby.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-house.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-leisurepng.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-lesson.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-life.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-medical.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-motor.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-pet.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-public.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-shopping.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/g-icon-travel.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-ad-info.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-area-info.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-ec.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-genre.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-i-info.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-map.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-search.png (3 days)
http://itp.ne.jp/img2/pc/cms/common/icon-topic.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/camp01-icon.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/camp02-icon.gif (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/header/header.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-business.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-ec.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-foreign.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-japan.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-medical.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/image-sodan.png (3 days)
http://itp.ne.jp/img2/pc/cms/itptop/up-icon.gif (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/icon_back.png (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/japamap_TPkun2016June.png (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_all.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_chubu.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_chugoku.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_kansai.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_kanto.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_kyushu.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_shikoku.jpg (3 days)
http://itp.ne.jp/img2/pc/cms/pref_map/map_tohoku.jpg (3 days)
http://itp.ne.jp/img2/pc/sprite.png (3 days)
http://itp.ne.jp/js/pc/cms/ui.js (3 days)
http://itp.ne.jp/js2/libs/jquery-1.7.1.min.js (3 days)
http://itp.ne.jp/js2/libs/modernizr-2.6.2.js (3 days)
http://itp.ne.jp/js2/pc/cmn/common.js (3 days)
http://itp.ne.jp/js2/pc/cmn/plugins.js (3 days)
http://itp.ne.jp/js2/pc/cmn/script.js (3 days)
http://itp.ne.jp/js2/pc/cms/pickup-random.js (3 days)
http://itp.ne.jp/js2/pc/cms/pref_map/main.js (3 days)
http://itp.ne.jp/js2/pc/cms/slick.js (3 days)
http://itp.ne.jp/js2/pc/cms/slickset.js (3 days)
http://itp.ne.jp/js2/pc/personalize/personalize.js (3 days)
http://itp.ne.jp/js2/pc/search/search_common_box.js (3 days)
http://itp.ne.jp/js2/pc/search/top.js (3 days)
http://itp.ne.jp/shopping/images/hobby-item04.png (3 days)
http://itp.ne.jp/shopping/images/hobby-item05.png (3 days)
http://itp.ne.jp/shopping/images/present-item03.png (3 days)
http://itp.ne.jp/shopping/images/present-item04.png (3 days)
http://itp.ne.jp/shopping/images/present-item05.png (3 days)
http://itp.ne.jp/shopping/images/present-item06.png (3 days)
http://itp.ne.jp/shopping/images/present-item07.png (3 days)
http://itp.ne.jp/shopping/images/present-item08.png (3 days)
http://itp.ne.jp/shopping/images/sanchi-item01.png (3 days)
http://itp.ne.jp/shopping/images/sanchi-item22.png (3 days)
http://itp.ne.jp/shopping/images/sanchi-item31.png (3 days)
http://itp.ne.jp/shopping/images/sanchi-item32.png (3 days)
http://itp.ne.jp/vl/vl_ps.js (3 days)

priority - 10 Optimize images

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

Optimize the following images to reduce their size by 100.3KiB (51% reduction).

Compressing and resizing http://itp.ne.jp/topics/img/cmk/160608.jpg could save 77.5KiB (93% reduction).
Compressing and resizing http://itp.ne.jp/img2/pc/cms/itptop/camp01-icon.png could save 4.9KiB (58% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_chugoku.jpg could save 4.3KiB (19% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_kansai.jpg could save 4KiB (21% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_shikoku.jpg could save 3.3KiB (21% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_kyushu.jpg could save 3KiB (15% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_chubu.jpg could save 978B (12% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/icon_back.png could save 896B (82% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/SEARCHRESULT_1_HELP.jpg could save 834B (12% reduction).
Losslessly compressing http://itp.ne.jp/img2/pc/cms/pref_map/map_kanto.jpg could save 799B (11% reduction).

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

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

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://itp.ne.jp/js2/libs/modernizr-2.6.2.js
http://itp.ne.jp/js2/pc/personalize/personalize.js
http://itp.ne.jp/js2/libs/jquery-1.7.1.min.js
http://itp.ne.jp/js2/pc/cms/pref_map/main.js
http://itp.ne.jp/js2/pc/cms/slick.js
http://itp.ne.jp/js2/pc/cms/slickset.js

Optimize CSS Delivery of the following:

http://itp.ne.jp/css2/pc/cmn/style.css
http://itp.ne.jp/css2/pc/cmn/desktop.css
http://itp.ne.jp/css2/pc/cmn/small.css
http://itp.ne.jp/css2/pc/cms/footer.css
http://itp.ne.jp/css2/pc/cms/import_pc.css
http://itp.ne.jp/css2/pc/cms/area_pickup.css
http://itp.ne.jp/css2/pc/cms/pref_map/prefmap.css
http://itp.ne.jp/css2/pc/cms/module.css
http://itp.ne.jp/css2/pc/cms/ec-weekly.css
http://itp.ne.jp/css2/pc/cms/slick.css
http://itp.ne.jp/css2/pc/cms/slick-theme.css
http://itp.ne.jp/css2/pc/cms/topmodule.css
http://itp.ne.jp/css2/pc/cms/footer.css

priority - 3 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://itp.ne.jp/
http://itp.ne.jp/qp/;jsessionid=CD6DA2CF695FED082EE1F7E9223C72B5?rf=1
http://itp.ne.jp/?rf=1

priority - 1 Minify 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 12.9KiB (24% reduction).

Minifying http://itp.ne.jp/js2/pc/cmn/script.js could save 3.5KiB (32% reduction) after compression.
Minifying http://itp.ne.jp/js2/pc/cms/slick.js could save 3.1KiB (24% reduction) after compression.
Minifying http://itp.ne.jp/vl/vl_ps.js could save 2.7KiB (20% reduction) after compression.
Minifying http://itp.ne.jp/js2/libs/modernizr-2.6.2.js could save 1.2KiB (16% reduction) after compression.
Minifying http://itp.ne.jp/js2/pc/cmn/common.js could save 1KiB (29% reduction) after compression.
Minifying http://itp.ne.jp/js2/pc/personalize/personalize.js could save 777B (54% reduction) after compression.
Minifying http://d-cache.microad.jp/js/bl_track.js could save 548B (16% reduction).

priority - 1 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 9.3KiB (20% reduction).

Minifying http://itp.ne.jp/css2/pc/cmn/desktop.css could save 3.5KiB (14% reduction) after compression.
Minifying http://itp.ne.jp/css2/pc/cms/module.css could save 3.2KiB (47% reduction) after compression.
Minifying http://itp.ne.jp/css2/pc/cmn/small.css could save 974B (18% reduction) after compression.
Minifying http://itp.ne.jp/css2/pc/cms/pref_map/prefmap.css could save 867B (12% reduction) after compression.
Minifying http://itp.ne.jp/css2/pc/cms/topmodule.css could save 850B (24% reduction) after compression.

priority - 0 Enable 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 2.4KiB (68% reduction).

Compressing http://d-cache.microad.jp/js/bl_track.js could save 2.4KiB (68% reduction).

itp.ne.jp Desktop Resources

Total Resources122
Number of Hosts17
Static Resources108
JavaScript Resources28
CSS Resources15

itp.ne.jp Desktop Resource Breakdown

itp.ne.jp mobile page speed rank

Last tested: 2016-06-14


Mobile Speed Bad
62/100

itp.ne.jp Mobile Speed Test Quick Summary


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

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

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js
http://itp.ne.jp/js2/sp2/common/lib/jquery/jquery.easing.js
http://itp.ne.jp/js2/sp2/common/base.js?20160331
http://itp.ne.jp/js2/sp2/common/flipsnap.min.js?20160331
http://itp.ne.jp/js2/sp2/common/remodal.js?20160331
http://itp.ne.jp/js2/sp2/common/top.js?20160414
http://itp.ne.jp/js2/sp2/common/favoriteShopRegist.js?20160331
http://itp.ne.jp/js2/sp2/common/menu_login.js?20160331
http://bjad.durasite.net/A-affiliate2/mobile?site=…&ord=307700829.5804262
http://map.api.goo.ne.jp/keyitp-smp/authkey_conten…p=FVS-TOP-001&enc=SJIS
http://map.api.goo.ne.jp/key8/authkey_auth.php?key…01&r=http://itp.ne.jp/
http://itp.ne.jp/vl/vl_s_ct.js

Optimize CSS Delivery of the following:

http://itp.ne.jp/css2/sp2/common/YUI/reset.css?20160331
http://itp.ne.jp/css2/sp2/common/base.css?20160414
http://itp.ne.jp/css2/sp2/common/result.css?20160331
http://itp.ne.jp/css2/sp2/common/top.css?20160331
http://itp.ne.jp/css2/sp2/common/scroll-map.css?20160331
http://itp.ne.jp/css2/sp2/common/remodal.css?20160331

priority - 21 Leverage 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://itp.ne.jp/api/stats/pv.json (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-N4QD6H (16.2 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://itp.ne.jp/css2/sp2/common/YUI/reset.css?20160331 (3 days)
http://itp.ne.jp/css2/sp2/common/base.css?20160414 (3 days)
http://itp.ne.jp/css2/sp2/common/remodal.css?20160331 (3 days)
http://itp.ne.jp/css2/sp2/common/result.css?20160331 (3 days)
http://itp.ne.jp/css2/sp2/common/scroll-map.css?20160331 (3 days)
http://itp.ne.jp/css2/sp2/common/top.css?20160331 (3 days)
http://itp.ne.jp/img2/sp2/common/header/logo_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/arrow_01_left.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/arrow_01_right.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_02.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_03.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_05.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_07.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_08.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_09.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_10.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_13.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_14.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/gnav_15.png (3 days)
http://itp.ne.jp/img2/sp2/common/icon/icon_x_02.png (3 days)
http://itp.ne.jp/img2/sp2/common/map/ajax-loader-1.gif (3 days)
http://itp.ne.jp/img2/sp2/common/map/icon_here_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/map/minus.png (3 days)
http://itp.ne.jp/img2/sp2/common/map/plus.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/btn_help_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_back_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_close_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_close_02.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_entry_btn_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_info_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_list_btn_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_list_btn_02.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_plus_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/icon_search_btn_01.png (3 days)
http://itp.ne.jp/img2/sp2/common/top/weather/111.png (3 days)
http://itp.ne.jp/js2/sp2/common/base.js?20160331 (3 days)
http://itp.ne.jp/js2/sp2/common/favoriteShopRegist.js?20160331 (3 days)
http://itp.ne.jp/js2/sp2/common/flipsnap.min.js?20160331 (3 days)
http://itp.ne.jp/js2/sp2/common/lib/jquery/jquery.easing.js (3 days)
http://itp.ne.jp/js2/sp2/common/menu_login.js?20160331 (3 days)
http://itp.ne.jp/js2/sp2/common/remodal.js?20160331 (3 days)
http://itp.ne.jp/js2/sp2/common/top.js?20160414 (3 days)
http://itp.ne.jp/vl/vl_s_ct.js (3 days)

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 4% of the final above-the-fold content could be rendered with the full HTML response.

priority - 2 Minify 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 17.1KiB (32% reduction).

Minifying http://itp.ne.jp/js2/sp2/common/top.js?20160414 could save 9.4KiB (38% reduction) after compression.
Minifying http://itp.ne.jp/vl/vl_s_ct.js could save 3.8KiB (23% reduction) after compression.
Minifying http://itp.ne.jp/js2/sp2/common/remodal.js?20160331 could save 1.4KiB (33% reduction) after compression.
Minifying http://itp.ne.jp/js2/sp2/common/lib/jquery/jquery.easing.js could save 1.1KiB (58% reduction) after compression.
Minifying http://itp.ne.jp/js2/sp2/common/base.js?20160331 could save 824B (23% reduction) after compression.
Minifying http://itp.ne.jp/js2/sp2/common/menu_login.js?20160331 could save 601B (32% reduction) after compression.

priority - 1 Optimize images

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

Optimize the following images to reduce their size by 3.4KiB (42% reduction).

Losslessly compressing http://itp.ne.jp/img2/sp2/common/top/icon_info_01.png could save 1.4KiB (52% reduction).
Losslessly compressing http://itp.ne.jp/img2/sp2/common/top/icon_plus_01.png could save 859B (84% reduction).
Losslessly compressing http://itp.ne.jp/img2/sp2/common/top/icon_list_btn_02.png could save 631B (37% reduction).
Losslessly compressing http://itp.ne.jp/img2/sp2/common/map/icon_here_01.png could save 573B (20% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.9KiB (17% reduction).

Minifying http://itp.ne.jp/css2/sp2/common/base.css?20160414 could save 1KiB (13% reduction) after compression.
Minifying http://itp.ne.jp/css2/sp2/common/top.css?20160331 could save 871B (24% reduction) after compression.

itp.ne.jp Mobile Resources

Total Resources83
Number of Hosts9
Static Resources77
JavaScript Resources16
CSS Resources6

itp.ne.jp Mobile Resource Breakdown

itp.ne.jp mobile page usability

Last tested: 2016-06-14


Mobile Usability Good
97/100

itp.ne.jp Mobile Usability Test Quick Summary


priority - 2 Size 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 <div id="inBtnPlus"></div> is close to 1 other tap targets.

The tap target <a href="javascript:void(0);" class="closeBtn"></a> is close to 1 other tap targets.

itp.ne.jp Mobile Resources

Total Resources83
Number of Hosts9
Static Resources77
JavaScript Resources16
CSS Resources6

itp.ne.jp Mobile Resource Breakdown

itp.ne.jp similar domains

Similar domains:
www.itp.com
www.itp.net
www.itp.org
www.itp.info
www.itp.biz
www.itp.us
www.itp.mobi
www.tp.ne.jp
www.itp.ne.jp
www.utp.ne.jp
www.iutp.ne.jp
www.uitp.ne.jp
www.jtp.ne.jp
www.ijtp.ne.jp
www.jitp.ne.jp
www.ktp.ne.jp
www.iktp.ne.jp
www.kitp.ne.jp
www.otp.ne.jp
www.iotp.ne.jp
www.oitp.ne.jp
www.ip.ne.jp
www.irp.ne.jp
www.itrp.ne.jp
www.irtp.ne.jp
www.ifp.ne.jp
www.itfp.ne.jp
www.iftp.ne.jp
www.igp.ne.jp
www.itgp.ne.jp
www.igtp.ne.jp
www.iyp.ne.jp
www.ityp.ne.jp
www.iytp.ne.jp
www.it.ne.jp
www.ito.ne.jp
www.itpo.ne.jp
www.itop.ne.jp
www.itl.ne.jp
www.itpl.ne.jp
www.itlp.ne.jp

itp.ne.jp Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


itp.ne.jp TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.