Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | Love Tokyo | PHPを中心に | Search engines recommend title length of around 50-60 characters. The length of this title is 20. |
Load time | 1.6762 seconds on average | Load speed is a concern and should be improved if and when possible. |
Total links on homepage | We found 165 links | This is a normal amount of links. |
Page HTML size | 42.3KB | How do we put this... improvement is quite necessary. Load speed is a very important factor in so many ways! |
Website server | Server appears to be online. The IP address for the server is 104.28.24.126. | We are happy to say that the hosting service is provided by a respected company. Physically, the server is located in San Francisco, California, United States. |
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: Sat, 18 Jun 2016 13:04:01 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Set-Cookie: __cfduid=d9b77883aa381e159afa07614fd902c511466255040; expires=Sun, 18-Jun-17 13:04:00 GMT; path=/; domain=.kashioka.net; HttpOnly X-Powered-By: W3 Total Cache/0.9.4.1 Set-Cookie: PHPSESSID=o1s322lus76vc8p9fcdd6acm56; path=/; HttpOnly Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Link: <http://kashioka.net/wp-json/>; rel="https://api.w.org/" Vary: Accept-Encoding,User-Agent Server: cloudflare-nginx CF-RAY: 2b4ef1d192d12270-LAX |
WHOIS information |
---|
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % % Error: Invalid query |
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 1770 mistypes, associated with kashioka.net:
If you are curious about what TLD extensions could also match the domain name of kashioka.net 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: