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 25. |
| Meta description | A description has not been provided for this site. | 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 50 characters. |
| Load time | 2.2938 seconds on average | Load speed is a concern and should be improved if and when possible. |
| Alexa global | 6 319 447, 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 57 links | This is a normal amount of links. |
| Number of backlinks | Around 7 | Backlinks is one of the key metrics for search engines. This website seems to have a very low number of backlinks, which means poorer rank in search results. |
| Page HTML size | 15.4KB | 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 157.7.188.228. | 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.
As we've mentioned before, traffic is not a key metric. However, the target audience does say a lot about what's been done to optimize the website, as well as what should be done going forwards. Let's see if we have any useful information here.
| Parameter name | Status | Comment |
|---|---|---|
| Related websites | okazaki-endo.com gion-endo.com kyoto-yoshikawa.co.jp tunahachi.co.jp |
These are the websites that fall into the same category as endo.kyoto, and so target the same audience and, likely, keywords. To a larger or smaller extent, all of them are competitors. |
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: Mon, 16 Oct 2017 03:22:59 GMT Server: Apache Last-Modified: Wed, 06 Sep 2017 22:39:44 GMT Accept-Ranges: bytes Content-Length: 15670 Vary: Accept-Encoding Content-Type: text/html |
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 1760 mistypes, associated with endo.kyoto:
If you are curious about what TLD extensions could also match the domain name of endo.kyoto 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: