Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Jzoom - 電動キックボード | Search engines recommend title length of around 50-60 characters. The length of this title is 16. |
| Meta description | Jzoomの世界最軽量電動キックボード、e-Twow。最高時速30kmのパワフル駆動、3秒で折りたたんでコンパクト。電動スクーターや電動自転車に代わる、環境に優しくて快適な新しい移動手段。 | 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 94 characters. |
| Load time | 2.115 seconds on average | Load speed is a concern and should be improved if and when possible. |
| Alexa global | 913 833, 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 75 links | This is a normal amount of links. |
| Page HTML size | 73.2KB | 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 23.227.38.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.
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 Server: nginx Date: Mon, 05 Jun 2017 00:43:33 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding X-Sorting-Hat-PodId: 0 X-Sorting-Hat-PodId-Cached: 0 X-Sorting-Hat-ShopId: 8201557 X-Sorting-Hat-Section: pod X-Sorting-Hat-ShopId-Cached: 0 Vary: Accept-Encoding X-Sorting-Hat-PodId: 0 X-Sorting-Hat-PodId-Cached: 0 X-Sorting-Hat-ShopId: 8201557 X-Sorting-Hat-Section: pod X-Sorting-Hat-ShopId-Cached: 0 Vary: Accept-Encoding X-ShopId: 8201557 X-ShardId: 0 Content-Language: en ETag: cacheable:bb2890cbadd54ec9a05b097955856a52 X-Alternate-Cache-Key: cacheable:bd966596ea7775231707823c4b62a86c X-Cache: miss Set-Cookie: secure_customer_sig=; path=/; expires=Fri, 05 Jun 2037 00:43:33 -0000; secure; HttpOnly Content-Security-Policy: upgrade-insecure-requests; report-uri /csp-report?source%5Baction%5D=index&source%5Bapp%5D=Shopify&source%5Bcontroller%5D=storefront_section%2Fshop&source%5Bsection%5D=storefront&source%5Buuid%5D=b0727feb-18f8-4a30-af2e-bab13ceb207c X-Content-Type-Options: nosniff X-Download-Options: noopen X-Permitted-Cross-Domain-Policies: none X-XSS-Protection: 1; mode=block; report=/xss-report?source%5Baction%5D=index&source%5Bapp%5D=Shopify&source%5Bcontroller%5D=storefront_section%2Fshop&source%5Bsection%5D=storefront&source%5Buuid%5D=b0727feb-18f8-4a30-af2e-bab13ceb207c P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR" X-Dc: ash,chi2 X-Content-Type-Options: nosniff X-Request-ID: b0727feb-18f8-4a30-af2e-bab13ceb207c Set-Cookie: _landing_page=%2F; Expires=Mon, 19-Jun-17 00:43:33 GMT; Path=/; HttpOnly Set-Cookie: _orig_referrer=; Expires=Mon, 19-Jun-17 00:43:33 GMT; Path=/; HttpOnly Set-Cookie: cart_sig=; path=/; expires=Mon, 19 Jun 2017 00:43:33 -0000; HttpOnly X-Content-Type-Options: nosniff |
| 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] JZOOM.JP [Registrant] JZoom [Name Server] 01.dnsv.jp [Name Server] 02.dnsv.jp [Name Server] 03.dnsv.jp [Name Server] 04.dnsv.jp [Signing Key] [Created on] 2015/04/04 [Expires on] 2018/04/30 [Status] Active [Last Updated] 2017/05/01 01:05:10 (JST) Contact Information: [Name] JZoom [Email] [Web Page] [Postal code] 108-0073 [Postal Address] Min Mita 1-6-3 #3305 [Phone] 08050673377 [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 1230 mistypes, associated with jzoom.jp:
If you are curious about what TLD extensions could also match the domain name of jzoom.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: