Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | PASS | Search engines recommend title length of around 50-60 characters. The length of this title is 4. |
Load time | 1.3164 seconds on average | Website load speed is pretty fast. |
Alexa global | 803 707, 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 9 links | Honestly, this is a strange amount of links for a homepage. |
Page HTML size | 9.1KB | 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 104.25.99.38. | 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.
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: Thu, 25 Jan 2018 09:20:18 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Set-Cookie: __cfduid=dd06af75da0545f2ed36550f6685a9a871516872017; expires=Fri, 25-Jan-19 09:20:17 GMT; path=/; domain=.pass.co.jp; HttpOnly; Secure Cache-Control: max-age=0, private, must-revalidate Set-Cookie: _liquid_pay_session=Z3I0dG1wNmgyTUFLbGxhdUVVc2d1b1pJckE1R1Q5M3NrR1hsa0VWMnVTaHF4Y24xMjlCQnVsSVVGakdIUUZsNGRRd2dBOXc2Y0dBT1Z1bFhHa3RJL05TYjRsSFRNNVpZQ1hJdDFUNHJ1aG9hdjBGdCt5QWFrd0xjZjVpSlZ2NFVha1hWR1Y1WEN5U1hvQWtEdFdHV2VBPT0tLWlYNFk3YU05bHRTTWNIRXc4TXJqSGc9PQ%3D%3D--c5e43ce7d9caa40ea5b18673337065195ce8470c; path=/; HttpOnly Via: 1.1 spaces-router (5f8b4cab1432) X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-Request-Id: 4a771f80-4faf-4dbc-9444-7d14432ac91c X-Runtime: 0.054828 X-Xss-Protection: 1; mode=block Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" Server: cloudflare CF-RAY: 3e2a27de8bde9aca-FRA |
WHOIS information |
---|
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: a. [Domain Name] PASS.CO.JP g. [Organization] Liquidinc l. [Organization Type] corporation m. [Administrative Contact] YK50403JP n. [Technical Contact] YK50364JP p. [Name Server] candy.ns.cloudflare.com p. [Name Server] simon.ns.cloudflare.com s. [Signing Key] [State] Connected (2018/08/31) [Registered Date] 2017/08/08 [Connected Date] 2017/08/08 [Last Update] 2017/08/21 13:07:48 (JST) |
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 1215 mistypes, associated with pass.co.jp:
If you are curious about what TLD extensions could also match the domain name of pass.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: