Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | Connecting Londoners | Search engines recommend title length of around 50-60 characters. The length of this title is 20. |
Meta description | Connecting Londoners for a more networked city | 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 46 characters. |
Load time | 2.1013 seconds on average | Load speed is a concern and should be improved if and when possible. |
Total links on homepage | We found 302 links | This is a normal amount of links. |
Page HTML size | 44.5KB | 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 52.43.4.201. | 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 Access-Control-Allow-Origin: * Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Content-Type: text/html;charset=utf8 Date: Fri, 12 Jan 2018 17:24:45 GMT Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Fri, 27 Oct 2017 14:19:52 GMT Link: <http://www.connectinglondoners.blog/indieauth/auth>; rel="authorization_endpoint" Link: <http://www.connectinglondoners.blog/indieauth/token>; rel="token_endpoint" Link: <http://www.connectinglondoners.blog/micropub/endpoint>; rel="micropub" Link: <http://www.connectinglondoners.blog/webmention/>; rel="http://webmention.org/" Link: <http://www.connectinglondoners.blog/webmention/>; rel="webmention" Link: <http://withknown.superfeedr.com/>; rel="hub" Link: <http://www.connectinglondoners.blog/2017/joining-up-the-dots-to-show-ourwayahead>; rel="self" P3P: CP="CAO PSA OUR" Pragma: no-cache Server: Apache Set-Cookie: known=sqd78k234rbkfv6dkhkrh3f2n3eka8kmdjq0nrnlgiqn4l74ed50; expires=Fri, 19-Jan-2018 17:24:45 GMT; Max-Age=604800; path=/; HttpOnly X-Clacks-Overhead: GNU Terry Pratchett X-Known-Build-Fingerprint: 03dbe5af8293d3217c405326e173bd83ff93342a887a8650d47f9168196ebc0c Content-Length: 45145 Connection: keep-alive |
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 1770 mistypes, associated with connectinglondoners.blog:
If you are curious about what TLD extensions could also match the domain name of connectinglondoners.blog 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: