Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Enchufa2 | Search engines recommend title length of around 50-60 characters. The length of this title is 8. |
| Load time | 2.1896 seconds on average | Load speed is a concern and should be improved if and when possible. |
| Alexa global | 992 863, 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 154 links | This is a normal amount of links. |
| Page HTML size | 2.4KB | How do we put this... improvement is quite necessary. Load speed is a very important factor in so many ways! |
| Website server | Server appears to be online. The IP address for the server is 185.60.216.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 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'; 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=600; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="k2v657xBsOVe1PQRwOsHsw3bsGT2VzIqz5K+59sNQws="; pin-sha256="gMxWOrX4PMQesK9qFNbYBxjBfjUvlkn/vN1n+L9lE5E="; pin-sha256="q4PO2G2cbkZhZ82+JgmRUyGMoAeozA+BSXVXQWB8XWQ="; includeSubdomains; 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 Content-Type: text/html;charset=utf-8 facebook-api-version: v2.3 X-Content-Type-Options: nosniff Cache-Control: private, no-cache, no-store, must-revalidate Vary: Accept-Encoding X-FB-Debug: LQ7aRC2FzY/K0EvRwIWRLsIb+fofbb7jI4h02ZQacd6Duvx2l56YoX/h/RjRPZX+suCivpee0hTsxd0QCQ2IgQ== Date: Mon, 30 Oct 2017 03:51:46 GMT Transfer-Encoding: chunked Connection: keep-alive |
| WHOIS information |
|---|
This TLD has no whois server, but you can access the whois database at https://www.nic.es/ |
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 1760 mistypes, associated with enchufa2.es:
If you are curious about what TLD extensions could also match the domain name of enchufa2.es 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: