Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | StoCare | Search engines recommend title length of around 50-60 characters. The length of this title is 7. |
| Load time | 1.0423 seconds on average | Website load speed is pretty fast. |
| Alexa global | 799 484, as last updated | According to Alexa, the website's popularity is not exactly high. Take this rank with a healthy pinch of salt. |
| Page HTML size | 1.4KB | 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 172.104.91.153. | 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: Fri, 06 Oct 2017 16:48:53 GMT Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.0.23 X-Powered-By: PHP/7.0.23 Cache-Control: no-cache, private Set-Cookie: XSRF-TOKEN=eyJpdiI6IlVHXC9ENWxqdTBPakJ4UzBYTmtuWVBBPT0iLCJ2YWx1ZSI6Im8zbUtLRThyYithdHkzTkFMZHNVQ3FOMFU2ckhJTWxDRTE2aUFVRWh0cUtsUFRJUHQxVkRTWUxoZ1BodGtXV3NhZ2h4c3JQT2ExWmwxZGM3R0VxbGdnPT0iLCJtYWMiOiJhZTYxMmRkYzdiMjQ4YmM0ZDEyMjRhNGNiNzVmYzE3MTgyNDIyZjEzOTg0NTg0ODNjY2Q2OTJlZTgyNjE0NjA3In0%3D; expires=Fri, 06-Oct-2017 18:48:53 GMT; Max-Age=7200; path=/ Set-Cookie: laravel_session=eyJpdiI6ImwzQkV0ZCtJNllVZmtJVGJyWkFkXC9RPT0iLCJ2YWx1ZSI6InBMQkg3d0t4REFFakU3Vyt1cmNrWVAxcnhJdEFTM1RneFNxdXlGN3BtVm9cL0ZcL0xrOUJVZk41NjI1a2FVXC9hMWJGZmtJaGVKblBCXC83ZWVVaU90OGpzdz09IiwibWFjIjoiZDQ5MjM0NjRhNTcyYTMyMThiNzk2NzEyYTU4M2Y3ZTJlYTc3YTI5YjIwMTU0OWJiMmQyMTNjMDBlNjM0NDUyMCJ9; expires=Fri, 06-Oct-2017 18:48:53 GMT; Max-Age=7200; path=/; HttpOnly Content-Length: 1386 Content-Type: text/html; charset=UTF-8 |
| 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: [Domain Name] STOCARE.JP [Registrant] LANEX Corporation [Name Server] 01.dnsv.jp [Name Server] 02.dnsv.jp [Name Server] 03.dnsv.jp [Name Server] 04.dnsv.jp [Signing Key] [Created on] 2017/08/23 [Expires on] 2018/08/31 [Status] Active [Last Updated] 2017/09/26 13:25:40 (JST) Contact Information: [Name] Whois Privacy Protection Service by onamae.com [Email] [Web Page] [Postal code] 150-8512 [Postal Address] Shibuya-ku 26-1 Sakuragaoka-cho Cerulean Tower 11F [Phone] +81.354562560 [Fax] |
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 1788 mistypes, associated with stocare.jp:
If you are curious about what TLD extensions could also match the domain name of stocare.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: