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 11. |
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 119 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 | 1.2737 seconds on average | Website load speed is pretty fast. |
Total links on homepage | We found 58 links | This is a normal amount of links. |
Page HTML size | 17.2KB | Load speed (and overall responsiveness) is such an important factor for both search engines and user experience, would you not agree? With that in mind, this is a very good result. |
Website server | Server appears to be online. The IP address for the server is 203.180.245.32. | 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 Date: Mon, 01 Jan 2018 13:47:12 GMT Server: Apache Last-Modified: Sun, 31 Dec 2017 15:01:18 GMT Expires: Thu, 19 Nov 1981 08:52:00 GMT X-FRAME-OPTIONS: SAMEORIGIN X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff Set-Cookie: acms_ssid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=jp Set-Cookie: acms_ssid=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=co.jp Set-Cookie: acms_ssid=dsncqe4hqpd11d63uc0tqlhlt4; expires=Mon, 08-Jan-2018 13:47:12 GMT; Max-Age=604800; path=/; domain=epron.co.jp; HttpOnly Cache-Control: no-store, no-cache, must-revalidate Pragma: no-cache Vary: Accept-Encoding,User-Agent Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 |
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 1320 mistypes, associated with epron.co.jp:
If you are curious about what TLD extensions could also match the domain name of epron.co.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: