Perhaps the most relevant statistics data that we could gather is presented here:
Data type/Website parameter | Status or value | Our findings |
---|---|---|
Site title (meta) | OS/ON | Sticking to between 50-60 characters for meta title length is a good idea. The length of this website's meta title is 5. |
Website meta description | Loja online com curadoria focada em marcas novas. Também atendemos no showroom no Rio de Janeiro. Rua Lopes Quintas 147, Jardim Botânico. | The length of the meta description is 137 characters. Google recommends up to around 280-320 characters at the most. |
Website load speed | Approximately 1.4742 seconds | Website load speed is on a good level, great! But if an improvement can be made, it's always for the better. |
Rank by Alexa | 821,336 | We are not fans of the Alexa rank, but if we base our assumptions on it, the website is not that popular. |
Homepage links | Approximately 114 | A good amount of links and nothing to worry about. |
Size of page HTML | 40.8KB | This is a very good result, as search engines prioritize websites that are quick to load. |
Server data | Server seems to be online. IP adress for this domain is 23.227.38.32. | Due to lack of data, we can't provide a meaningful insight. |
The basic overview not enough? Let's dive deeper.
Alexa, perhaps the oldest ranking system of its sort, bases it's website rating on approximated number of visitors of a specific page. In other words, the more visitors, the higher the global and local ranks. As of recently, Alexa has well over four million websites ranked. Having said all that, Alexa rank should be taken with a grain of salt. Or a massive bucketload. In other words, we think it to be greatly overrated, as it never takes into account how popular a website is within its niche.
What is a server? It's basically a physical storage device (one that, sometimes, makes up several virtual servers for the cheaper shared hosting) that holds all the files and databases associated with a specific website or websites. Obviously, it's a touch more complicated than that (servers also have processors), but the essence is quite simple - your browser contacts the server, which then sends all the neccessary information and files to your computer. Each physical server has a unique IP address assigned to it, too, for easy recognition.
If you need more raw data, here's what we managed to gather:
Header information |
---|
HTTP/1.1 200 OK Server: nginx Date: Wed, 28 Jun 2017 13:06:11 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding X-Sorting-Hat-PodId: 16 X-Sorting-Hat-PodId-Cached: 0 X-Sorting-Hat-ShopId: 15778247 X-Sorting-Hat-Section: pod X-Sorting-Hat-ShopId-Cached: 0 Vary: Accept-Encoding X-ShopId: 15778247 X-ShardId: 16 Content-Language: pt-BR ETag: cacheable:ce6cd2bc31893a4c0b64307c797a390c X-Alternate-Cache-Key: cacheable:1e60371e1d4d79893588a20ca8d5143a X-Cache: hit, server Set-Cookie: secure_customer_sig=; path=/; expires=Sun, 28 Jun 2037 13:06:11 -0000; secure; HttpOnly X-Request-Id: 615ae413-8a65-4ddd-a0a6-ad1578bac4b7 Content-Security-Policy: block-all-mixed-content; 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=615ae413-8a65-4ddd-a0a6-ad1578bac4b7 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=615ae413-8a65-4ddd-a0a6-ad1578bac4b7 P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR" X-Dc: ash Set-Cookie: _landing_page=%2F; Expires=Wed, 12-Jul-17 13:06:11 GMT; Path=/; HttpOnly Set-Cookie: _orig_referrer=; Expires=Wed, 12-Jul-17 13:06:11 GMT; Path=/; HttpOnly Set-Cookie: cart_sig=; path=/; expires=Wed, 12 Jul 2017 13:06:11 -0000; HttpOnly X-Content-Type-Options: nosniff |
WHOIS entry |
---|
domain: oson.com.br owner: marina Azevedo owner-c: MAAZE41 admin-c: MAAZE41 tech-c: ANLAL222 billing-c: MAAZE41 nserver: a.sec.dns.br nsstat: 20170707 AA nslastaa: 20170707 nserver: b.sec.dns.br nsstat: 20170707 AA nslastaa: 20170707 dsrecord: 1801 RSASHA1 9939C0C49408055597A0A8C6E0328507EFFEF9E6 dsstatus: 20170707 DSOK dslastok: 20170707 saci: yes created: 20120626 #10103684 changed: 20170609 expires: 20190626 status: published nic-hdl-br: MAAZE41 person: marina Azevedo created: 20100205 changed: 20170609 nic-hdl-br: ANLAL222 person: André Lins de Albuquerque created: 20151012 changed: 20151012 |
Typos are not uncommon, not even with website addresses. More than that, the more popular the website, the more typos there tend to happen. We have gathered and generated the following list of most frequently encountered mistypes for oson.com.br:
Here is a list of some more reports for you to check. If you found this one on oson.com.br useful, the following list will be of interest to you, too:
This list contains 370 top level domain variantions for oson.com.br domain name: