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 40. |
Meta description | 阪神エリアのお葬式・法要、直葬・福祉葬から家族葬・一般葬までなら「葬儀センター 香琳社」にお任せください。西宮をはじめ、神戸・尼崎・伊丹・宝塚・川西・芦屋、池田・箕面・豊中など、幅広く対応いたします。 | 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 100 characters. |
Keywords | 葬儀,葬式,家族葬,直葬,福祉葬,一般葬,葬祭,西宮,芦屋,宝塚,伊丹,神戸,尼崎,香琳社 | 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 | 2.3975 seconds on average | Load speed is a concern and should be improved if and when possible. |
Total links on homepage | We found 73 links | This is a normal amount of links. |
Page HTML size | 41.8KB | 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 153.122.49.41. | 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: Fri, 15 Dec 2017 18:18:41 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive 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://kourinsya.jp/wp-json/>; rel="https://api.w.org/", <http://kourinsya.jp/>; rel=shortlink Set-Cookie: PHPSESSID=i1nfmn615aqbm3mogod3m82iu6; path=/ X-Powered-By: PleskLin |
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 1719 mistypes, associated with kourinsya.jp:
If you are curious about what TLD extensions could also match the domain name of kourinsya.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: