Follow recommendations of this health report to keep your site healthy
Examined at : 2023-02-06 21:03:24
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
и | 91 | 16.728 % | No |
Темы | 88 | 16.176 % | No |
Сообщения | 85 | 15.625 % | No |
в | 73 | 13.419 % | No |
Скачать | 45 | 8.272 % | No |
bart | 44 | 8.088 % | No |
на | 35 | 6.434 % | No |
Сегодня | 30 | 5.515 % | No |
по | 25 | 4.596 % | No |
Закреплено | 18 | 3.309 % | No |
не | 16 | 2.941 % | No |
курсы | 15 | 2.757 % | No |
для | 15 | 2.757 % | No |
форума | 14 | 2.574 % | No |
темы | 14 | 2.574 % | No |
Подфорумы | 14 | 2.574 % | No |
Янв | 13 | 2.39 % | No |
тренинги | 12 | 2.206 % | No |
уроки | 11 | 2.022 % | No |
Курсы | 11 | 2.022 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Сегодня в | 30 | 5.515 % | No |
2022 Сегодня | 18 | 3.309 % | No |
Янв 2023 | 13 | 2.39 % | No |
Закреплено Закреплено | 11 | 2.022 % | No |
2023 Сегодня | 10 | 1.838 % | No |
Сообщения 11K | 8 | 1.471 % | No |
на тему | 7 | 1.287 % | No |
курсы по | 6 | 1.103 % | No |
Вчера в | 6 | 1.103 % | No |
Темы 2K | 6 | 1.103 % | No |
2K Сообщения | 6 | 1.103 % | No |
|
5 | 0.919 % | No |
Информационные продукты | 5 | 0.919 % | No |
> | 5 | 0.919 % | No |
Новые сообщения | 5 | 0.919 % | No |
2023 ••• | 4 | 0.735 % | No |
Скачать Как | 4 | 0.735 % | No |
Темы 16K | 4 | 0.735 % | No |
16K Сообщения | 4 | 0.735 % | No |
Курсы тренинги | 4 | 0.735 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
2022 Сегодня в | 18 | 3.309 % | No |
2023 Сегодня в | 10 | 1.838 % | No |
Темы 2K Сообщения | 6 | 1.103 % | No |
Закреплено Закреплено Закреплено | 5 | 0.919 % | No |
> |
5 | 0.919 % | No |
Темы 16K Сообщения | 4 | 0.735 % | No |
Сообщения 11K Темы | 4 | 0.735 % | No |
Янв 2023 ••• | 4 | 0.735 % | No |
Рубедо 2023 Сегодня | 4 | 0.735 % | No |
Темы 12K Сообщения | 4 | 0.735 % | No |
Темы 2 Сообщения | 4 | 0.735 % | No |
на форуме Темы | 3 | 0.551 % | No |
создателей популярных форумов | 3 | 0.551 % | No |
Янв 2023 Gustav | 3 | 0.551 % | No |
Янв 2023 bart | 3 | 0.551 % | No |
о том как | 3 | 0.551 % | No |
Сообщения 11K Скачать | 3 | 0.551 % | No |
Совместные покупки инфопродуктов | 3 | 0.551 % | No |
2022 Вчера в | 3 | 0.551 % | No |
Бизнес под ключ | 3 | 0.551 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Рубедо 2023 Сегодня в | 4 | 0.735 % | No |
для кого английский язык | 3 | 0.551 % | No |
для тех для кого | 3 | 0.551 % | No |
Бизнес под ключ от | 3 | 0.551 % | No |
под ключ от создателей | 3 | 0.551 % | No |
ключ от создателей популярных | 3 | 0.551 % | No |
от создателей популярных форумов | 3 | 0.551 % | No |
linkedin 2022 Сегодня в | 3 | 0.551 % | No |
является родным linkedin 2022 | 3 | 0.551 % | No |
не является родным linkedin | 3 | 0.551 % | No |
язык не является родным | 3 | 0.551 % | No |
английский язык не является | 3 | 0.551 % | No |
кого английский язык не | 3 | 0.551 % | No |
тех для кого английский | 3 | 0.551 % | No |
родным linkedin 2022 Сегодня | 3 | 0.551 % | No |
Темы 176 Сообщения 13K | 2 | 0.368 % | No |
и Гугле Громов 2022 | 2 | 0.368 % | No |
Пошаговый план поиска клиентов | 2 | 0.368 % | No |
Темы 398 Сообщения 11K | 2 | 0.368 % | No |
Темы 25 Сообщения 415 | 2 | 0.368 % | No |
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" />
directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a>
if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
SL | Host | Class | TTL | Type | PRI | Target | IP |
1 | eground.org | IN | 14394 | A | 91.223.123.14 | ||
2 | eground.org | IN | 3592 | NS | ns2.frienddns.info | ||
3 | eground.org | IN | 3592 | NS | ns4.frienddns.net | ||
4 | eground.org | IN | 3592 | NS | ns1.frienddns.info | ||
5 | eground.org | IN | 3592 | NS | ns3.frienddns.net | ||
6 | eground.org | IN | 14400 | MX | 10 | mail.eground.org |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://s1.eground.org/ | content type | text/html; charset=utf-8 |
http code | 200 | header size | 934 |
request size | 378 | filetime | -1 |
ssl verify result | 0 | redirect count | 2 |
total time | 3.320897 | namelookup time | 0.25287 |
connect time | 0.378209 | pretransfer time | 0.652523 |
size upload | 0 | size download | 234247 |
speed download | 70537 | speed upload | 0 |
download content length | 234247 | upload content length | 0 |
starttransfer time | 1.389166 | redirect time | 1.555675 |
redirect url | primary ip | 91.223.123.14 | |
certinfo | primary port | 443 | |
local ip | 103.108.220.126 | local port | 38610 |
97 requests • 1,433 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 960 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 2,040 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
4714 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
1,820 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
3.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Potential savings of 87 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 96 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 1,433 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
8.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
3,139 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More
100 requests • 1,439 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 120 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Potential savings of 100 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 97 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 1,439 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
3,139 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More