iee.jp website information.
iee.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.
No name server records were found.
and probably website iee.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 iee.jp position was 33687 (in the world). The lowest Alexa rank position was 994394. Now website iee.jp ranked in Alexa database as number 278961 (in the world).
Website iee.jp Desktop speed measurement score (72/100) is better than the results of 54.39% of other sites shows that the page desktop performance can be improved.
iee.jp Mobile usability score (98/100) is better than the results of 55.61% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of iee.jp (36/100) is better than the results of 14.78% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
Date | Rank | Change |
---|---|---|
Nov-15-2024 | 278,961 | -1,414 |
Nov-14-2024 | 277,547 | 5,375 |
Nov-13-2024 | 282,922 | 0 |
Nov-12-2024 | 282,922 | 0 |
Nov-11-2024 | 282,922 | 0 |
Nov-10-2024 | 282,922 | -9,630 |
Nov-09-2024 | 273,292 | 2,623 |
Advertisement
iee.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.
iee.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.
iee.jp server information
Servers Location
IP Address |
---|
Country |
---|
iee.jp desktop page speed rank
Last tested: 2015-10-20
iee.jp Desktop Speed Test Quick Summary
priority - 13 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://www.cgc.co.jp/iee_bnr/ohmsha.gif (expiration not specified)
http://www.cgc.co.jp/iee_bnr/toshiba.jpg (expiration not specified)
http://www.iee.jp/wp-content/plugins/count-per-day/counter.css (expiration not specified)
http://www.iee.jp/wp-content/plugins/custom_event/ev-widget.css (expiration not specified)
http://www.iee.jp/wp-content/plugins/easingsliderpro/images/loading.gif (expiration not specified)
http://www.iee.jp/wp-content/plugins/easingsliderp…show_icon_inactive.png (expiration not specified)
http://www.iee.jp/wp-content/plugins/lightbox-2-wo…htbox/css/lightbox.css (expiration not specified)
http://www.iee.jp/wp-content/plugins/lightbox-2-wo…/images/closelabel.gif (expiration not specified)
http://www.iee.jp/wp-content/plugins/lightbox-2-wo…box/images/loading.gif (expiration not specified)
http://www.iee.jp/wp-content/plugins/whats-new-genarator/image/list.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2013/06/251.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2013/06/252.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2013/08/bk.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2013/10/jhp.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2014/01/BN-250x40_4.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2014/04/head-400x100-b.png (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/05/cd678…2ca97a5a43-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/09/Ctaikai_2016-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/09/Dtaikai_2016-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/09/denki-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/09/icee2015_1-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/2015/10/takai2015-960x290.jpg (expiration not specified)
http://www.iee.jp/wp-content/uploads/honbu/img/wecc2015.gif (expiration not specified)
https://www.jstage.jst.go.jp/pub/ieejjournal/thumb…ieejjournal_135_10.jpg (expiration not specified)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 16 blocking script resources and 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.
Remove render-blocking JavaScript:
http://www.iee.jp/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://ajax.googleapis.com/ajax/libs/prototype/1.7…prototype.js?ver=1.7.1
http://www.iee.jp/wp-content/plugins/easingsliderp…eshow.min.js?ver=2.0.3
http://www.iee.jp/wp-content/plugins/post-list-gen…next-page.js?ver=1.2.4
http://www.iee.jp/wp-content/themes/tokyo-bay/bay/…modernizr.js?ver=2.6.1
http://ajax.googleapis.com/ajax/libs/scriptaculous…ptaculous.js?ver=1.9.0
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/builder.js
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/effects.js
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/dragdrop.js
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/controls.js
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/slider.js
http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/sound.js
http://ajax.googleapis.com/ajax/libs/scriptaculous…0/effects.js?ver=1.9.0
http://ajax.googleapis.com/ajax/libs/scriptaculous…0/builder.js?ver=1.9.0
http://www.iee.jp/wp-content/plugins/lightbox-2-wo…js/lightbox.js?ver=3.8
Optimize CSS Delivery of the following:
http://www.iee.jp/wp-content/plugins/contact-form-…s/styles.css?ver=3.7.2
http://www.iee.jp/wp-content/plugins/easingsliderp…show.min.css?ver=2.0.3
http://www.iee.jp/wp-content/plugins/post-list-gen…enerator.css?ver=1.2.4
http://www.iee.jp/wp-content/plugins/whats-new-gen…/whats-new.css?ver=3.8
http://www.iee.jp/wp-content/plugins/wp-visual-ico…s/wpvi-fa4.css?ver=3.8
http://www.iee.jp/wp-content/plugins/tablepress/css/default.min.css?ver=1.3
http://www.iee.jp/wp-content/plugins/multisite-glo…arch/style.css?ver=3.8
http://www.iee.jp/wp-content/plugins/lightbox-2-wo…htbox/css/lightbox.css
http://www.iee.jp/wp-content/plugins/count-per-day/counter.css
priority - 6 Reduce server response time
In our test, your server responded in 0.79 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 5 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 51KiB (14% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2014/04/head-400x100-b.png could save 5.3KiB (22% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2013/06/251.png could save 4KiB (31% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2013/06/252.png could save 3.5KiB (30% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2013/10/jhp.png could save 3.3KiB (25% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2015/09/icee2015_1-960x290.jpg could save 3.1KiB (3% reduction).
Losslessly compressing http://www.cgc.co.jp/iee_bnr/ohmsha.gif could save 1.7KiB (20% reduction).
Losslessly compressing https://www.jstage.jst.go.jp/pub/ieejjournal/thumb…ieejjournal_135_10.jpg could save 1.1KiB (11% reduction).
Losslessly compressing http://www.cgc.co.jp/iee_bnr/toshiba.jpg could save 916B (6% reduction).
Losslessly compressing http://www.cgc.co.jp/iee_bnr/hitachi.jpg could save 911B (10% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/honbu/img/wecc2015.gif could save 878B (14% reduction).
Losslessly compressing http://www.iee.jp/wp-content/plugins/easingsliderp…show_icon_inactive.png could save 862B (73% reduction).
Losslessly compressing http://www.iee.jp/wp-content/uploads/2014/01/BN-250x40_4.png could save 577B (15% reduction).
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 19.1KiB (23% reduction).
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/controls.js could save 2.8KiB (32% reduction) after compression.
Minifying http://www.iee.jp/wp-content/plugins/lightbox-2-wo…js/lightbox.js?ver=3.8 could save 2.4KiB (50% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/effects.js could save 1.8KiB (21% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous…0/effects.js?ver=1.9.0 could save 1.8KiB (21% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/dragdrop.js could save 1.7KiB (23% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous…ptaculous.js?ver=1.9.0 could save 864B (57% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/slider.js could save 673B (26% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous/1.9.0/builder.js could save 580B (32% reduction) after compression.
Minifying http://ajax.googleapis.com/ajax/libs/scriptaculous…0/builder.js?ver=1.9.0 could save 580B (32% reduction) after compression.
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 2.4KiB (18% reduction).
Minifying http://www.iee.jp/wp-content/plugins/wp-visual-ico…s/wpvi-fa4.css?ver=3.8 could save 708B (16% reduction) after compression.
Minifying http://www.iee.jp/wp-content/plugins/easingsliderp…show.min.css?ver=2.0.3 could save 592B (30% 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 847B (8% reduction).
iee.jp Desktop Resources
Total Resources | 59 |
Number of Hosts | 7 |
Static Resources | 36 |
JavaScript Resources | 20 |
CSS Resources | 11 |
iee.jp Desktop Resource Breakdown
iee.jp mobile page speed rank
Last tested: 2019-08-16
iee.jp Mobile Speed Test Quick Summary
priority - 81 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 788KiB (67% reduction).
Compressing and resizing https://www.iee.jp/wp/wp-content/uploads/sites/2/2019/04/ataikai_2019r.jpg could save 121.2KiB (96% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/2019/02/ishizue12-1.jpg could save 116.4KiB (54% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/sites/3/2019/04/Btaikai2019r.jpg could save 84.3KiB (51% reduction).
Compressing and resizing https://www.iee.jp/wp/wp-content/uploads/sites/3/2…02/bsymp20190319-2.jpg could save 82.5KiB (96% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/sites/4/2019/04/2019ctaikai.jpg could save 76.2KiB (51% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/sites/9/2…0327-kengaku-tokyo.jpg could save 58.2KiB (54% reduction).
Compressing http://digitalkiss.jp/test/iee/images/tokotakaoka_banner.png could save 21.4KiB (81% reduction).
Compressing http://digitalkiss.jp/test/iee/images/meidensha_banner.png could save 21.1KiB (82% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/2019/08/profnakagawa.jpg could save 11.9KiB (43% reduction).
Compressing https://www.iee.jp/assets/images/common/no-image.jpg could save 9.5KiB (60% reduction).
Compressing https://www.iee.jp/wp/wp-content/uploads/2019/06/maintain.jpg could save 7.8KiB (27% reduction).
Compressing http://digitalkiss.jp/test/iee/images/01_hitachi.jpg could save 4.9KiB (50% reduction).
Compressing https://www.iee.jp/assets/images/common/logo.png could save 2KiB (29% reduction).
Compressing https://www.iee.jp/assets/images/index/icon05.png could save 1.4KiB (19% reduction).
Compressing https://www.iee.jp/assets/images/common/icon-youtube.png could save 926B (22% reduction).
Compressing https://www.iee.jp/assets/images/index/icon01.png could save 310B (11% reduction).
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 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:
https://fonts.googleapis.com/css?family=Roboto
https://www.iee.jp/assets/css/style.css
https://fonts.googleapis.com/earlyaccess/notosansjapanese.css
https://www.iee.jp/wp/wp-includes/css/dist/block-l…tyle.min.css?ver=5.0.3
https://www.iee.jp/wp/wp-content/plugins/contact-f…s/styles.css?ver=5.1.3
https://www.iee.jp/wp/wp-content/plugins/jetpack/css/jetpack.css?ver=7.1.1
priority - 26 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://www.iee.jp/
https://www.iee.jp/
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://digitalkiss.jp/test/iee/images/06_interface.gif (expiration not specified)
http://digitalkiss.jp/test/iee/images/meidensha_banner.png (expiration not specified)
http://digitalkiss.jp/test/iee/images/tokotakaoka_banner.png (expiration not specified)
https://www.iee.jp/assets/css/print.css (expiration not specified)
https://www.iee.jp/assets/css/style.css (expiration not specified)
https://www.iee.jp/assets/images/common/icon-info.png (expiration not specified)
https://www.iee.jp/assets/images/common/icon-youtube.png (expiration not specified)
https://www.iee.jp/assets/images/common/logo.png (expiration not specified)
https://www.iee.jp/assets/images/common/no-image.jpg (expiration not specified)
https://www.iee.jp/assets/images/index/icon01.png (expiration not specified)
https://www.iee.jp/assets/images/index/icon02.png (expiration not specified)
https://www.iee.jp/assets/images/index/icon03.png (expiration not specified)
https://www.iee.jp/assets/images/index/icon04.png (expiration not specified)
https://www.iee.jp/assets/images/index/icon05.png (expiration not specified)
https://www.iee.jp/assets/images/index/icon06.png (expiration not specified)
https://www.iee.jp/assets/js/app.js (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/02/b…20190319-2-768x232.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/02/ishizue12-1.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/06/b-logo-768x232.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/06/maintain.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/08/2020-u-21-709x1024.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/2019/08/profnakagawa.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/2/2019/04/ataikai_2019r.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/3/2…02/bsymp20190319-2.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/3/2019/04/Btaikai2019r.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/4/2019/04/2019ctaikai.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/6/2019/01/Esymp2019.jpg (expiration not specified)
https://www.iee.jp/wp/wp-content/uploads/sites/9/2…0327-kengaku-tokyo.jpg (expiration not specified)
https://www.google.com/recaptcha/api.js?render=6Ld…Beiun2f2drnXSM&ver=3.0 (5 minutes)
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=v1563777128698 (5 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 20 Reduce server response time
In our test, your server responded in 0.54 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
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 2KiB (14% reduction).
iee.jp Mobile Resources
Total Resources | 60 |
Number of Hosts | 11 |
Static Resources | 41 |
JavaScript Resources | 11 |
CSS Resources | 9 |
iee.jp Mobile Resource Breakdown
iee.jp mobile page usability
Last tested: 2019-08-16
iee.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.
<input id="s" type="text" name="s">
is close to 1 other tap targets.The tap target
<input type="submit">
is close to 1 other tap targets.<p class="p-navi__group__contens__title">電気学会のご紹介</p>
and 3 others are close to other tap targets.<a class="p-navi__menu__…s js-navi-menu">メニュー</a>
is close to 1 other tap targets.<a href="https://www.iee.jp/" class="p-navi__menu__items">ホーム</a>
and 3 others are close to other tap targets.<a href="blog/post/secretariat/" class="p-top-info__more__button">お知らせ一覧</a>
is close to 1 other tap targets.<a href="event/list/" class="p-top-info__more__button">イベント一覧</a>
is close to 2 other tap targets.<li class="is-current">本部</li>
is close to 1 other tap targets.<li>プレス</li>
and 6 others are close to other tap targets.<a href="https://www.go…icies/privacy/">Privacy</a>
is close to 1 other tap targets.iee.jp similar domains
www.iee.net
www.iee.org
www.iee.info
www.iee.biz
www.iee.us
www.iee.mobi
www.ee.jp
www.iee.jp
www.uee.jp
www.iuee.jp
www.uiee.jp
www.jee.jp
www.ijee.jp
www.jiee.jp
www.kee.jp
www.ikee.jp
www.kiee.jp
www.oee.jp
www.ioee.jp
www.oiee.jp
www.ie.jp
www.iwe.jp
www.iewe.jp
www.iwee.jp
www.ise.jp
www.iese.jp
www.isee.jp
www.ide.jp
www.iede.jp
www.idee.jp
www.ire.jp
www.iere.jp
www.iree.jp
www.iew.jp
www.ieew.jp
www.ies.jp
www.iees.jp
www.ied.jp
www.ieed.jp
www.ier.jp
www.ieer.jp
iee.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.
iee.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.