Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Home · lispgames/lispgames.github.io Wiki · GitHub | Search engines recommend title length of around 50-60 characters. The length of this title is 50. |
| Meta description | A description has not been provided for this site. | 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 50 characters. |
| Load time | 1.1061 seconds on average | Website load speed is pretty fast. |
| Total links on homepage | We found 165 links | This is a normal amount of links. |
| Number of backlinks | Around 15 | Backlinks is one of the key metrics for search engines. This website seems to have a very low number of backlinks, which means poorer rank in search results. |
| Page HTML size | 48.5KB | 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 192.30.253.113. | 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.
As we've mentioned before, traffic is not a key metric. However, the target audience does say a lot about what's been done to optimize the website, as well as what should be done going forwards. Let's see if we have any useful information here.
| Parameter name | Status | Comment |
|---|---|---|
| Related websites | xelf.me lispers.org lispnyc.org landoflisp.com lisperati.com |
These are the websites that fall into the same category as lispgames.org, and so target the same audience and, likely, keywords. To a larger or smaller extent, all of them are competitors. |
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 Server: GitHub.com Date: Thu, 05 Oct 2017 07:42:56 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Status: 200 OK Cache-Control: no-cache Vary: X-PJAX X-UA-Compatible: IE=Edge,chrome=1 Set-Cookie: logged_in=no; domain=.github.com; path=/; expires=Mon, 05 Oct 2037 07:42:56 -0000; secure; HttpOnly Set-Cookie: _gh_sess=eyJzZXNzaW9uX2lkIjoiMTA5NTg1ODcyNjEyYTVmZTAwMDI2MThlYWYzMTc0OGIiLCJsYXN0X3JlYWRfZnJvbV9yZXBsaWNhcyI6MTUwNzE4OTM3NjY3Miwic3B5X3JlcG8iOiJsaXNwZ2FtZXMvbGlzcGdhbWVzLmdpdGh1Yi5pbyIsInNweV9yZXBvX2F0IjoxNTA3MTg5Mzc2LCJfY3NyZl90b2tlbiI6IjF1YzdhU0UvZmdSeTVkeHpjc3VNaUx6cXFaNGUrbGFPWGtBeTFqNTJpMU09In0%3D--68d03f270b1786dcfc93f8e79bc8fc1ef8b3009b; path=/; secure; HttpOnly X-Request-Id: 4ed189cec3e297b814cb3700247ebab7 X-Runtime: 0.176814 Content-Security-Policy: default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src render.githubusercontent.com; connect-src 'self' uploads.github.com status.github.com collector.githubapp.com api.github.com www.google-analytics.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com wss://live.github.com; font-src assets-cdn.github.com; form-action 'self' github.com gist.github.com; frame-ancestors 'none'; img-src 'self' data: assets-cdn.github.com identicons.github.com collector.githubapp.com github-cloud.s3.amazonaws.com *.githubusercontent.com; media-src 'none'; script-src assets-cdn.github.com; style-src 'unsafe-inline' assets-cdn.github.com Strict-Transport-Security: max-age=31536000; includeSubdomains; preload Public-Key-Pins: max-age=5184000; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="RRM1dGqnDFsCJXBTHky16vi1obOlCgFFn/yOhI/y+ho="; pin-sha256="k2v657xBsOVe1PQRwOsHsw3bsGT2VzIqz5K+59sNQws="; pin-sha256="K87oWBWM9UZfyddvDfoxL+8lpNyoUB2ptGtn0fv6G2Q="; pin-sha256="IQBnNBEiFuhj+8x6X8XLgh01V9Ic5/V3IRQLNFFc7v4="; pin-sha256="iie1VXtL7HzAMF+/PVPR9xzT80kQxdZeJ+zduCB3uj0="; pin-sha256="LvRiGEjRqfzurezaWuj8Wie2gyHMrW5Q06LspMnox7A="; includeSubDomains X-Content-Type-Options: nosniff X-Frame-Options: deny X-XSS-Protection: 1; mode=block X-Runtime-rack: 0.184732 X-GitHub-Request-Id: A1E0:FE59:F9783E:189348A:59D5E280 |
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 1755 mistypes, associated with lispgames.org:
If you are curious about what TLD extensions could also match the domain name of lispgames.org 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: