INTAGE.CO.JP 市場調査・マーケティングリサーチならインテージ


intage.co.jp website information.

intage.co.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 intage.co.jp domain:

  • ns2.intage.co.jp
  • ns6-tk02.ocn.ad.jp
  • ns1.intage.co.jp

and probably website intage.co.jp is hosted by AKAMAI-AS - Akamai Technologies, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AKAMAI-AS - Akamai Technologies, Inc., US hosting company.

According to Alexa traffic rank the highest website intage.co.jp position was 5379 (in the world). The lowest Alexa rank position was 912005. Now website intage.co.jp ranked in Alexa database as number 218385 (in the world).

Website intage.co.jp Desktop speed measurement score (54/100) is better than the results of 28.19% of other sites shows that the page desktop performance can be improved.

intage.co.jp Mobile usability score (62/100) is better than the results of 7.29% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of intage.co.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.

Weekly Rank Report

DateRankChange
Sep-21-2024 218,385-1,671
Sep-20-2024 216,7141,938
Sep-19-2024 218,652541
Sep-18-2024 219,193-4,406
Sep-17-2024 214,7874,405
Sep-16-2024 219,192-1,332
Sep-15-2024 217,8604,715

Advertisement

intage.co.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.



intage.co.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.


intage.co.jp server information

Servers Location

IP Address
210.154.97.67
Country
Japan
Region
Tokyo
City
Tokyo

intage.co.jp desktop page speed rank

Last tested: 2018-10-08


Desktop Speed Bad
54/100

intage.co.jp Desktop Speed Test Quick Summary


priority - 41 Optimize images

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

Optimize the following images to reduce their size by 402.7KiB (38% reduction).

Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s03.jpg could save 30.6KiB (48% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s05.jpg could save 29.7KiB (55% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s04.jpg could save 26.7KiB (56% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s02.jpg could save 26.3KiB (44% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ation_banner_s06_3.jpg could save 26.1KiB (39% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s04.jpg could save 22.7KiB (52% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s01.jpg could save 22.2KiB (56% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s07.jpg could save 21.8KiB (60% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s03.jpg could save 19.9KiB (71% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s08.jpg could save 16.2KiB (58% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnSlide01/next2.png could save 15.6KiB (97% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnSlide01/prev2.png could save 15.4KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/btn_ft_search.png could save 15.4KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/slideBlock01/next.png could save 15.3KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/slideBlock01/prev.png could save 15.3KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s06.jpg could save 15.2KiB (53% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s02.jpg could save 15.2KiB (48% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/btn_pagetop.png could save 15KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnArea/btn_rss.png could save 14.9KiB (93% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…_mailmagazine_mini.png could save 3.3KiB (89% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…d_btn_contact_mini.png could save 3.3KiB (91% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ge/sl_btn_chousa_s.png could save 3.3KiB (8% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…image/top/h1_top_0.png could save 2KiB (12% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/top/btn_scroll.png could save 1.1KiB (66% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…k01/bg_gradationGR.jpg could save 930B (3% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/newsList/ar_newslist.png could save 922B (87% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ation_banner_s01_1.jpg could save 921B (3% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/ar_footer.png could save 917B (89% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…Link01/icon_menu01.png could save 911B (89% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/top/topimage.jpg could save 906B (1% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…kotei_banner_s05_0.jpg could save 904B (5% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/bg_footer.jpg could save 887B (1% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…/icon_ft_marketing.png could save 856B (77% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…er/icon_ft_company.png could save 850B (76% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…r/icon_ft_solution.png could save 834B (69% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/icon_ft_news.png could save 829B (71% reduction).

priority - 24 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://js.ptengine.jp/7cfdfde6.js (expiration not specified)
http://jsv2.ptengine.jp/pta.js (expiration not specified)
http://jsv2.ptengine.jp/pts.js (expiration not specified)
http://track.list-finder.jp/js/ja/track.js (60 seconds)
http://y.nakanohito.jp/ua/ya.js (5 minutes)
http://i.yimg.jp/images/listing/tool/ywapb/pb.js (10.1 minutes)
http://s.yjtag.jp/tag.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-W9SVNN (16.2 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.intage.co.jp/common/css/btnSlide01.css (3 days)
http://www.intage.co.jp/common/css/common.css (3 days)
http://www.intage.co.jp/common/css/default.css (3 days)
http://www.intage.co.jp/common/css/import.css (3 days)
http://www.intage.co.jp/common/css/print.css (3 days)
http://www.intage.co.jp/common/css/slideBlock01.css (3 days)
http://www.intage.co.jp/common/css/top.css (3 days)
http://www.intage.co.jp/common/images/module_parts/btnArea/btn_rss.png (3 days)
http://www.intage.co.jp/common/images/module_parts…Link01/icon_menu01.png (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/bx_loader.gif (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/next2.png (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/prev2.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/ar_footer.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/bg_footer.jpg (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/btn_ft_search.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/btn_pagetop.png (3 days)
http://www.intage.co.jp/common/images/module_parts…icon_ft_about_site.png (3 days)
http://www.intage.co.jp/common/images/module_parts…er/icon_ft_company.png (3 days)
http://www.intage.co.jp/common/images/module_parts…er/icon_ft_contact.png (3 days)
http://www.intage.co.jp/common/images/module_parts…/icon_ft_marketing.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/icon_ft_news.png (3 days)
http://www.intage.co.jp/common/images/module_parts…r/icon_ft_solution.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/logo_s.png (3 days)
http://www.intage.co.jp/common/images/module_parts/header/bg_header.png (3 days)
http://www.intage.co.jp/common/images/module_parts…d_btn_contact_mini.png (3 days)
http://www.intage.co.jp/common/images/module_parts…der/hd_btn_english.png (3 days)
http://www.intage.co.jp/common/images/module_parts…_mailmagazine_mini.png (3 days)
http://www.intage.co.jp/common/images/module_parts/header/icon_search.png (3 days)
http://www.intage.co.jp/common/images/module_parts/newsList/ar_newslist.png (3 days)
http://www.intage.co.jp/common/images/module_parts…k01/bg_gradationGR.jpg (3 days)
http://www.intage.co.jp/common/images/module_parts/slideBlock01/next.png (3 days)
http://www.intage.co.jp/common/images/module_parts/slideBlock01/prev.png (3 days)
http://www.intage.co.jp/common/images/top/ar_top.png (3 days)
http://www.intage.co.jp/common/images/top/btn_scroll.png (3 days)
http://www.intage.co.jp/common/js/classie.js (3 days)
http://www.intage.co.jp/common/js/common.js (3 days)
http://www.intage.co.jp/common/js/global_navigation.js (3 days)
http://www.intage.co.jp/common/js/jquery-1.11.1.min.js (3 days)
http://www.intage.co.jp/common/js/jquery.backgroundSize.js (3 days)
http://www.intage.co.jp/common/js/jquery.bxslider.min.js (3 days)
http://www.intage.co.jp/common/js/loader.js (3 days)
http://www.intage.co.jp/common/js/modernizr.custom.js (3 days)
http://www.intage.co.jp/common/js/top.js (3 days)
http://www.intage.co.jp/common/js/uisearch.js (3 days)
http://www.intage.co.jp/piwik/piwik.js (3 days)
http://www.intage.co.jp/sites/default/files/field/…ge/sl_btn_chousa_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/sl_btn_gojuuon_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/sl_btn_gyoukai_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…age/sl_btn_kadai_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…ation_banner_s01_1.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s02.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s03.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s04.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s05.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…ation_banner_s06_3.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…image/top/h1_top_0.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s01.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s02.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s03.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s04.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…kotei_banner_s05_0.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s06.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s07.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s08.jpg (3 days)
http://www.intage.co.jp/sites/default/files/top/topimage.jpg (3 days)

priority - 16 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 151.9KiB (68% reduction).

Compressing http://www.intage.co.jp/common/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
Compressing http://wv004.sibulla.com/dekatag/access?id=n01SHXf1 could save 30.9KiB (80% reduction).
Compressing http://www.intage.co.jp/piwik/piwik.js could save 27.1KiB (65% reduction).
Compressing http://www.intage.co.jp/common/js/jquery.bxslider.min.js could save 13.7KiB (73% reduction).
Compressing http://www.intage.co.jp/common/js/jquery.backgroundSize.js could save 4.9KiB (65% reduction).
Compressing http://www.intage.co.jp/common/js/modernizr.custom.js could save 4.1KiB (55% reduction).
Compressing http://www.intage.co.jp/common/js/uisearch.js could save 3.5KiB (56% reduction).
Compressing http://track.list-finder.jp/js/ja/track.js could save 2.8KiB (70% reduction).
Compressing http://www.intage.co.jp/common/js/common.js could save 2.2KiB (67% reduction).
Compressing http://www.intage.co.jp/common/js/classie.js could save 1.1KiB (62% reduction).
Compressing http://www.intage.co.jp/common/js/global_navigation.js could save 515B (59% reduction).

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

Your page has 10 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.

Optimize CSS Delivery of the following:

http://www.intage.co.jp/common/css/top.css
http://www.intage.co.jp/common/css/slideBlock01.css
http://www.intage.co.jp/common/css/btnSlide01.css
http://www.intage.co.jp/common/css/import.css
http://www.intage.co.jp/common/css/default.css
http://www.intage.co.jp/common/css/common.css
http://www.intage.co.jp/common/css/print.css
http://www.intage.co.jp/common/css/top.css
http://www.intage.co.jp/common/css/slideBlock01.css
http://www.intage.co.jp/common/css/btnSlide01.css

priority - 3 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 25KiB (44% reduction).

Minifying http://wv004.sibulla.com/dekatag/access?id=n01SHXf1 could save 18.9KiB (50% reduction).
Minifying http://www.intage.co.jp/common/js/jquery.backgroundSize.js could save 3.2KiB (43% reduction).
Minifying http://www.intage.co.jp/common/js/uisearch.js could save 1.4KiB (23% reduction).
Minifying http://www.intage.co.jp/common/js/classie.js could save 882B (49% reduction).
Minifying http://www.intage.co.jp/common/js/common.js could save 711B (21% 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 1KiB (6% reduction).

Minifying http://www.intage.co.jp/common/css/common.css could save 1KiB (6% reduction) after compression.

priority - 0 Minify 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 855B (14% reduction).

Minifying http://www.intage.co.jp/ could save 855B (14% reduction) after compression.

intage.co.jp Desktop Resources

Total Resources96
Number of Hosts21
Static Resources76
JavaScript Resources28
CSS Resources7

intage.co.jp Desktop Resource Breakdown

intage.co.jp mobile page speed rank

Last tested: 2018-10-08


Mobile Speed Bad
46/100

intage.co.jp Mobile Speed Test Quick Summary


priority - 41 Optimize images

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

Optimize the following images to reduce their size by 402.7KiB (38% reduction).

Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s03.jpg could save 30.6KiB (48% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s05.jpg could save 29.7KiB (55% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s04.jpg could save 26.7KiB (56% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s02.jpg could save 26.3KiB (44% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ation_banner_s06_3.jpg could save 26.1KiB (39% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…otation_banner_s04.jpg could save 22.7KiB (52% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s01.jpg could save 22.2KiB (56% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s07.jpg could save 21.8KiB (60% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s03.jpg could save 19.9KiB (71% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s08.jpg could save 16.2KiB (58% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnSlide01/next2.png could save 15.6KiB (97% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnSlide01/prev2.png could save 15.4KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/btn_ft_search.png could save 15.4KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/slideBlock01/next.png could save 15.3KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/slideBlock01/prev.png could save 15.3KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s06.jpg could save 15.2KiB (53% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s02.jpg could save 15.2KiB (48% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/btn_pagetop.png could save 15KiB (96% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/btnArea/btn_rss.png could save 14.9KiB (93% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…_mailmagazine_mini.png could save 3.3KiB (89% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…d_btn_contact_mini.png could save 3.3KiB (91% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ge/sl_btn_chousa_s.png could save 3.3KiB (8% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…image/top/h1_top_0.png could save 2KiB (12% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/top/btn_scroll.png could save 1.1KiB (66% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…k01/bg_gradationGR.jpg could save 930B (3% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/newsList/ar_newslist.png could save 922B (87% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…ation_banner_s01_1.jpg could save 921B (3% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/ar_footer.png could save 917B (89% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…Link01/icon_menu01.png could save 911B (89% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/top/topimage.jpg could save 906B (1% reduction).
Losslessly compressing http://www.intage.co.jp/sites/default/files/field/…kotei_banner_s05_0.jpg could save 904B (5% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/bg_footer.jpg could save 887B (1% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…/icon_ft_marketing.png could save 856B (77% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…er/icon_ft_company.png could save 850B (76% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts…r/icon_ft_solution.png could save 834B (69% reduction).
Losslessly compressing http://www.intage.co.jp/common/images/module_parts/footer/icon_ft_news.png could save 829B (71% reduction).

priority - 35 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://js.ptengine.jp/7cfdfde6.js (expiration not specified)
http://jsv2.ptengine.jp/pta.js (expiration not specified)
http://jsv2.ptengine.jp/pts.js (expiration not specified)
http://track.list-finder.jp/js/ja/track.js (60 seconds)
http://y.nakanohito.jp/ua/ya.js (5 minutes)
http://i.yimg.jp/images/listing/tool/ywapb/pb.js (10 minutes)
http://s.yjtag.jp/tag.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-W9SVNN (16.2 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.intage.co.jp/common/css/btnSlide01.css (3 days)
http://www.intage.co.jp/common/css/common.css (3 days)
http://www.intage.co.jp/common/css/default.css (3 days)
http://www.intage.co.jp/common/css/import.css (3 days)
http://www.intage.co.jp/common/css/print.css (3 days)
http://www.intage.co.jp/common/css/slideBlock01.css (3 days)
http://www.intage.co.jp/common/css/top.css (3 days)
http://www.intage.co.jp/common/images/module_parts/btnArea/btn_rss.png (3 days)
http://www.intage.co.jp/common/images/module_parts…Link01/icon_menu01.png (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/bx_loader.gif (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/next2.png (3 days)
http://www.intage.co.jp/common/images/module_parts/btnSlide01/prev2.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/ar_footer.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/bg_footer.jpg (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/btn_ft_search.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/btn_pagetop.png (3 days)
http://www.intage.co.jp/common/images/module_parts…icon_ft_about_site.png (3 days)
http://www.intage.co.jp/common/images/module_parts…er/icon_ft_company.png (3 days)
http://www.intage.co.jp/common/images/module_parts…er/icon_ft_contact.png (3 days)
http://www.intage.co.jp/common/images/module_parts…/icon_ft_marketing.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/icon_ft_news.png (3 days)
http://www.intage.co.jp/common/images/module_parts…r/icon_ft_solution.png (3 days)
http://www.intage.co.jp/common/images/module_parts/footer/logo_s.png (3 days)
http://www.intage.co.jp/common/images/module_parts/header/bg_header.png (3 days)
http://www.intage.co.jp/common/images/module_parts…d_btn_contact_mini.png (3 days)
http://www.intage.co.jp/common/images/module_parts…der/hd_btn_english.png (3 days)
http://www.intage.co.jp/common/images/module_parts…_mailmagazine_mini.png (3 days)
http://www.intage.co.jp/common/images/module_parts/header/icon_search.png (3 days)
http://www.intage.co.jp/common/images/module_parts/newsList/ar_newslist.png (3 days)
http://www.intage.co.jp/common/images/module_parts…k01/bg_gradationGR.jpg (3 days)
http://www.intage.co.jp/common/images/module_parts/slideBlock01/next.png (3 days)
http://www.intage.co.jp/common/images/module_parts/slideBlock01/prev.png (3 days)
http://www.intage.co.jp/common/images/top/ar_top.png (3 days)
http://www.intage.co.jp/common/images/top/btn_scroll.png (3 days)
http://www.intage.co.jp/common/js/classie.js (3 days)
http://www.intage.co.jp/common/js/common.js (3 days)
http://www.intage.co.jp/common/js/global_navigation.js (3 days)
http://www.intage.co.jp/common/js/jquery-1.11.1.min.js (3 days)
http://www.intage.co.jp/common/js/jquery.backgroundSize.js (3 days)
http://www.intage.co.jp/common/js/jquery.bxslider.min.js (3 days)
http://www.intage.co.jp/common/js/loader.js (3 days)
http://www.intage.co.jp/common/js/modernizr.custom.js (3 days)
http://www.intage.co.jp/common/js/top.js (3 days)
http://www.intage.co.jp/common/js/uisearch.js (3 days)
http://www.intage.co.jp/piwik/piwik.js (3 days)
http://www.intage.co.jp/sites/default/files/field/…ge/sl_btn_chousa_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/sl_btn_gojuuon_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/sl_btn_gyoukai_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…age/sl_btn_kadai_s.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…ation_banner_s01_1.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s02.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s03.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s04.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…otation_banner_s05.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…ation_banner_s06_3.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…image/top/h1_top_0.png (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s01.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s02.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s03.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s04.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…kotei_banner_s05_0.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s06.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s07.jpg (3 days)
http://www.intage.co.jp/sites/default/files/field/…e/kotei_banner_s08.jpg (3 days)
http://www.intage.co.jp/sites/default/files/top/topimage.jpg (3 days)

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

Your page has 10 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.

Optimize CSS Delivery of the following:

http://www.intage.co.jp/common/css/top.css
http://www.intage.co.jp/common/css/slideBlock01.css
http://www.intage.co.jp/common/css/btnSlide01.css
http://www.intage.co.jp/common/css/import.css
http://www.intage.co.jp/common/css/default.css
http://www.intage.co.jp/common/css/common.css
http://www.intage.co.jp/common/css/print.css
http://www.intage.co.jp/common/css/top.css
http://www.intage.co.jp/common/css/slideBlock01.css
http://www.intage.co.jp/common/css/btnSlide01.css

priority - 16 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 151.9KiB (68% reduction).

Compressing http://www.intage.co.jp/common/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
Compressing http://wv004.sibulla.com/dekatag/access?id=n01SHXf1 could save 30.9KiB (80% reduction).
Compressing http://www.intage.co.jp/piwik/piwik.js could save 27.1KiB (65% reduction).
Compressing http://www.intage.co.jp/common/js/jquery.bxslider.min.js could save 13.7KiB (73% reduction).
Compressing http://www.intage.co.jp/common/js/jquery.backgroundSize.js could save 4.9KiB (65% reduction).
Compressing http://www.intage.co.jp/common/js/modernizr.custom.js could save 4.1KiB (55% reduction).
Compressing http://www.intage.co.jp/common/js/uisearch.js could save 3.5KiB (56% reduction).
Compressing http://track.list-finder.jp/js/ja/track.js could save 2.8KiB (70% reduction).
Compressing http://www.intage.co.jp/common/js/common.js could save 2.2KiB (67% reduction).
Compressing http://www.intage.co.jp/common/js/classie.js could save 1.1KiB (62% reduction).
Compressing http://www.intage.co.jp/common/js/global_navigation.js could save 515B (59% reduction).

priority - 3 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 25KiB (44% reduction).

Minifying http://wv004.sibulla.com/dekatag/access?id=n01SHXf1 could save 18.9KiB (50% reduction).
Minifying http://www.intage.co.jp/common/js/jquery.backgroundSize.js could save 3.2KiB (43% reduction).
Minifying http://www.intage.co.jp/common/js/uisearch.js could save 1.4KiB (23% reduction).
Minifying http://www.intage.co.jp/common/js/classie.js could save 882B (49% reduction).
Minifying http://www.intage.co.jp/common/js/common.js could save 711B (21% 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 1KiB (6% reduction).

Minifying http://www.intage.co.jp/common/css/common.css could save 1KiB (6% reduction) after compression.

priority - 0 Minify 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 855B (14% reduction).

Minifying http://www.intage.co.jp/ could save 855B (14% reduction) after compression.

intage.co.jp Mobile Resources

Total Resources96
Number of Hosts21
Static Resources76
JavaScript Resources28
CSS Resources7

intage.co.jp Mobile Resource Breakdown

intage.co.jp mobile page usability

Last tested: 2018-10-08


Mobile Usability Bad
62/100

intage.co.jp Mobile Usability Test Quick Summary


priority - 40 Use 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.

HOME renders only 4 pixels tall (14 CSS pixels).

ソリューション and 5 others render only 4 pixels tall (14 CSS pixels).

インテージは、ビジネスの現場と生活者視点を起点に and 1 others render only 5 pixels tall (18 CSS pixels).

インテージが解決できること renders only 8 pixels tall (26 CSS pixels).

ソリューションから探す and 3 others render only 5 pixels tall (16 CSS pixels).

ニュース・お知らせ renders only 4 pixels tall (14 CSS pixels).

イベント・セミナー and 2 others render only 4 pixels tall (14 CSS pixels).

2015/05/19 and 4 others render only 4 pixels tall (14 CSS pixels).

デジタルマーケティング施策の…nel』を4月1日にリリース and 4 others render only 4 pixels tall (14 CSS pixels).

最新のニュース・お知らせ 一覧を見る renders only 4 pixels tall (14 CSS pixels).

このサイトについて and 3 others render only 4 pixels tall (13 CSS pixels).

広報(調査データ引用・転載、…頼など)に関するお問い合わせ and 23 others render only 4 pixels tall (13 CSS pixels).
インテージが解決できること renders only 4 pixels tall (13 CSS pixels).

マーケティング用語集 renders only 4 pixels tall (14 CSS pixels).
Copyright © 20…ghts Reserved. renders only 2 pixels tall (8 CSS pixels).

priority - 15 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 <a href="/">株式会社インテージ</a> is close to 1 other tap targets.

The tap target <a href="/english/">ENGLISH</a> is close to 2 other tap targets.

The tap target <div id="sb-search" class="sb-search"></div> is close to 3 other tap targets.

The tap target <input type="submit" class="sb-search-submit"> is close to 3 other tap targets.

The tap target <a href="/contact/">お問い合わせ</a> is close to 4 other tap targets.

The tap target <a href="https://www.in…m_mailmagazine">インテージメールマガジン</a> is close to 2 other tap targets.

The tap target <a href="/company/" class="">会社情報</a> and 3 others are close to other tap targets.

The tap target <a href="" class="bx-prev">Prev</a> is close to 1 other tap targets.

The tap target <a href="" class="bx-next">Next</a> is close to 1 other tap targets.

The tap target <a href="#tab01" class="active">ニュース・お知らせ</a> is close to 1 other tap targets.

The tap target <a href="#tab02">メディア掲載情報</a> and 1 others are close to other tap targets.

The tap target <a href="/topics/news/20150519">業界最大規模の小売店パネルデ…ケットデータを正式に提供開始</a> and 4 others are close to other tap targets.

The tap target <a href="/topics/news/feed/">RSS Feed</a> is close to 1 other tap targets.

The tap target <a href="/topics/news">最新のニュース・お知らせ 一覧を見る</a> is close to 1 other tap targets.

The tap target <a href="/company">会社情報</a> and 3 others are close to other tap targets.

The tap target <a href="/company">インテージとは</a> and 23 others are close to other tap targets.
The tap target <a href="/library/glossary">マーケティング用語集</a> is close to 1 other tap targets.
The tap target <input type="submit" class="searchBtn"> is close to 1 other tap targets.

priority - 10 Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

Configuring a viewport specifying width=device-width instead of width=1024 will allow your page to adapt for devices of various widths. This may require additional work to adapt your styling for smaller screens.

intage.co.jp similar domains

Similar domains:
www.intage.com
www.intage.net
www.intage.org
www.intage.info
www.intage.biz
www.intage.us
www.intage.mobi
www.ntage.co.jp
www.intage.co.jp
www.untage.co.jp
www.iuntage.co.jp
www.uintage.co.jp
www.jntage.co.jp
www.ijntage.co.jp
www.jintage.co.jp
www.kntage.co.jp
www.ikntage.co.jp
www.kintage.co.jp
www.ontage.co.jp
www.iontage.co.jp
www.ointage.co.jp
www.itage.co.jp
www.ibtage.co.jp
www.inbtage.co.jp
www.ibntage.co.jp
www.ihtage.co.jp
www.inhtage.co.jp
www.ihntage.co.jp
www.ijtage.co.jp
www.injtage.co.jp
www.imtage.co.jp
www.inmtage.co.jp
www.imntage.co.jp
www.inage.co.jp
www.inrage.co.jp
www.intrage.co.jp
www.inrtage.co.jp
www.infage.co.jp
www.intfage.co.jp
www.inftage.co.jp
www.ingage.co.jp
www.intgage.co.jp
www.ingtage.co.jp
www.inyage.co.jp
www.intyage.co.jp
www.inytage.co.jp
www.intge.co.jp
www.intqge.co.jp
www.intaqge.co.jp
www.intqage.co.jp
www.intwge.co.jp
www.intawge.co.jp
www.intwage.co.jp
www.intsge.co.jp
www.intasge.co.jp
www.intsage.co.jp
www.intzge.co.jp
www.intazge.co.jp
www.intzage.co.jp
www.intae.co.jp
www.intafe.co.jp
www.intagfe.co.jp
www.intafge.co.jp
www.intave.co.jp
www.intagve.co.jp
www.intavge.co.jp
www.intate.co.jp
www.intagte.co.jp
www.intatge.co.jp
www.intabe.co.jp
www.intagbe.co.jp
www.intabge.co.jp
www.intaye.co.jp
www.intagye.co.jp
www.intayge.co.jp
www.intahe.co.jp
www.intaghe.co.jp
www.intahge.co.jp
www.intag.co.jp
www.intagw.co.jp
www.intagew.co.jp
www.intagwe.co.jp
www.intags.co.jp
www.intages.co.jp
www.intagse.co.jp
www.intagd.co.jp
www.intaged.co.jp
www.intagde.co.jp
www.intagr.co.jp
www.intager.co.jp
www.intagre.co.jp

intage.co.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.


intage.co.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.