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

Similar Ranking

19
СИСТЕМА ОБМЕНА ВИЗИТАМИ И ПОСЕЩЕНИЯМИ
freevisit.ru
19
SEO ФОРУМ ВЕБМАСТЕРОВ DLE
forumdle.ru
19
ADVEAR.RU - РЕКЛАМА И ЗАРАБОТОК
advear.ru
19
ВСЁ ПРО СТАЛКЕР - МОДЫ, ФАЙЛЫ, СЕКРЕТЫ, ПРОХОЖДЕНИЕ, НОВОСТИ... - ВАШ ПУТЕВОДИТЕЛЬ ПО ИГРЕ "СТАЛКЕР"
prostalker.ru
19
БАННЕРООБМЕННАЯ СЕТЬ - 468.SURF
468.surf
19
PR-CY
pr-cy.ru
19
MINIHD.RU
minihd.ru

Latest Sites

26
MONTSERRAT – MULTIPURPOSE
exclick.pro

19 forumdle.ru Last Updated: 3 years

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

Desktop

Mobile

Performance Desktop Score 47%
Best Practices Desktop Score 92%
SEO Desktop Score 92%
PWA Desktop Score 22%
Performance Mobile Score 12%
Best Practices Mobile Score 77%
SEO Mobile Score 90%
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 25 Characters
SEO ФОРУМ ВЕБМАСТЕРОВ DLE
Meta Description 103 Characters
Форум посвящён движку dle, у нас вы можете найти модули, шаблоны, хаки, SEO продвижение и многое другое
Effective URL 19 Characters
https://forumdle.ru
Excerpt Page content
SEO форум вебмастеров DLE ...
Keywords Cloud Density
сообщения13 новые7 ответы7 программы7 шаблон6 последние6 вопросы6 поиск6 партнёрские5 обновлено5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
сообщения 13
новые 7
ответы 7
программы 7
шаблон 6
последние 6
вопросы 6
поиск 6
партнёрские 5
обновлено 5
Google Preview Your look like this in google search result
SEO ФОРУМ ВЕБМАСТЕРОВ DLE
https://forumdle.ru
Форум посвящён движку dle, у нас вы можете найти модули, шаблоны, хаки, SEO продвижение и многое другое
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~129.07 KB
Code Size: ~72.04 KB
Text Size: ~57.02 KB Ratio: 44.18%

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images Potential savings of 83 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 3,451 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 24 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
Minify JavaScript Potential savings of 26 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Serve static assets with an efficient cache policy 74 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 480 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.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 480 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 310 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid an excessive DOM size 1,573 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 736 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Cumulative Layout Shift 0.123
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid enormous network payloads Total size was 3,980 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage Third-party code blocked the main thread for 210 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
Minimizes main-thread work 1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Total Blocking Time 430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images Potential savings of 277 KiB
Optimized images load faster and consume less cellular data
Serve images in next-gen formats Potential savings of 371 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Use video formats for animated content Potential savings of 156 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
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
Defer offscreen images Potential savings of 11 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small 114 requests • 3,980 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid serving legacy JavaScript to modern browsers Potential savings of 13 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Mobile

Mobile Screenshot
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive 24.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests 24 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
Largest Contentful Paint 10.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Tap targets are not sized appropriately 67% 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
Keep request counts low and transfer sizes small 115 requests • 3,980 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimize main-thread work 6.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid enormous network payloads Total size was 3,980 KiB
Large network payloads cost users real money and are highly correlated with long load times
Document uses legible font sizes 99.49% 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
Cumulative Layout Shift 0.322
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce the impact of third-party code Third-party code blocked the main thread for 2,060 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
Defer offscreen images Potential savings of 11 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Reduce JavaScript execution time 3.0 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
Reduce unused CSS Potential savings of 736 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minify JavaScript Potential savings of 26 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Speed Index 10.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid an excessive DOM size 1,573 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)
Max Potential First Input Delay 1,980 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 2,500 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused JavaScript Potential savings of 3,452 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Meaningful Paint 7.0 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint (3G) 6136 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Contentful Paint 3.1 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
Serve static assets with an efficient cache policy 74 resources found
A long cache lifetime can speed up repeat visits to your page
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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 images in next-gen formats Potential savings of 371 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid serving legacy JavaScript to modern browsers Potential savings of 13 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
Efficiently encode images Potential savings of 277 KiB
Optimized images load faster and consume less cellular data
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Use video formats for animated content Potential savings of 156 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
Eliminate render-blocking resources Potential savings of 2,130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

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

99,999,999

Global Rank

99,999,999

-
Traffic
Поиск

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

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере.
HTTP/2 200 
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
last-modified: Thu, 17 Feb 2022 17:58:08 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: private, no-cache, max-age=0
vary: Accept-Encoding,User-Agent
content-type: text/html; charset=utf-8
set-cookie: xf_csrf=zrLhiSqn7WiGMYcj; path=/; secure
content-length: 29281
date: Thu, 17 Feb 2022 17:58:08 GMT
server: LiteSpeed
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
Записи DNS Записи ресурсов DNS, связанные с именем хоста
Просмотр записей DNS