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) | Amo Café Espresso Cafeína Total - Startseite | Facebook | Sticking to between 50-60 characters for meta title length is a good idea. The length of this website's meta title is 55. |
Website meta description | Amo Café Espresso Cafeína Total in São Paulo. Amo Espresso sua página do Café no Facebook http://www.AmoEspresso.com.br | The length of the meta description is 119 characters. Google recommends up to around 280-320 characters at the most. |
Website load speed | Approximately 3.1986 seconds | It takes too long to load the website – we would suggest the webmaster to look into it. |
Rank by Alexa | 804,905 | 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 286 | A good amount of links and nothing to worry about. |
Size of page HTML | 564.4KB | If it were up to us, we'd urge the webmaster to improve. The result isn't very good, you see. Just saying. |
Server data | Server seems to be online. IP adress for this domain is 179.60.192.36. | 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 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' chrome-extension://boadgeojelhgndaghljhdicfkmllpafd chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm; X-Frame-Options: DENY X-XSS-Protection: 0 Access-Control-Allow-Credentials: true 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=500; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E="; pin-sha256="q4PO2G2cbkZhZ82+JgmRUyGMoAeozA+BSXVXQWB8XWQ="; report-uri="http://reports.fb.com/hpkp/" access-control-allow-method: OPTIONS Expires: Sat, 01 Jan 2000 00:00:00 GMT Strict-Transport-Security: max-age=15552000; preload X-Content-Type-Options: nosniff Cache-Control: private, no-cache, no-store, must-revalidate Vary: Accept-Encoding Content-Type: text/html; charset=UTF-8 X-FB-Debug: pkDk8KKPBM/d3srT2BNvJs80ORlvyfl/bJMHIP+DkxMCHZxVd9woN8o88SMlpoBwN0btY2budBICR+ZBQBNXCg== Date: Fri, 09 Jun 2017 22:42:13 GMT Transfer-Encoding: chunked Connection: keep-alive |
WHOIS entry |
---|
domain: amoespresso.com.br owner: PRISCILLA PEREIRA ROSA owner-c: PPRWI admin-c: PPRWI tech-c: ROW5 billing-c: ROW5 nserver: a.sec.dns.br nsstat: 20170708 AA nslastaa: 20170708 nserver: c.sec.dns.br nsstat: 20170708 AA nslastaa: 20170708 dsrecord: 10607 RSASHA1 D4A21EDED0A50B4B5C65AF6A3AF22F5E6316FF62 dsstatus: 20170708 DSOK dslastok: 20170708 saci: yes created: 20111017 #8978793 changed: 20161028 expires: 20171017 status: published nic-hdl-br: PPRWI person: Priscilla Pereira Rosa Wilbert created: 20100721 changed: 20140416 nic-hdl-br: ROW5 person: Rogério Wilbert created: 19980309 changed: 20140928 |
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 amoespresso.com.br:
Here is a list of some more reports for you to check. If you found this one on amoespresso.com.br useful, the following list will be of interest to you, too:
This list contains 370 top level domain variantions for amoespresso.com.br domain name: