Perhaps the most relevant statistics data that we could gather is presented here:
| Data type/Website parameter | Status or value | Our findings |
|---|---|---|
| Site title (meta) | Find my Tokyo. | 東京メトロ | Sticking to between 50-60 characters for meta title length is a good idea. The length of this website's meta title is 22. |
| Website meta description | 東京メトロの広告キャンペーン「Find my Tokyo.」についてご紹介しています | The length of the meta description is 42 characters. Google recommends up to around 280-320 characters at the most. |
| Metadata keywords | 東京メトロ,営団地下鉄,東京地下鉄,metro,tokyo,石原さとみ,Find my Tokyo,CM,動画,ポスター,findmytokyo | Oh. It's unexpected, to put it mildly, to see meta keywords still being used. After all, they are no longer a ranking factor and associate with spam more than anything else. |
| Website load speed | Approximately 2.9075 seconds | It takes too long to load the website – we would suggest the webmaster to look into it. |
| Rank by Alexa | 342,555 | We are not fans of the Alexa rank, but if we base our assumptions on it, the website is not that popular. |
| Size of page HTML | 3.5KB | If it were up to us, we'd urge the webmaster to improve. The result isn't very good, you see. Just saying. |
| Server data | Server seems to be online. IP adress for this domain is 115.30.21.26. | Due to lack of data, we can't provide a meaningful insight. |
The basic overview not enough? Let's dive deeper.
Alexa, perhaps the oldest ranking system of its sort, bases it's website rating on approximated number of visitors of a specific page. In other words, the more visitors, the higher the global and local ranks. As of recently, Alexa has well over four million websites ranked. Having said all that, Alexa rank should be taken with a grain of salt. Or a massive bucketload. In other words, we think it to be greatly overrated, as it never takes into account how popular a website is within its niche.
What is a server? It's basically a physical storage device (one that, sometimes, makes up several virtual servers for the cheaper shared hosting) that holds all the files and databases associated with a specific website or websites. Obviously, it's a touch more complicated than that (servers also have processors), but the essence is quite simple - your browser contacts the server, which then sends all the neccessary information and files to your computer. Each physical server has a unique IP address assigned to it, too, for easy recognition.
If you need more raw data, here's what we managed to gather:
| Header information |
|---|
HTTP/1.1 200 OK Date: Tue, 06 Jun 2017 17:38:17 GMT Server: Apache Set-Cookie: PHPSESSID=0ifspo2usc3181qu46c75sd6s0; path=/ 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://findmy.tokyo/wp-json/>; rel="https://api.w.org/" Content-Length: 3496 Connection: close Content-Type: text/html; charset=UTF-8 |
| WHOIS entry |
|---|
No whois server is known for this kind of object. |
Typos are not uncommon, not even with website addresses. More than that, the more popular the website, the more typos there tend to happen. We have gathered and generated the following list of most frequently encountered mistypes for findmy.tokyo:
Here is a list of some more reports for you to check. If you found this one on findmy.tokyo useful, the following list will be of interest to you, too:
This list contains 370 top level domain variantions for findmy.tokyo domain name: