Here is an overview of what we consider to be the key website statistics and information:
Parameter name | Status | Comment |
---|---|---|
Website meta title | Search engines recommend title length of around 50-60 characters. The length of this title is 12. | |
Load time | 4.5628 seconds on average | Load speed is a concern and should be improved if and when possible. |
Alexa global | 874 835, 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 100 links | This is a normal amount of links. |
Page HTML size | 49.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 37.140.192.119. | 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 Server: nginx Date: Tue, 13 Jun 2017 15:16:33 GMT Content-Type: text/html; charset=windows-1251 Content-Length: 50439 Connection: keep-alive Vary: Accept-Encoding X-Powered-By: PHP/5.6.30 P3P: policyref="/bitrix/p3p.xml", CP="NON DSP COR CUR ADM DEV PSA PSD OUR UNR BUS UNI COM NAV INT DEM STA" X-Powered-CMS: Bitrix Site Manager (96571c6341f78a42bc0366af1aa504ff) Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Set-Cookie: PHPSESSID=29a2b2ef84a1bb2caef77ab790467756; path=/; HttpOnly Set-Cookie: BITRIX_SM_SITE_LANG=DE; expires=Fri, 08-Jun-2018 15:16:32 GMT; Max-Age=31104000; path=/ |
WHOIS information |
---|
domain: MEGI.RU nserver: ns1.masterhost.ru. nserver: ns2.masterhost.ru. nserver: ns.masterhost.ru. state: REGISTERED, DELEGATED, VERIFIED org: Ltd "MEGI" registrar: RU-CENTER-RU admin-contact: https://www.nic.ru/whois created: 2005-11-14T21:00:00Z paid-till: 2017-11-14T21:00:00Z free-date: 2017-12-16 source: TCI Last updated on 2017-05-12T15:16:33Z |
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 1392 mistypes, associated with megi.ru:
If you are curious about what TLD extensions could also match the domain name of megi.ru 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: