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

Similar Ranking

14
SEOGRAN.RU
seogran.ru
14
REKIZ.RU РЕКЛАМА И ЗАРАБОТОК
rekiz.ru
14
WELCOME TO NGINX!
mangohost.net
14
ДЛЯ МАЛОГО И МИКРОБИЗНЕСА (ООО, ИП И САМОЗАНЯТЫЕ) | VRN-BUH.RU
vrn-buh.ru
14
БАЗА ПОСТАВЩИКОВ ОНЛАЙН
supplierbase.forum-top.ru
14
SLIVATORR
slivattor.blogspot.com
14
ОНЛАЙН ГЕНЕРАТОР ПАРОЛЕЙ
passwr.ru

Latest Sites

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

14 rekiz.ru Last Updated: 2 years

Success 63% of passed verification steps
Warning 7% of total warning
Errors 30% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 69%
SEO Desktop Score 82%
PWA Desktop Score 22%
Performance Mobile Score 76%
Best Practices Mobile Score 69%
SEO Mobile Score 89%
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 28 Characters
REKIZ.RU РЕКЛАМА И ЗАРАБОТОК
Meta Description 0 Characters
NO DATA
Effective URL 16 Characters
https://rekiz.ru
Excerpt Page content
REKiZ.Ru Реклама и Заработок Контакты Вход Регистрция   Вы не авторизированы Войти на сайт Регистра...
Keywords Cloud Density
реклама7 визитами5 обмен5 заработок4 сайт4 ссылках3 задания3 rekiz3 личный2 кабинет2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
реклама 7
визитами 5
обмен 5
заработок 4
сайт 4
ссылках 3
задания 3
rekiz 3
личный 2
кабинет 2
Google Preview Your look like this in google search result
REKIZ.RU РЕКЛАМА И ЗАРАБОТОК
https://rekiz.ru
REKiZ.Ru Реклама и Заработок Контакты Вход Регистрция   Вы не авторизированы Войти на сайт Регистра...
Robots.txt File Detected
http://rekiz.ru/robots.txt
Sitemap.xml File Detected
http://rekiz.ru/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~15.69 KB
Code Size: ~8.15 KB
Text Size: ~7.54 KB Ratio: 48.04%

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
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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
Avoid chaining critical requests 6 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 403 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce unused CSS Potential savings of 60 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 64 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images Potential savings of 77 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Does not use HTTPS 1 insecure request 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
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
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 7 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize third-party usage Third-party code blocked the main thread for 0 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
Включает интерфейсные библиотеки JavaScript с известными уязвимостями безопасности 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 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
Minimizes main-thread work 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size 247 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)
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 22 requests • 403 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript Potential savings of 43 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
Avoid chaining critical requests 6 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
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 5.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 2430 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Cumulative Layout Shift 0.071
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids an excessive DOM size 247 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 10 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Tap targets are not sized appropriately 68% 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
Serve images in next-gen formats Potential savings of 64 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Document uses legible font sizes 100% 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
Reduce JavaScript execution time 1.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Манифест веб-приложения или работник службы не соответствуют требованиям к возможности установки 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
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small 22 requests • 403 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads Total size was 403 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused CSS Potential savings of 59 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time 830 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 43 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Does not use HTTPS 1 insecure request 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
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce the impact of third-party code Third-party code blocked the main thread for 890 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
Initial server response time was short Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 3.0 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 59 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Max Potential First Input Delay 400 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 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 Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted

Speed And Optimization Tips

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

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Поиск

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

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере. 
HTTP/2 200 
set-cookie: PHPSESSID=s14ke4iafp2rd2nba042p153k7; path=/; secure
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: max-age=0, private, must-revalidate                           
pragma: no-cache
content-type: text/html; charset=UTF-8
date: Thu, 17 Feb 2022 17:53:12 GMT
server: LiteSpeed
vary: User-Agent
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
Type Name Value Class TTL
A rekiz.ru 185.22.155.51 IN 14396
NS rekiz.ru ns1.justhost.ru IN 14400
NS rekiz.ru ns2.justhost.ru IN 14400
MX rekiz.ru mail.rekiz.ru IN 14400
TXT rekiz.ru v=spf1 a mx ip4:46.17.40.9 ~all IN 14400
TXT rekiz.ru yandex-verification: 441e4d839d80b073 IN 14400
AAAA rekiz.ru 2a00:b700::12 IN 14320

О нас

Контактная информация

Подписывайтесь на нас

Copyright 2016
Языки | English