Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Yahoo!ロコ - グルメ話題度ランキングとお出かけ情報サイト | Search engines recommend title length of around 50-60 characters. The length of this title is 32. |
| Meta description | Yahoo!ロコは、毎日更新されるグルメ話題度ランキングや、グルメ、ショッピング、レジャー施設、イベント情報などの写真、口コミ、クーポンなどが検索できる日本最大級の地域情報サイトです。 | 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 92 characters. |
| Keywords | ロコ,ヤフーロコ,Yahoo!ロコ | 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 | 3.9417 seconds on average | Load speed is a concern and should be improved if and when possible. |
| Total links on homepage | We found 830 links | Honestly, this is a strange amount of links for a homepage. |
| Page HTML size | 232.1KB | 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 182.22.25.252. | 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, 23 Oct 2017 11:33:50 GMT P3P: policyref="http://privacy.yahoo.co.jp/w3c/p3p_jp.xml", CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE GOV" X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block X-Frame-Options: SAMEORIGIN Set-Cookie: B=d38thmpcurksu&b=3&s=ac; expires=Thu, 24-Oct-2019 11:33:51 GMT; path=/; domain=.yahoo.co.jp Vary: Accept-Encoding Cache-Control: private Content-Type: text/html; charset=UTF-8 Age: 2 Transfer-Encoding: chunked Connection: keep-alive Via: http/1.1 edge1427.img.bbt.yahoo.co.jp (ApacheTrafficServer [c sSf ]) Server: ATS |
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 1035 mistypes, associated with loco.yahoo.co.jp:
If you are curious about what TLD extensions could also match the domain name of loco.yahoo.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: