yokogawa.com Website Information

Daily Unique Visits: 72,385

Daily Page Views: 434,310

Income Per Day: $869

Estimated Value: $625,680

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

yokogawa.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website yokogawa.com is using the following name servers:

zns001-0m9002.yokogawa.co.jp
zns001-0m9001.yokogawa.co.jp
zns001-kz9021.yokogawa.co.jp
zns001-0m9006.yokogawa.co.jp

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website yokogawa.com position in Alexa rank database was 15210 and the lowest rank position was 19876. Current position of yokogawa.com in Alexa rank database is 19814.

Desktop speed score of yokogawa.com (51/100) is better than the results of 24.87% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of yokogawa.com (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of yokogawa.com (35/100) is better than the results of 13.85% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

yokogawa.com 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.

yokogawa.com 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.

Domain Name: YOKOGAWA.COM
Registry Domain ID: 2150218_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.psi.jp
Registrar URL: http://www.psi.jp/
Updated Date: 2023-10-09T07:01:44Z
Creation Date: 1998-10-09T04:00:00Z
Registry Expiry Date: 2024-10-08T04:00:00Z
Registrar: PSI-Japan, Inc.
Registrar IANA ID: 78
Registrar Abuse Contact Email: support@psi-japan.co.jp
Registrar Abuse Contact Phone: +81.332346921
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ZNS001-0M9001.YOKOGAWA.CO.JP
Name Server: ZNS001-0M9002.YOKOGAWA.CO.JP
Name Server: ZNS001-0M9006.YOKOGAWA.CO.JP
Name Server: ZNS001-KZ9021.YOKOGAWA.CO.JP
Name Server: ZNS001-KZ9022.YOKOGAWA.CO.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-20T19:42:00Z

yokogawa.com server information

Servers Location

yokogawa.com desktop page speed rank

Last tested: 2016-11-22

Desktop Speed Bad

51/100

yokogawa.com Desktop Speed Test Quick Summary

priority - 61Optimize images

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

Optimize the following images to reduce their size by 596.9KiB (88% reduction).

Compressing http://web-material3.yokogawa.com/e86beeedd505030e…cd7038470728c01aa9.jpg could save 559.8KiB (93% reduction).
Compressing http://web-material3.yokogawa.com/f0995dc844fb3fd4…1ffdd43858cc907568.jpg could save 14.4KiB (31% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-3.png could save 3.9KiB (92% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-4.png could save 3.9KiB (91% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-5.png could save 3.9KiB (90% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-6.png could save 3.9KiB (89% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-1.png could save 3.4KiB (79% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-2.png could save 2.7KiB (53% reduction).
Compressing https://www.google.com/uds/css/small-logo.png could save 1.1KiB (72% reduction).

priority - 12Leverage 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://munchkin.marketo.net/munchkin-beta.js (expiration not specified)
http://web-material3.yokogawa.com/03cefa85bc9083ac…573fd1890dcaa3b11e.jpg (expiration not specified)
http://web-material3.yokogawa.com/2dac655af748b29b…a5ab16bd63b8b1c2d7.jpg (expiration not specified)
http://web-material3.yokogawa.com/32ffbfcb7cad62c7…3c188e95f8045f01bc.jpg (expiration not specified)
http://web-material3.yokogawa.com/33d4dabfadcdf6e3…e30aaf00efad884dda.jpg (expiration not specified)
http://web-material3.yokogawa.com/49eb3598e869e57f…4cb449953f0bc70f0e.jpg (expiration not specified)
http://web-material3.yokogawa.com/852604424f84c1d0…6249c4de9275f5b42c.jpg (expiration not specified)
http://web-material3.yokogawa.com/9558b14520e6afbf…5ca13d37544837e292.jpg (expiration not specified)
http://web-material3.yokogawa.com/ad59a8e21b81679e…dfa5ff146efa8ed96f.jpg (expiration not specified)
http://web-material3.yokogawa.com/b79cda337665e718…b6076ab2bbba785f49.jpg (expiration not specified)
http://web-material3.yokogawa.com/b7c7cd882b7b81c2…857abe748b459e096c.jpg (expiration not specified)
http://web-material3.yokogawa.com/d9b4ecf5b24e5a3e…2e359525dd289a4ec5.jpg (expiration not specified)
http://web-material3.yokogawa.com/e86beeedd505030e…cd7038470728c01aa9.jpg (expiration not specified)
http://web-material3.yokogawa.com/f0995dc844fb3fd4…1ffdd43858cc907568.jpg (expiration not specified)
http://cdn.optimizely.com/img/2522160138/49a05d87c…7286e6ee99c8515c73.png (114 seconds)
https://cdn.optimizely.com/js/2522160138.js (2.1 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-MJC3GV (15 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://js-agent.newrelic.com/nr-974.min.js (60 minutes)
http://script.crazyegg.com/pages/scripts/0051/9628.js?411051 (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://c.nakanohito.jp/b3/bi.js (3 hours)
http://www.yokogawa.com/g_common/img/icon_pdf.gif (3 hours)

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

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

Remove render-blocking JavaScript:

http://www.yokogawa.com/public/vendor/modernizr.js
https://cdn.optimizely.com/js/2522160138.js
http://munchkin.marketo.net/munchkin-beta.js
https://www.yokogawa.com/public/vendor/beaconize-v0.3.3-min.js
http://www.yokogawa.com/public/build/js/client/plugins-a74e1b0d69.js
http://www.yokogawa.com/public/build/js/client/global-309ba5f743.js
http://www.yokogawa.com/public/build/js/client/app-9e022a5f80.js
http://www.yokogawa.com/public/build/js/client/pages/home-9015116473.js

Optimize CSS Delivery of the following:

http://www.yokogawa.com/public/build/css/client/main-7c52ed2310.css
http://fonts.googleapis.com/earlyaccess/notosansjapanese.css

priority - 8Enable 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 73.8KiB (80% reduction).

Compressing http://www.yokogawa.com/ could save 73.8KiB (80% reduction).

priority - 5Reduce server response time

priority - 2Prioritize 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.

92.3KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 1% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

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

Minifying http://www.yokogawa.com/ could save 15KiB (17% reduction).

priority - 1Minify JavaScript

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

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

Minifying http://www.yokogawa.com/public/vendor/modernizr.js could save 10.2KiB (66% reduction) after compression.
Minifying https://www.yokogawa.com/public/vendor/beaconize-v0.3.3-min.js could save 1,013B (73% reduction) after compression.

priority - 0Minify 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 3.9KiB (40% reduction).

Minifying https://www.google.com/uds/api/search/1.0/0c3990ce…873c9b6/default+en.css could save 3.9KiB (40% reduction) after compression.

yokogawa.com Desktop Resource Breakdown

Total Resources	78
Number of Hosts	22
Static Resources	50
JavaScript Resources	23
CSS Resources	4

yokogawa.com mobile page speed rank

Last tested: 2016-11-22

Mobile Speed Bad

35/100

yokogawa.com Mobile Speed Test Quick Summary

priority - 115Enable 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 1.1MiB (89% reduction).

Compressing http://www.yokogawa.com/api/mobile-navigation/?region=1 could save 1MiB (90% reduction).
Compressing http://www.yokogawa.com/ could save 73.9KiB (80% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

http://www.yokogawa.com/public/build/css/client/main-7c52ed2310.css
http://fonts.googleapis.com/earlyaccess/notosansjapanese.css
https://www.google.com/uds/api/search/1.0/0c3990ce…873c9b6/default+en.css
https://www.google.com/cse/style/look/default.css

priority - 16Leverage 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://munchkin.marketo.net/munchkin-beta.js (expiration not specified)
http://web-material3.yokogawa.com/2dac655af748b29b…a5ab16bd63b8b1c2d7.jpg (expiration not specified)
http://web-material3.yokogawa.com/33d4dabfadcdf6e3…e30aaf00efad884dda.jpg (expiration not specified)
http://web-material3.yokogawa.com/49eb3598e869e57f…4cb449953f0bc70f0e.jpg (expiration not specified)
http://web-material3.yokogawa.com/852604424f84c1d0…6249c4de9275f5b42c.jpg (expiration not specified)
http://web-material3.yokogawa.com/9558b14520e6afbf…5ca13d37544837e292.jpg (expiration not specified)
http://web-material3.yokogawa.com/ad59a8e21b81679e…dfa5ff146efa8ed96f.jpg (expiration not specified)
http://web-material3.yokogawa.com/b79cda337665e718…b6076ab2bbba785f49.jpg (expiration not specified)
http://web-material3.yokogawa.com/b7c7cd882b7b81c2…857abe748b459e096c.jpg (expiration not specified)
http://web-material3.yokogawa.com/d9b4ecf5b24e5a3e…2e359525dd289a4ec5.jpg (expiration not specified)
http://cdn.optimizely.com/img/2522160138/49a05d87c…7286e6ee99c8515c73.png (2 minutes)
https://cdn.optimizely.com/js/2522160138.js (2.1 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-MJC3GV (15 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://script.crazyegg.com/pages/scripts/0051/9628.js?411051 (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://js-agent.newrelic.com/nr-998.min.js (60 minutes)
https://www.google.com/jsapi?autoload=%7B%22module…22%3A%22en%22%7D%5D%7D (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://c.nakanohito.jp/b3/bi.js (3 hours)
http://www.yokogawa.com/g_common/img/icon_pdf.gif (3 hours)

priority - 9Reduce server response time

priority - 8Prioritize 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.

92.5KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 3% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 2Optimize images

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

Optimize the following images to reduce their size by 22.8KiB (81% reduction).

Compressing http://www.yokogawa.com/public/img/brilliant-grid-3.png could save 3.9KiB (92% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-4.png could save 3.9KiB (91% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-5.png could save 3.9KiB (90% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-6.png could save 3.9KiB (89% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-1.png could save 3.4KiB (79% reduction).
Compressing http://www.yokogawa.com/public/img/brilliant-grid-2.png could save 2.7KiB (53% reduction).
Compressing https://www.google.com/uds/css/small-logo.png could save 1.1KiB (72% reduction).

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

Minifying http://www.yokogawa.com/ could save 15KiB (17% reduction).

priority - 1Minify JavaScript

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

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

priority - 0Minify 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 3.9KiB (40% reduction).

Minifying https://www.google.com/uds/api/search/1.0/0c3990ce…873c9b6/default+en.css could save 3.9KiB (40% reduction) after compression.

yokogawa.com Mobile Resource Breakdown

Total Resources	75
Number of Hosts	22
Static Resources	46
JavaScript Resources	24
CSS Resources	4

yokogawa.com mobile page usability

Last tested: 2016-11-22

Mobile Usability Good

99/100

yokogawa.com Mobile Usability Test Quick Summary

priority - 1Size 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 <button id="card-slider-prev" type="button" class="slider-arrow s…ev slick-arrow">Prev</button> and 3 others are close to other tap targets.
The tap target <li id="slick-slide10" class="slick-active">1</li> and 1 others are close to other tap targets.
The tap target <a href="http://www.yok…htm?nid=footer">Terms of Use</a> and 3 others are close to other tap targets.

yokogawa.com HTML validation

Errors

Attribute “ng-app” not allowed on element “html” at this point.

Line: 3 Column: 23 - 75
"...E 8]><!--> <html class="no-js gt-ie8" id="ng-app" ng-app="app"> <!--<..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 6 Column: 3 - 64
"...utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><scrip..."

Attribute “ng-controller” not allowed on element “body” at this point.

Line: 145 Column: 25 - 172
"... 8]><!--> <body class="gt-ie8 theme-ia is-homepage" ng-controller="BaseController as baseCtrl" ng-class="{ 'active-mobile-menu': baseCtrl.activeMobileMenu }"> <!--<..."

Attribute “ng-class” not allowed on element “body” at this point.

Line: 145 Column: 25 - 172
"... 8]><!--> <body class="gt-ie8 theme-ia is-homepage" ng-controller="BaseController as baseCtrl" ng-class="{ 'active-mobile-menu': baseCtrl.activeMobileMenu }"> <!--<..."

Attribute “ng-cloak” not allowed on element “ul” at this point.

Line: 154 Column: 2 - 14
"...e-menu"> <ul ng-cloak> <li..."

Bad element name “gcse:searchbox-only”: Code point “U+003A” is not allowed

Line: 157 Column: 10 - 52
"... <gcse:searchbox-only resultsUrl="/search/"></gcse..." Line: 209 Column: 21 - 63
"... <gcse:searchbox-only resultsUrl="/search/"></gcse..."

Attribute “ng-show” not allowed on element “li” at this point.

Line: 160 Column: 3 - 89
"... </li> <li class="left-arrow" ng-show="baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent"> <a..." Line: 164 Column: 3 - 87
"... </li> <li class="browse-all" ng-show="baseCtrl.fullNavList[baseCtrl.currentMenuItem].name"> <a..."

Attribute “ng-click” not allowed on element “a” at this point.

Line: 161 Column: 4 - 211
"...rent"> <a href="#" ng-click="baseCtrl.handleNavigationClick($event, baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent)" ng-show="baseCtrl.fullNavList[baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent].name">{{ bas..." Line: 162 Column: 4 - 211
"...}}</a> <a href="#" ng-click="baseCtrl.handleNavigationClick($event, baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent)" ng-hide="baseCtrl.fullNavList[baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent].name">Menu</..." Line: 168 Column: 4 - 126
"...nued"> <a href="#" ng-click="baseCtrl.handleNavigationClick($event, child)" ng-show="baseCtrl.fullNavList[child].children.length">{{ bas..." Line: 196 Column: 37 - 188
"...location"><a ng-class="{ 'active': baseCtrl.activeLocationMenu }" href="http://www.yokogawa.com/index.htm?mode=pc" ng-click="baseCtrl.toggleLocationMenu($event)"><span ..." Line: 211 Column: 6 - 86
"...div> <a href="#" class="hamburger" ng-click="baseCtrl.toggleMobileNavigation($event)"><i cla..." Line: 513 Column: 10 - 75
"... <li><a class="control" ng-click="baseCtrl.toggleLocationMenu($event)"><i cla..." Line: 516 Column: 68 - 119
"...rters' }"><a ng-click="rsc.changeTab($event, 'headquarters')">Region..." Line: 517 Column: 64 - 111
"...ation' }"><a ng-click="rsc.changeTab($event, 'location')">Choose..." Line: 634 Column: 7 - 82
"...iv> <a href="#" ng-click="rsc.changeTab($event, 'location')" class="link right">Can't ..." Line: 639 Column: 31 - 156
"...show-all"><a href="#" ng-class="{'active': rsc.activeLetter === '' && rsc.searchLocations === '' }" ng-click="rsc.resetFilters($event)">All</a..." Line: 643 Column: 98 - 172
"...eLetter}"><a href="#" ng-click="rsc.filterByLetter($event, letter)" ng-bind="letter"></a></..." Line: 1169 Column: 2 - 123
"... </div> <a href="#top" ng-click="baseCtrl.goToTop($event)" class="go-to-top" ng-class="{ 'is-visible': baseCtrl.goToTopVisible }"><div c..."

Attribute “ng-show” not allowed on element “a” at this point.

Attribute “ng-hide” not allowed on element “a” at this point.

Line: 162 Column: 4 - 211
"...}}</a> <a href="#" ng-click="baseCtrl.handleNavigationClick($event, baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent)" ng-hide="baseCtrl.fullNavList[baseCtrl.fullNavList[baseCtrl.currentMenuItem].parent].name">Menu</..." Line: 169 Column: 4 - 108
"...}}</a> <a ng-href="{{ baseCtrl.fullNavList[child].url }}" ng-hide="baseCtrl.fullNavList[child].children.length">{{ bas..."

Attribute “ng-href” not allowed on element “a” at this point.

Line: 165 Column: 4 - 73
"...name"> <a ng-href="{{ baseCtrl.fullNavList[baseCtrl.currentMenuItem].url }}">Browse..." Line: 169 Column: 4 - 108
"...}}</a> <a ng-href="{{ baseCtrl.fullNavList[child].url }}" ng-hide="baseCtrl.fullNavList[child].children.length">{{ bas..." Line: 657 Column: 45 - 123
"...ble-cell"><a class="link" ng-href="{{ location.wwl_url }}" ng-bind="location.contact_hq"></a></..."

Attribute “ng-repeat” not allowed on element “li” at this point.

Attribute “ng-class” not allowed on element “li” at this point.

Line: 167 Column: 3 - 246
"... </li> <li ng-repeat="child in baseCtrl.fullNavList[baseCtrl.currentMenuItem].children" ng-class="{ 'right-arrow': baseCtrl.fullNavList[child].children.length }" ng-if="!baseCtrl.fullNavList[child].hidden && !baseCtrl.fullNavList[child].discontinued"> <a..." Line: 215 Column: 10 - 257
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'industries' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/industries/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('industries')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 216 Column: 13 - 267
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'solutions' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/solutions/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('solutions')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 217 Column: 13 - 294
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'products-platforms' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/products-platforms/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('products-platforms')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 218 Column: 13 - 264
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'services' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/services/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('services')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 219 Column: 13 - 271
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'technical_library' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/library/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('technical_library')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 220 Column: 13 - 245
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'about' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/about/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('about')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 516 Column: 6 - 67
"...bs"> <li ng-class="{ 'active': rsc.activeTab === 'headquarters' }"><a ng-..." Line: 517 Column: 6 - 63
".../li> <li ng-class="{ 'active': rsc.activeTab === 'location' }"><a ng-..." Line: 643 Column: 9 - 97
"...> <li ng-repeat="letter in rsc.letters" ng-class="{'active': letter === rsc.activeLetter}"><a hre..."

Attribute “ng-if” not allowed on element “li” at this point.

Attribute “ng-class” not allowed on element “header” at this point.

Line: 181 Column: 3 - 113
"...ainer"> <header id="geoBanner" class="prompt-geolocate" ng-class="{ 'is-visible': baseCtrl.showGeoBanner() }" ng-cloak> <div..."

Attribute “ng-cloak” not allowed on element “header” at this point.

Line: 181 Column: 3 - 113
"...ainer"> <header id="geoBanner" class="prompt-geolocate" ng-class="{ 'is-visible': baseCtrl.showGeoBanner() }" ng-cloak> <div..."

Attribute “ng-click” not allowed on element “span” at this point.

Line: 183 Column: 3 - 66
"...ainer"> <span class="prompt-close" ng-click="baseCtrl.closeGeoBanner()"></span..."

Attribute “ng-class” not allowed on element “a” at this point.

Line: 196 Column: 37 - 188
"...location"><a ng-class="{ 'active': baseCtrl.activeLocationMenu }" href="http://www.yokogawa.com/index.htm?mode=pc" ng-click="baseCtrl.toggleLocationMenu($event)"><span ..." Line: 639 Column: 31 - 156
"...show-all"><a href="#" ng-class="{'active': rsc.activeLetter === '' && rsc.searchLocations === '' }" ng-click="rsc.resetFilters($event)">All</a..." Line: 1169 Column: 2 - 123
"... </div> <a href="#top" ng-click="baseCtrl.goToTop($event)" class="go-to-top" ng-class="{ 'is-visible': baseCtrl.goToTopVisible }"><div c..."

Attribute “ng-mouseover” not allowed on element “li” at this point.

Line: 215 Column: 10 - 257
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'industries' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/industries/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('industries')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 216 Column: 13 - 267
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'solutions' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/solutions/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('solutions')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 217 Column: 13 - 294
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'products-platforms' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/products-platforms/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('products-platforms')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 218 Column: 13 - 264
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'services' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/solutions/services/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('services')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 219 Column: 13 - 271
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'technical_library' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/library/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('technical_library')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..." Line: 220 Column: 13 - 245
"... <li ng-class="{ 'hover': baseCtrl.activeMenuItem === 'about' && baseCtrl.activeDesktopMenu, 'active': baseCtrl.isCurrent('/about/') }" ng-mouseover="baseCtrl.mouseEnterMenuItem('about')" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()"><a hre..."

Attribute “ng-mouseleave” not allowed on element “li” at this point.

Attribute “ng-class” not allowed on element “nav” at this point.

Line: 226 Column: 3 - 175
"... </div> <nav class="mega-menu" ng-class="{ 'active': baseCtrl.activeDesktopMenu }" ng-mouseleave="baseCtrl.mouseLeaveMenuItem()" ng-mouseover="baseCtrl.preventMenuClose()" ng-cloak> ..." Line: 507 Column: 4 - 92
"...</nav> <nav class="location-menu" ng-class="{ 'active': baseCtrl.activeLocationMenu }" ng-cloak> <div..."

Attribute “ng-mouseleave” not allowed on element “nav” at this point.

Attribute “ng-mouseover” not allowed on element “nav” at this point.

Attribute “ng-cloak” not allowed on element “nav” at this point.

Attribute “ng-show” not allowed on element “div” at this point.

Line: 228 Column: 7 - 62
"...r"> <div ng-show="baseCtrl.activeMenuItem === 'industries'"> <..." Line: 267 Column: 9 - 63
"...> <div ng-show="baseCtrl.activeMenuItem === 'solutions'"> <..." Line: 309 Column: 9 - 72
"...> <div ng-show="baseCtrl.activeMenuItem === 'products-platforms'"> <..." Line: 357 Column: 9 - 62
"...> <div ng-show="baseCtrl.activeMenuItem === 'services'"> <..." Line: 390 Column: 9 - 71
"...> <div ng-show="baseCtrl.activeMenuItem === 'technical_library'"> <..." Line: 474 Column: 9 - 59
"...> <div ng-show="baseCtrl.activeMenuItem === 'about'"> <..."

Attribute “columnize” not allowed on element “ul” at this point.

Line: 230 Column: 19 - 66
"... <ul class="mega-menu-list mod-33" columnize="3"> ..." Line: 269 Column: 19 - 66
"... <ul class="mega-menu-list mod-33" columnize="3"> ..." Line: 311 Column: 19 - 66
"... <ul class="mega-menu-list mod-33" columnize="3"> ..." Line: 359 Column: 19 - 66
"... <ul class="mega-menu-list mod-33" columnize="3"> ..." Line: 392 Column: 12 - 59
"... <ul class="mega-menu-list mod-33" columnize="3"> ..." Line: 396 Column: 5 - 63
"...per"> <ul class="mega-menu-list-child-list mod-50" columnize="2"> ..." Line: 427 Column: 5 - 57
"...per"> <ul class="mega-menu-list-child-list " columnize="1"> ..." Line: 452 Column: 5 - 57
"...per"> <ul class="mega-menu-list-child-list " columnize="1"> ..."

Attribute “ng-controller” not allowed on element “div” at this point.

Line: 510 Column: 4 - 56
"...umns"> <div ng-controller="RegionSelectorController as rsc"> <..."

Attribute “ng-class” not allowed on element “div” at this point.

Line: 520 Column: 6 - 88
"...ap"> <div class="parent-body" ng-class="{ 'active': rsc.activeTab === 'headquarters' }"> ..." Line: 636 Column: 6 - 84
"...div> <div class="parent-body" ng-class="{ 'active': rsc.activeTab === 'location' }"> ..." Line: 1170 Column: 2 - 175
"...div></a> <div class="overlay" ng-class="{ 'active': baseCtrl.activeDesktopMenu || baseCtrl.activeLocationMenu || baseCtrl.activeMobileMenu }" ng-click="baseCtrl.handleOverlayClick()"></div>..."

Attribute “ng-model” not allowed on element “input” at this point.

Line: 640 Column: 36 - 130
"...r-search"><input type="text" ng-model="rsc.searchLocations" placeholder="Enter your country/region name"></div>..."

Attribute “ng-bind” not allowed on element “a” at this point.

Line: 643 Column: 98 - 172
"...eLetter}"><a href="#" ng-click="rsc.filterByLetter($event, letter)" ng-bind="letter"></a></..." Line: 657 Column: 45 - 123
"...ble-cell"><a class="link" ng-href="{{ location.wwl_url }}" ng-bind="location.contact_hq"></a></..."

Attribute “ng-repeat” not allowed on element “div” at this point.

Line: 655 Column: 10 - 178
"... <div class="locations-table-row" ng-repeat="location in filteredLocations = (rsc.locations | filter:rsc.searchLocations | firstletter:rsc.activeLetter:'location_name')"> ..."

Attribute “ng-bind” not allowed on element “div” at this point.

Line: 656 Column: 11 - 77
"... <div class="locations-table-cell" ng-bind="location.location_name"></div>..."

Attribute “ng-if” not allowed on element “div” at this point.

Line: 659 Column: 10 - 76
"... <div class="locations-table-row" ng-if="!filteredLocations.length"> ..." Line: 810 Column: 9 - 125
"...> <div ng-if="baseCtrl.feeds.news_events_featured_url" ng-bind-html="baseCtrl.feeds.news_events_featured_url.response"></div>..." Line: 811 Column: 9 - 117
"...> <div ng-if="baseCtrl.feeds.news_events_more_url" ng-bind-html="baseCtrl.feeds.news_events_more_url.response"></div>..."

Duplicate ID “brilliant-grid-step-1”.

Line: 698 Column: 18 - 89
"... <div id="brilliant-grid-step-1" class="brilliant-grid brilliant-grid-1"></div>..." Line: 717 Column: 18 - 89
"... <div id="brilliant-grid-step-1" class="brilliant-grid brilliant-grid-1"></div>..."

Duplicate ID “brilliant-grid-step-2”.

Line: 699 Column: 10 - 81
"... <div id="brilliant-grid-step-2" class="brilliant-grid brilliant-grid-2"></div>..." Line: 718 Column: 10 - 81
"... <div id="brilliant-grid-step-2" class="brilliant-grid brilliant-grid-2"></div>..."

Duplicate ID “brilliant-grid-step-3”.

Line: 700 Column: 10 - 81
"... <div id="brilliant-grid-step-3" class="brilliant-grid brilliant-grid-3"></div>..." Line: 719 Column: 10 - 81
"... <div id="brilliant-grid-step-3" class="brilliant-grid brilliant-grid-3"></div>..."

Duplicate ID “brilliant-grid-step-4”.

Line: 701 Column: 10 - 81
"... <div id="brilliant-grid-step-4" class="brilliant-grid brilliant-grid-4"></div>..." Line: 720 Column: 10 - 81
"... <div id="brilliant-grid-step-4" class="brilliant-grid brilliant-grid-4"></div>..."

Duplicate ID “brilliant-grid-step-5”.

Line: 702 Column: 10 - 81
"... <div id="brilliant-grid-step-5" class="brilliant-grid brilliant-grid-5"></div>..." Line: 721 Column: 10 - 81
"... <div id="brilliant-grid-step-5" class="brilliant-grid brilliant-grid-5"></div>..."

Duplicate ID “brilliant-grid-step-6”.

Line: 703 Column: 10 - 81
"... <div id="brilliant-grid-step-6" class="brilliant-grid brilliant-grid-6"></div>..." Line: 722 Column: 10 - 81
"... <div id="brilliant-grid-step-6" class="brilliant-grid brilliant-grid-6"></div>..."

Attribute “ng-bind-html” not allowed on element “div” at this point.

Line: 810 Column: 9 - 125
"...> <div ng-if="baseCtrl.feeds.news_events_featured_url" ng-bind-html="baseCtrl.feeds.news_events_featured_url.response"></div>..." Line: 811 Column: 9 - 117
"...> <div ng-if="baseCtrl.feeds.news_events_more_url" ng-bind-html="baseCtrl.feeds.news_events_more_url.response"></div>..."

Attribute “ng-click” not allowed on element “div” at this point.

Line: 1170 Column: 2 - 175
"...div></a> <div class="overlay" ng-class="{ 'active': baseCtrl.activeDesktopMenu || baseCtrl.activeLocationMenu || baseCtrl.activeMobileMenu }" ng-click="baseCtrl.handleOverlayClick()"></div>..."

The “aria-labelledby” attribute must point to an element in the same document.

Line: 1173 Column: 3 - 132
"...> <div id="geo-modal" class="reveal-modal medium" data-reveal aria-labelledby="redirectModalTitle" aria-hidden="true" role="dialog"> <d..."

Warnings

Element name “gcse:searchbox-only” cannot be represented as XML 1.0.

Line: 157 Column: 10 - 52
"... <gcse:searchbox-only resultsUrl="/search/"></gcse..." Line: 209 Column: 21 - 63
"... <gcse:searchbox-only resultsUrl="/search/"></gcse..."

The first occurrence of ID “brilliant-grid-step-1” was here.

Line: 679 Column: 18 - 89
"... <div id="brilliant-grid-step-1" class="brilliant-grid brilliant-grid-1"></div>..." Line: 679 Column: 18 - 89
"... <div id="brilliant-grid-step-1" class="brilliant-grid brilliant-grid-1"></div>..."

The first occurrence of ID “brilliant-grid-step-2” was here.

Line: 680 Column: 10 - 81
"... <div id="brilliant-grid-step-2" class="brilliant-grid brilliant-grid-2"></div>..." Line: 680 Column: 10 - 81
"... <div id="brilliant-grid-step-2" class="brilliant-grid brilliant-grid-2"></div>..."

The first occurrence of ID “brilliant-grid-step-3” was here.

Line: 681 Column: 10 - 81
"... <div id="brilliant-grid-step-3" class="brilliant-grid brilliant-grid-3"></div>..." Line: 681 Column: 10 - 81
"... <div id="brilliant-grid-step-3" class="brilliant-grid brilliant-grid-3"></div>..."

The first occurrence of ID “brilliant-grid-step-4” was here.

Line: 682 Column: 10 - 81
"... <div id="brilliant-grid-step-4" class="brilliant-grid brilliant-grid-4"></div>..." Line: 682 Column: 10 - 81
"... <div id="brilliant-grid-step-4" class="brilliant-grid brilliant-grid-4"></div>..."

The first occurrence of ID “brilliant-grid-step-5” was here.

Line: 683 Column: 10 - 81
"... <div id="brilliant-grid-step-5" class="brilliant-grid brilliant-grid-5"></div>..." Line: 683 Column: 10 - 81
"... <div id="brilliant-grid-step-5" class="brilliant-grid brilliant-grid-5"></div>..."

The first occurrence of ID “brilliant-grid-step-6” was here.

Line: 684 Column: 10 - 81
"... <div id="brilliant-grid-step-6" class="brilliant-grid brilliant-grid-6"></div>..." Line: 684 Column: 10 - 81
"... <div id="brilliant-grid-step-6" class="brilliant-grid brilliant-grid-6"></div>..."

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

Line: 3 Column: 23 - 75
"...E 8]><!--> <html class="no-js gt-ie8" id="ng-app" ng-app="app"> <!--<..."

yokogawa.com similar domains

Similar domains:

www.yokogawa.com
www.yokogawa.net
www.yokogawa.org
www.yokogawa.info
www.yokogawa.biz
www.yokogawa.us
www.yokogawa.mobi
www.okogawa.com
www.yokogawa.com
www.tokogawa.com
www.ytokogawa.com
www.tyokogawa.com
www.gokogawa.com
www.ygokogawa.com
www.gyokogawa.com
www.hokogawa.com
www.yhokogawa.com
www.hyokogawa.com
www.uokogawa.com
www.yuokogawa.com
www.uyokogawa.com
www.ykogawa.com
www.yikogawa.com
www.yoikogawa.com
www.yiokogawa.com
www.ykkogawa.com
www.yokkogawa.com
www.ykokogawa.com
www.ylkogawa.com
www.yolkogawa.com
www.ylokogawa.com
www.ypkogawa.com
www.yopkogawa.com
www.ypokogawa.com
www.yoogawa.com
www.yojogawa.com
www.yokjogawa.com
www.yojkogawa.com
www.yoiogawa.com
www.yokiogawa.com
www.yomogawa.com
www.yokmogawa.com
www.yomkogawa.com
www.yologawa.com
www.yoklogawa.com
www.yooogawa.com
www.yokoogawa.com
www.yookogawa.com
www.yokgawa.com
www.yokigawa.com
www.yokoigawa.com
www.yokkgawa.com
www.yokokgawa.com
www.yoklgawa.com
www.yokolgawa.com
www.yokpgawa.com
www.yokopgawa.com
www.yokpogawa.com
www.yokoawa.com
www.yokofawa.com
www.yokogfawa.com
www.yokofgawa.com
www.yokovawa.com
www.yokogvawa.com
www.yokovgawa.com
www.yokotawa.com
www.yokogtawa.com
www.yokotgawa.com
www.yokobawa.com
www.yokogbawa.com
www.yokobgawa.com
www.yokoyawa.com
www.yokogyawa.com
www.yokoygawa.com
www.yokohawa.com
www.yokoghawa.com
www.yokohgawa.com
www.yokogwa.com
www.yokogqwa.com
www.yokogaqwa.com
www.yokogqawa.com
www.yokogwwa.com
www.yokogawwa.com
www.yokogwawa.com
www.yokogswa.com
www.yokogaswa.com
www.yokogsawa.com
www.yokogzwa.com
www.yokogazwa.com
www.yokogzawa.com
www.yokogaa.com
www.yokogaqa.com
www.yokogawqa.com
www.yokogaaa.com
www.yokogawaa.com
www.yokogaawa.com
www.yokogasa.com
www.yokogawsa.com
www.yokogaea.com
www.yokogawea.com
www.yokogaewa.com
www.yokogaw.com
www.yokogawq.com
www.yokogawaq.com
www.yokogaww.com
www.yokogawaw.com
www.yokogaws.com
www.yokogawas.com
www.yokogawz.com
www.yokogawaz.com
www.yokogawza.com
www.yokogawa.con

yokogawa.com 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.

yokogawa.com 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.

YOKOGAWA.COM Yokogawa Electric Corporation

yokogawa.com Website Information

Advertisement

yokogawa.com Alexa Rank

yokogawa.com whois

yokogawa.com server information

Servers Location

yokogawa.com desktop page speed rank

yokogawa.com Desktop Speed Test Quick Summary

priority - 61Optimize images

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

Optimize the following images to reduce their size by 596.9KiB (88% reduction).

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

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 8Enable 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 73.8KiB (80% reduction).

priority - 5Reduce server response time

priority - 2Prioritize 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.

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

priority - 1Minify JavaScript

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

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

priority - 0Minify 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 3.9KiB (40% reduction).

yokogawa.com Desktop Resource Breakdown

yokogawa.com mobile page speed rank

yokogawa.com Mobile Speed Test Quick Summary

priority - 115Enable 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 1.1MiB (89% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

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

priority - 9Reduce server response time

priority - 8Prioritize 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.

priority - 2Optimize images

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

Optimize the following images to reduce their size by 22.8KiB (81% reduction).

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

priority - 1Minify JavaScript

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

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

priority - 0Minify 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 3.9KiB (40% reduction).

yokogawa.com Mobile Resource Breakdown

yokogawa.com mobile page usability

yokogawa.com Mobile Usability Test Quick Summary

priority - 1Size 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.

yokogawa.com HTML validation

Errors

Attribute “ng-app” not allowed on element “html” at this point.

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Attribute “ng-controller” not allowed on element “body” at this point.

Attribute “ng-class” not allowed on element “body” at this point.

Attribute “ng-cloak” not allowed on element “ul” at this point.

Bad element name “gcse:searchbox-only”: Code point “U+003A” is not allowed

Attribute “ng-show” not allowed on element “li” at this point.

Attribute “ng-click” not allowed on element “a” at this point.

Attribute “ng-show” not allowed on element “a” at this point.

Attribute “ng-hide” not allowed on element “a” at this point.