Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | inReplay - | Search engines recommend title length of around 50-60 characters. The length of this title is 10. |
Load time | 0.3449 seconds on average | Website load speed is pretty fast. |
Alexa global | 977 813, 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 33 links | This is a normal amount of links. |
Page HTML size | 46.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 104.25.125.36. | 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: Mon, 31 Jul 2017 00:33:16 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Set-Cookie: __cfduid=dda64aed048863fff101752218e34e93c1501461196; expires=Tue, 31-Jul-18 00:33:16 GMT; path=/; domain=.inreplay.com.br; HttpOnly Vary: Accept-Encoding Link: <http://inreplay.com.br/wp-json/>; rel="https://api.w.org/" X-Powered-By: NginxFacil Strict-Transport-Security: max-age=15768000; preload CF-Cache-Status: EXPIRED Expires: Tue, 01 Aug 2017 00:33:16 GMT Cache-Control: public, max-age=86400 Server: cloudflare-nginx CF-RAY: 386c771ea74f2744-FRA |
WHOIS information |
---|
domain: inreplay.com.br owner: Gustavo Henrique Alencar de Carvalho owner-c: GHACA13 admin-c: GHACA13 tech-c: GHACA13 billing-c: GHACA13 nserver: john.ns.cloudflare.com nsstat: 20170725 AA nslastaa: 20170725 nserver: ulla.ns.cloudflare.com nsstat: 20170725 AA nslastaa: 20170725 saci: yes created: 20170404 #16843087 changed: 20170622 expires: 20180404 status: published nic-hdl-br: GHACA13 person: Gustavo Henrique Alencar de Carvalho created: 20170404 changed: 20170404 |
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 1764 mistypes, associated with inreplay.com.br:
If you are curious about what TLD extensions could also match the domain name of inreplay.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: