Оценка вашего веб-сайта

Similar Ranking

2
КУПИ-ПРОДАЙ
freesite.ml
2
МАГАЗИН СКРИПТОВ И ШАБЛОНОВ
scrimag.ru

Latest Sites

26
MONTSERRAT – MULTIPURPOSE
exclick.pro

2 proflinks.ru Last Updated: 3 years

Success 31% of passed verification steps
Warning 23% of total warning
Errors 46% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 94%
Best Practices Desktop Score 58%
SEO Desktop Score 82%
PWA Desktop Score 0%
Performance Mobile Score 80%
Best Practices Mobile Score 58%
SEO Mobile Score 69%
PWA Mobile Score 0%
Page Authority Authority 0%
Авторитет домена Авторитет домена 0%
Moz Rank 0.0/10
Показатель отказов Rate 0%
Charset Encoding
Great, language/character encoding is specified: WINDOWS-1251
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 19 Characters
http://proflinks.ru
Google Preview Your look like this in google search result
proflinks.ru
http://proflinks.ru
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN B
Text Size: ~1 B Ratio: 100.00%

Estimation Traffic and Earnings

4,673
Unique Visits
Daily
8,645
Pages Views
Daily
$6
Income
Daily
130,844
Unique Visits
Monthly
246,383
Pages Views
Monthly
$150
Income
Monthly
1,514,052
Unique Visits
Yearly
2,904,720
Pages Views
Yearly
$1,584
Income
Yearly

Desktop

Desktop Screenshot
Defer offscreen images Potential savings of 13 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Efficiently encode images Potential savings of 10 KiB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 30 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
Preload Largest Contentful Paint image Potential savings of 70 ms
Preload the image used by the LCP element in order to improve your LCP time
Serve images in next-gen formats Potential savings of 173 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoids an excessive DOM size 483 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies 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
Minimizes main-thread work 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 3 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
Avoids enormous network payloads Total size was 426 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 170 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Keep request counts low and transfer sizes small 43 requests • 426 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Does not use HTTPS 38 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce unused JavaScript Potential savings of 69 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 2.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted
Network Round Trip Times 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

Mobile

Mobile Screenshot
First Contentful Paint (3G) 2866 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources 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
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Efficiently encode images Potential savings of 10 KiB
Optimized images load faster and consume less cellular data
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Network Round Trip Times 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
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize third-party usage Third-party code blocked the main thread for 60 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
Reduce unused JavaScript Potential savings of 70 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Keep request counts low and transfer sizes small 43 requests • 449 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 4.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 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
Does not use HTTPS 38 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids an excessive DOM size 483 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve images in next-gen formats Potential savings of 182 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids enormous network payloads Total size was 449 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 3 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
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 5.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Speed And Optimization Tips

Скорость веб-сайта оказывает огромное влияние на производительность, влияя на пользовательский опыт, коэффициенты конверсии и даже рейтинг. Уменьшая время загрузки страницы, пользователи с меньшей вероятностью будут отвлекаться, а поисковые системы с
Title сайта
Предупреждение! Ваш заголовок не оптимизирован
Description сайта
Предупреждение! Ваше описание не оптимизировано
Robots.txt
Поздравляю! На вашем сайте есть файл robots.txt
Sitemap.xml
Предупреждение! Не удалось найти файл карты сайта для вашего сайта
SSL безопасный
Предупреждение! Ваш веб-сайт не защищен протоколом SSL (HTTPS).
Заголовки
Предупреждение! На вашей странице нет заголовков H1 и H2. Заголовки H1 и H2 помогают указать поисковым системам важные темы вашей страницы.
Черный список
Поздравляю! Ваш сайт не занесен в черный список
Валидатор W3C
Предупреждение! На вашем сайте есть ошибки W3C
Ускоренные мобильные страницы (AMP)
Предупреждение! У вашего сайта нет AMP-версии
Авторитет домена
Предупреждение! Авторитет домена вашего сайта медленный. Хорошо иметь авторитет домена больше 25.
GZIP Сжатие
Предупреждение! Ваш сайт не сжат, это может замедлить реакцию посетителей.
Favicon
Поздравляю! У вашего веб-сайта есть значка favicon
Неработающие ссылки
Поздравляю! У вас нет битых ссылок Просмотр ссылок

Alexa Rank

202,583

Global Rank

17,645

Russia
Traffic
Поиск

Информационный Сервер

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере.
HTTP/1.1 200 OK
Date: Tue, 29 Mar 2022 17:55:01 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
X-Powered-By: PHP/5.4.4-14+deb7u12
Set-Cookie: PHPSESSID=vh5fje84smigh1kjb3jh29psk7; path=/
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
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=s5KjqQ6w%2FJWhWlK68JUA6cJ9kfdQqvOV5GiAo9qqUZn2qfyJ6rFMlHV78Rw5XTA9gmVMKmmQ%2F6Rfcbd2izR96Fe1ImEJIQXMnOEndqY2Fryny7KOCY5agls3GAXAnKfPE0Khx2BMoYb%2FiQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 6f3a795eef0d7903-DME
Content-Encoding: gzip
Записи DNS Записи ресурсов DNS, связанные с именем хоста
Просмотр записей DNS