Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Hayabusa | Search engines recommend title length of around 50-60 characters. The length of this title is 8. |
| Load time | 1.0258 seconds on average | Website load speed is pretty fast. |
| Alexa global | 510 535, 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 19 links | This is a normal amount of links. |
| Page HTML size | 13.8KB | 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 13.32.14.233. | 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 Content-Type: text/html; charset=UTF-8 Content-Length: 13107 Connection: keep-alive Accept-Ranges: bytes Cache-Control: public, max-age=0 Date: Sat, 24 Jun 2017 08:29:31 GMT ETag: W/"3333-15c430a1810" Last-Modified: Fri, 26 May 2017 04:35:54 GMT X-Backend-Used: hayabusa_local X-Cache-Hits: 0 X-Cache: RefreshHit from cloudfront Via: 1.1 3bf1d6027627c6373861f6923b311679.cloudfront.net (CloudFront) X-Amz-Cf-Id: 7hz-NptzSyuNwc7ILdc_ZQKmm9WCXzdqmun_bCPh88hnZvj_r-R7Ng== |
| WHOIS information |
|---|
Domain : hayabusa.io Status : Live Expiry : 2018-01-07 NS 1 : ns-699.awsdns-23.net NS 2 : ns-2034.awsdns-62.co.uk NS 3 : ns-1080.awsdns-07.org NS 4 : ns-370.awsdns-46.com Owner Name : midori saegusa Owner OrgName : CyberAgent, Inc. Owner Addr : Shinsen-chou Owner Addr : Shibuya-ku Owner Addr : Tokyo Owner Addr : JP Check for 'hayabusa.sh' --- http://www.nic.sh/go/whois/hayabusa.sh Check for 'hayabusa.ac' --- http://www.nic.ac/go/whois/hayabusa.ac |
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 1740 mistypes, associated with hayabusa.io:
If you are curious about what TLD extensions could also match the domain name of hayabusa.io 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: