Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | buildblog | Let´s talk about business | Search engines recommend title length of around 50-60 characters. The length of this title is 37. |
Meta description | Let´s talk about business | To make sure all the meta description is visible in search results page, Google recommends length of up to 320 characters at the most. This description has exactly 25 characters. |
Load time | 0.1979 seconds on average | Website load speed is pretty fast. |
Alexa global | 885 286, 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 182 links | This is a normal amount of links. |
Page HTML size | 51.1KB | 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 188.40.55.198. | 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: Sun, 18 Jun 2017 07:21:58 GMT Server: Apache/2.4.7 (Ubuntu) X-Powered-By: PHP/5.5.9-1ubuntu4.20 Link: <http://buildblog.de/wp-json/>; rel="https://api.w.org/" Vary: Accept-Encoding Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 |
WHOIS information |
---|
Domain: buildblog.de Nserver: ns11.oricom.de Nserver: ns12.oricom.de Nserver: ns13.oricom.de Nserver: ns14.oricom.de Status: connect Changed: 2011-01-10T23:55:25+01:00 [Tech-C] Type: PERSON Name: Jakob Zogalla Address: Mittelstr. 7 PostalCode: 50676 City: Koeln CountryCode: DE Phone: +49-221-2920100 Fax: +49-221-2920112 Email: Changed: 2010-11-02T19:46:49+01:00 [Zone-C] Type: PERSON Name: Jakob Zogalla Address: Mittelstr. 7 PostalCode: 50676 City: Koeln CountryCode: DE Phone: +49-221-2920100 Fax: +49-221-2920112 Email: Changed: 2010-11-02T19:46:49+01:00 |
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 1790 mistypes, associated with buildblog.de:
If you are curious about what TLD extensions could also match the domain name of buildblog.de 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: