Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | Search engines recommend title length of around 50-60 characters. The length of this title is 8. | |
Load time | 1.1335 seconds on average | Website load speed is pretty fast. |
Alexa global | 821 471, 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 51 links | This is a normal amount of links. |
Page HTML size | 193.7KB | 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 157.240.21.35. | 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 Cache-Control: private, no-cache, no-store, must-revalidate Expires: Sat, 01 Jan 2000 00:00:00 GMT content-security-policy: default-src * data: blob:;script-src *.facebook.com *.fbcdn.net *.facebook.net *.google-analytics.com *.virtualearth.net *.google.com 127.0.0.1:* *.spotilocal.com:* 'unsafe-inline' 'unsafe-eval' fbstatic-a.akamaihd.net fbcdn-static-b-a.akamaihd.net *.atlassolutions.com blob: data: 'self';style-src data: blob: 'unsafe-inline' *;connect-src *.facebook.com *.fbcdn.net *.facebook.net *.spotilocal.com:* *.akamaihd.net wss://*.facebook.com:* https://fb.scanandcleanlocal.com:* *.atlassolutions.com attachment.fbsbx.com ws://localhost:* blob: *.cdninstagram.com 'self'; Access-Control-Allow-Credentials: true X-Frame-Options: DENY Access-Control-Allow-Origin: https://www.facebook.com Access-Control-Expose-Headers: X-FB-Debug, X-Loader-Length Pragma: no-cache Vary: Origin public-key-pins-report-only: max-age=600; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="k2v657xBsOVe1PQRwOsHsw3bsGT2VzIqz5K+59sNQws="; pin-sha256="gMxWOrX4PMQesK9qFNbYBxjBfjUvlkn/vN1n+L9lE5E="; pin-sha256="q4PO2G2cbkZhZ82+JgmRUyGMoAeozA+BSXVXQWB8XWQ="; report-uri="http://reports.fb.com/hpkp/" access-control-allow-method: OPTIONS Strict-Transport-Security: max-age=15552000; preload X-XSS-Protection: 0 X-Content-Type-Options: nosniff Vary: Accept-Encoding Content-Type: text/html; charset=UTF-8 X-FB-Debug: T/FtgjfTZm2La5VHiaoxxKp8/65pRaLEEC9TACgkKDQgNqMcXU9CBJYjjWHpelQCPZEzL9FeuDsHTEMd0v9tZA== Date: Sat, 07 Oct 2017 02:08:24 GMT Transfer-Encoding: chunked Connection: keep-alive |
WHOIS information |
---|
domain: 00riodejaneiro.com.br owner: Espaço Infinito Rest. e Bar Ltda. owner-c: AFM235 admin-c: AFM235 tech-c: ARCOR22 billing-c: AFM235 nserver: ns2580.dizinc.com nsstat: 20171005 AA nslastaa: 20171005 nserver: ns2581.dizinc.com nsstat: 20171005 AA nslastaa: 20171005 saci: yes created: 20111130 #9184565 changed: 20170210 expires: 20171130 status: published nic-hdl-br: AFM235 person: Arnaldo Franco Meriano created: 20030609 changed: 20170213 nic-hdl-br: ARCOR22 person: Armando Cordeiro created: 20110202 changed: 20160605 |
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 1841 mistypes, associated with 00riodejaneiro.com.br:
If you are curious about what TLD extensions could also match the domain name of 00riodejaneiro.com.br 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: