Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | カフェサンチェ(Cafe Sanche) 自家製カステラが人気の津市のカフェ | Search engines recommend title length of around 50-60 characters. The length of this title is 38. |
Meta description | 三重県津市のカフェサンチェ(Cafe Sanche)のページです。地元の素材を使ったフードメニューや自家製のカステラが人気 | 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 61 characters. |
Keywords | カフェ,cafe,サンチェ,sanche,カステラ,ロールケーキ,ランチ,三重県,津市,長岡町,緑の街,地産地消,あやひかり,たまご,百花蜜,南蛮釜,自家製,無添加,ギフト,贈答,プレゼント,お土産,自家製,手作り,通信販売,お取り寄せ | We did not expect meta keywords to be used. It's a worrying sign more than anything, really, as websites with meta keywords often tend to be spammy. |
Load time | 1.972 seconds on average | Load speed is a concern and should be improved if and when possible. |
Total links on homepage | We found 2 links | Honestly, this is a strange amount of links for a homepage. |
Page HTML size | 2.9KB | 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 52.68.51.131. | 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.
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 Server: nginx Date: Mon, 06 Nov 2017 18:58:54 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Status: 200 OK X-UA-Compatible: IE=Edge,chrome=1 ETag: "7bdf465e3edb9801374acf8fbea9d925" Cache-Control: max-age=0, private, must-revalidate Set-Cookie: _sanche_session=BAh7B0kiD3Nlc3Npb25faWQGOgZFRkkiJTYzMjYxZDhiZDEzOWU4NWQwYTM1YzcyNzY2MzVjNWM0BjsAVEkiEF9jc3JmX3Rva2VuBjsARkkiMTJlUFZiRFErRmdEOWtVZWZ4NVBURG5ETjJjRlFqS2s3WFdsbUx6bnJwMUU9BjsARg%3D%3D--d55d0341e23aa95cfe0d9785f360fabdc15f2a1e; path=/; HttpOnly X-Request-Id: 7ffb878733b5a6943deb038b5919cf99 X-Runtime: 0.005022 X-Rack-Cache: miss Strict-Transport-Security: max-age=15768000 |
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 1703 mistypes, associated with sanche.jp:
If you are curious about what TLD extensions could also match the domain name of sanche.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: