Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Home | Search engines recommend title length of around 50-60 characters. The length of this title is 4. |
| Meta description | HEINDL`S PALATSCHINKENKUCHL in Wien hat eine Riesengroße Auswahl an Palatschinken und österreichischen Schmarren zu sehr fairen Preisen | 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 135 characters. |
| Keywords | Palatschinkenkuchl, Palatschinken Lokal, Palatschinkenkeller,Heindl Erich, Fleischpalatschinken, Süsse Palatschinken, Fischpalatschinken, Wien, Käsepalatschinken | We did not expect meta keywords to be used. It's a worrying sign more than anything, really, as websites with meta keywords often tend to be spammy. |
| Load time | 0.7464 seconds on average | Website load speed is pretty fast. |
| Total links on homepage | We found 52 links | This is a normal amount of links. |
| Page HTML size | 46.2KB | 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 89.200.171.57. | 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.
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, 11 Dec 2017 07:00:06 GMT Server: Apache/2.2.22 (Debian) X-Logged-In: False X-Content-Powered-By: K2 v2.8.0 (by JoomlaWorks) P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM" Expires: Wed, 17 Aug 2005 00:00:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Set-Cookie: 761151c61d9ebd68d9615af51393a13c=ee6c0037819b9ea1e95aecac1c355410; path=/; HttpOnly Last-Modified: Mon, 11 Dec 2017 07:00:06 GMT Cache-Control: max-age=33135480, public Vary: Accept-Encoding Transfer-Encoding: chunked Content-Type: text/html; charset=utf-8 |
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 1860 mistypes, associated with palatschinkenkuchl.wien:
If you are curious about what TLD extensions could also match the domain name of palatschinkenkuchl.wien 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: