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

Similar Ranking

26
ПОЛУЧИТЬ ОТВЕТ НА ВОПРОС - БАЗА ДАННЫХ ВОПРОСОВ И ОТВЕТОВ
ru.qask.org
26
ОНЛАЙН ГЕНЕРАТОР ПАРОЛЕЙ
sitest.tk
26
БЕСПЛАТНЫЕ СКРИПТЫ. КАТАЛОГ СКРИПТОВ ДЛЯ САЙТА. СОЗДАНИЕ САЙТОВ.
directoryweb.ru
26
HỎI VÀ ĐÁP - TIỀN ĐIỆN TỬ, QUẢN TRỊ MÁY CHỦ, CMS, HỆ ĐIỀU HÀNH.
vn.qask.org
26
ÎNTREBĂRI ȘI RĂSPUNSURI IT - QASK.ORG
ro.qask.org
24
COUNTRYCRAFTSDIRECTORY.COM – ทุกประเทศในโลกและเมืองหลวงของพวกเขา
countrycraftsdirectory.com
22
ОЙ!
yandex.ru

Latest Sites

14
SEOGRAN.RU
seogran.ru
41
ZADOLLAR.RU — ПРОСТО ЕЩЕ ОДИН WORDPRESS САЙТ
zadollar.ru
19
СИСТЕМА ОБМЕНА ВИЗИТАМИ И ПОСЕЩЕНИЯМИ
freevisit.ru
31
ГЛАВНАЯ СТРАНИЦА | ГОРОД ФАКТОВ
vizit-trafik.ru
19
ЖУРНАЛ «ФОКУС ВНИМАНИЯ»
fokus-vnimaniya.com
19
ПРИОРБАНК - ВЕДУЩИЙ КОММЕРЧЕСКИЙ БАНК РЕСПУБЛИКИ БЕЛАРУСЬ
priorbank.by

26 directoryweb.ru Last Updated: 2 years

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

Desktop

Mobile

Performance Desktop Score 67%
Best Practices Desktop Score 85%
SEO Desktop Score 83%
PWA Desktop Score 33%
Performance Mobile Score 96%
Best Practices Mobile Score 92%
SEO Mobile Score 84%
PWA Mobile Score 30%
Page Authority Authority 0%
Авторитет домена Авторитет домена 0%
Moz Rank 0.0/10
Показатель отказов Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 64 Characters
БЕСПЛАТНЫЕ СКРИПТЫ. КАТАЛОГ СКРИПТОВ ДЛЯ САЙТА. СОЗДАНИЕ САЙТОВ.
Meta Description 0 Characters
NO DATA
Effective URL 23 Characters
https://directoryweb.ru
Excerpt Page content
Бесплатные скрипты. Каталог скриптов для сайта. Создание сайтов. DirectoryWeb ...
Keywords Cloud Density
xfvalue52 nazvanie26 скрипт23 вебмастеру14 скрипты13 stoimost13 tematika13 directoryweb11 подробнее10 онлайн9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
xfvalue 52
nazvanie 26
скрипт 23
вебмастеру 14
скрипты 13
stoimost 13
tematika 13
directoryweb 11
подробнее 10
онлайн 9
Google Preview Your look like this in google search result
БЕСПЛАТНЫЕ СКРИПТЫ. КАТАЛОГ СКРИПТОВ ДЛЯ САЙТА. СОЗДАНИЕ САЙ
https://directoryweb.ru
Бесплатные скрипты. Каталог скриптов для сайта. Создание сайтов. DirectoryWeb ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~92.37 KB
Code Size: ~68.44 KB
Text Size: ~23.93 KB Ratio: 25.91%

Estimation Traffic and Earnings

303
Unique Visits
Daily
560
Pages Views
Daily
$0
Income
Daily
8,484
Unique Visits
Monthly
15,960
Pages Views
Monthly
$0
Income
Monthly
98,172
Unique Visits
Yearly
188,160
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 403 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Initial server response time was short Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
Serve static assets with an efficient cache policy 95 resources found
A long cache lifetime can speed up repeat visits to your page
Minify CSS Potential savings of 8 KiB
Minifying CSS files can reduce network payload sizes
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Max Potential First Input Delay 350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript Potential savings of 34 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Eliminate render-blocking resources Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Keep request counts low and transfer sizes small 229 requests • 4,163 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid enormous network payloads Total size was 4,163 KiB
Large network payloads cost users real money and are highly correlated with long load times
Use video formats for animated content Potential savings of 424 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Largest Contentful Paint 0.9 s
Largest Contentful Paint marks the time at which the largest 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
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Enable text compression Potential savings of 12 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 220 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
Cumulative Layout Shift 0.265
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 22 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
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce unused JavaScript Potential savings of 1,793 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images Potential savings of 352 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 390 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers Potential savings of 18 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minimize main-thread work 2.5 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
Serve images in next-gen formats Potential savings of 713 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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
Time to Interactive 4.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid an excessive DOM size 864 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)
Reduce unused CSS Potential savings of 572 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

Mobile

Mobile Screenshot
Avoid chaining critical requests 4 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
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Keep request counts low and transfer sizes small 46 requests • 1,003 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Eliminate render-blocking resources Potential savings of 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint (3G) 2218 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce unused JavaScript Potential savings of 23 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 549 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Tap targets are not sized appropriately 87% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible
Efficiently encode images Potential savings of 279 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Document uses legible font sizes 97.64% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
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
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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
Serve static assets with an efficient cache policy 29 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids enormous network payloads Total size was 1,003 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
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
Avoids an excessive DOM size 300 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)
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.154
Cumulative Layout Shift measures the movement of visible elements within the viewport

Speed And Optimization Tips

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

Alexa Rank

738,499

Global Rank

738,499

Global
Traffic
Поиск

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

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере.
HTTP/2 200 
server: nginx/1.14.1
date: Mon, 20 Dec 2021 08:56:07 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding
x-powered-by: PHP/5.6.40
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=bqtj39oq2e3ehtgolrhgnu6pg1; path=/; domain=.directoryweb.ru; secure; HttpOnly
x-power-supply-by: 220 Volt
strict-transport-security: max-age=31536000;
content-encoding: gzip
Записи DNS Записи ресурсов DNS, связанные с именем хоста
Просмотр записей DNS