Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | ハンコック日本サイト|乗用車、トラック、バス用の最高のタイヤ | Search engines recommend title length of around 50-60 characters. The length of this title is 30. |
Meta description | ようこそハンコックタイヤの日本 ウェブサイトへ。当社は、高品質な乗用車用タイヤ、トラック用タイヤ、バス用タイヤ、競技車用タイヤを専門に製造しています。 | To make sure all the meta description is visible in search results page, Google recommends length of up to 320 characters at the most. This description has exactly 75 characters. |
Load time | 1.4979 seconds on average | Website load speed is pretty fast. |
Alexa global | 997 468, as last updated | According to Alexa, the website's popularity is not exactly high. Take this rank with a healthy pinch of salt. |
Total links on homepage | We found 198 links | This is a normal amount of links. |
Page HTML size | 47.3KB | Load speed (and overall responsiveness) is such an important factor for both search engines and user experience, would you not agree? With that in mind, this is a very good result. |
Website server | Server appears to be online. The IP address for the server is 151.249.90.215. | It's unfortunate, but despite our best attempts, we failed to gather enough data to provide a meaningful insight at this time. |
What, all that information was not enough? You want... more? Right, then. You asked for it.
With over 4 million websites indexed (which can seem as a lot, or very little, depending on your point of view), Alexa is perhaps the oldest and certainly the best known ranking system, deservedly or not. The Alexa Global and Local ranks of a website are based on an approximate amount of visitors a given website receives. The more visitors, the higher the rank. The Alexa rank, be it Local or Global, should be taken with a pinch of salt. After all, visitor count is by far not the simple measure of a website's success it's made out to be. For example, a gardening website is never going to be as popular as a movie review website. It does not mean it's not popular within it's niche.
Similarly to how a hard drive or a modern SSD device holds your files, a server holds all the files the website needs to operate. To load a webpage, your browser needs to contact the said server and request files - strings of code that make up the website into what it is, including images, text and database entries. Each physical server has a unique IP address that is used by the browser to contact it.
Let's see what technical information we've managed to gather:
Header in detail |
---|
HTTP/1.1 200 OK Date: Wed, 28 Jun 2017 05:10:50 GMT Server: PWS/8.2.1.6.5 Transfer-Encoding: chunked X-Px: nc h0-s1072.p11-fra ( h0-s130.p59-icn), nc h0-s130.p59-icn ( origin) Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Type: text/html;charset=UTF-8 X-xss-protection: 1 X-content-type-options: nosniff X-content-type-options: nosniff Vary: Accept-Encoding Connection: keep-alive Set-Cookie: renderid=rend01; path=/; Set-Cookie: JSESSIONID=1rlyld1wd0j3uq8jbpkye08uj;Path=/ |
WHOIS information |
---|
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: a. [Domain Name] HANKOOKTIRE.CO.JP g. [Organization] HANKOOK TIRE JAPAN CORP. l. [Organization Type] Company m. [Administrative Contact] HK38664JP n. [Technical Contact] HM3100JP n. [Technical Contact] YH994JP n. [Technical Contact] HK38664JP p. [Name Server] ns1.dzndns.com p. [Name Server] ns2.dzndns.com p. [Name Server] ns3.dzndns.com p. [Name Server] ns4.dzndns.com s. [Signing Key] [State] Connected (2017/12/31) [Registered Date] 2000/12/21 [Connected Date] 2001/05/30 [Last Update] 2017/01/01 01:10:04 (JST) |
A good domain address is usually one that is easy to spell, resulting in the smallest amount of mistypes possible. Still, such a thing inevitably happens. Here is a list with the most frequent 1752 mistypes, associated with hankooktire.co.jp:
If you are curious about what TLD extensions could also match the domain name of hankooktire.co.jp well, we have prepared an extensive list for you to look through:
We are glad you have finished this report. Hopefully, you found what you were looking for. In case you need more information to compare, here is a list of some other detailed overviews we have prepared: