Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | UMO | Search engines recommend title length of around 50-60 characters. The length of this title is 3. |
| Load time | 1.389 seconds on average | Website load speed is pretty fast. |
| Alexa global | 921 138, 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 24 links | This is a normal amount of links. |
| Page HTML size | 40.3KB | 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 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: Thu, 07 Sep 2017 18:36:22 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding X-Sorting-Hat-PodId: 3 X-Sorting-Hat-PodId-Cached: 1 X-Sorting-Hat-ShopId: 19545807 X-Sorting-Hat-Section: pod X-Sorting-Hat-ShopId-Cached: 1 Vary: Accept-Encoding X-ShopId: 19545807 X-ShardId: 3 Content-Language: en Strict-Transport-Security: max-age=7776000 ETag: cacheable:fa3e6ece0415bf0b711a6e7eda63d908 X-Alternate-Cache-Key: cacheable:daece26198855d4fc6815dd306e36062 X-Cache: hit, server Set-Cookie: secure_customer_sig=; path=/; expires=Mon, 07 Sep 2037 18:36:22 -0000; secure; HttpOnly X-Request-Id: ff961d06-79d1-4b14-81b3-684ca4e72f63 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=ff961d06-79d1-4b14-81b3-684ca4e72f63 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=ff961d06-79d1-4b14-81b3-684ca4e72f63 P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR" X-Dc: ash Set-Cookie: _landing_page=%2F; Expires=Thu, 21-Sep-17 18:36:22 GMT; Path=/; HttpOnly Set-Cookie: _orig_referrer=; Expires=Thu, 21-Sep-17 18:36:22 GMT; Path=/; HttpOnly Set-Cookie: cart_sig=; path=/; expires=Thu, 21 Sep 2017 18:36:22 -0000; HttpOnly X-Content-Type-Options: nosniff |
| WHOIS information |
|---|
No whois server is known for this kind of object. |
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 1728 mistypes, associated with umo.style:
If you are curious about what TLD extensions could also match the domain name of umo.style 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: