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

Similar Ranking

31
ТЕХНО SHIFT – РЕМОНТ НОУТБУКОВ ПК И СМАРТФОНОВ
kevin-seoshnik.ru
31
DOUGHNUT LOUNGE | SAVOR THE FLAVOR, LOVE THE LOUNGE
doughnutlounge.com
31
ᐉ КУПИТЬ САЙТ В 《МАГАЗИНЕ ГОТОВЫХ САЙТОВ TOP-BIT》 ВСЕГО ОТ 1$
top-bit.biz
31
КУПИТЬ АВТОНАПОЛНЯЕМЫЙ САЙТ НА WORDPRESS
wpgra.ru
26
ОБЗОРЫ НОВИНОК ТЕХНИКИ -
eurotehnik.ru
26
БЕСПЛАТНЫЕ СКРИПТЫ. КАТАЛОГ СКРИПТОВ ДЛЯ САЙТА. СОЗДАНИЕ САЙТОВ.
directoryweb.ru
26
ОНЛАЙН ГЕНЕРАТОР ПАРОЛЕЙ
sitest.tk

Latest Sites

26
ОБЗОРЫ НОВИНОК ТЕХНИКИ -
eurotehnik.ru
31
ТЕХНО SHIFT – РЕМОНТ НОУТБУКОВ ПК И СМАРТФОНОВ
kevin-seoshnik.ru
31
DOUGHNUT LOUNGE | SAVOR THE FLAVOR, LOVE THE LOUNGE
doughnutlounge.com
1

31 doughnutlounge.com Last Updated: 7 days

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

Desktop

Mobile

Performance Desktop Score 87%
Best Practices Desktop Score 74%
SEO Desktop Score 100%
Performance Mobile Score 66%
Best Practices Mobile Score 75%
SEO Mobile Score 100%
Page Authority Authority 0%
Авторитет домена Авторитет домена 0%
Moz Rank 0.0/10
Показатель отказов Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 51 Characters
DOUGHNUT LOUNGE | SAVOR THE FLAVOR, LOVE THE LOUNGE
Meta Description 163 Characters
Doughnut Lounge, your ultimate destination for all things donuts! Dive into our universe of deliciousness, donut history, unique recipes, and more. Donut miss out!
Effective URL 26 Characters
https://doughnutlounge.com
Excerpt Page content
Doughnut Lounge | Savor The Flavor, Love The Lounge Skip to content Menu ...
Google Preview Your look like this in google search result
DOUGHNUT LOUNGE | SAVOR THE FLAVOR, LOVE THE LOUNGE
https://doughnutlounge.com
Doughnut Lounge, your ultimate destination for all things donuts! Dive into our universe of deliciousness, donut history, unique recipes, and more. Do
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~693.85 KB
Code Size: ~541.35 KB
Text Size: ~152.49 KB Ratio: 21.98%

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
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Improve image delivery Est savings of 77 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Properly size images Est savings of 87 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources Est 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
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Legacy JavaScript Est savings of 8 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Avoid an excessive DOM size 3,454 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)
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads Total size was 814 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid serving legacy JavaScript to modern browsers Est savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Largest Contentful Paint element 1,820 ms
This is the largest contentful element painted within the viewport
Reduce unused JavaScript Est savings of 164 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 14 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
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
Server Backend Latencies 40 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
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize main-thread work 2.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Uses third-party cookies 1 cookie found
Third-party cookies may be blocked in some contexts
Render blocking requests Est savings of 20 ms
Requests are blocking the page's initial render, which may delay LCP
Use efficient cache lifetimes Est savings of 35 KiB
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 1.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Initial server response time was short Root document took 110 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 100 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
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your page
Network Round Trip Times 10 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
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Eliminate render-blocking resources Est 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 7.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 7,910 ms
This is the largest contentful element painted within the viewport
Largest Contentful Paint 7.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 3,459 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)
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Minimize third-party usage Third-party code blocked the main thread for 140 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
Avoids enormous network payloads Total size was 700 KiB
Large network payloads cost users real money and are highly correlated with long load times
Server Backend Latencies 40 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
Avoid serving legacy JavaScript to modern browsers Est savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Document uses legible font sizes 99.96% 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
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Document request latency Est savings of 640 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Total Blocking Time 230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 4.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 14 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
Legacy JavaScript Est savings of 8 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Render blocking requests Est savings of 30 ms
Requests are blocking the page's initial render, which may delay LCP
Network Round Trip Times 10 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 16 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce unused JavaScript Est savings of 164 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Uses third-party cookies 1 cookie found
Third-party cookies may be blocked in some contexts
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
Use efficient cache lifetimes Est savings of 35 KiB
A long cache lifetime can speed up repeat visits to your page

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 
date: Thu, 24 Jul 2025 14:33:22 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
x-powered-by: PHP/8.2.28
last-modified: Thu, 24 Jul 2025 14:25:17 GMT
cache-control: public, max-age=0
expires: Thu, 24 Jul 2025 14:33:23 GMT
content-encoding: gzip
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
server: hcdn
alt-svc: h3=":443"; ma=86400
x-hcdn-request-id: 8ba6be5cbde3e7457d1f2b8c96031869-fra-edge2
x-hcdn-cache-status: DYNAMIC
x-hcdn-upstream-rt: 0.267
Записи DNS Записи ресурсов DNS, связанные с именем хоста
Просмотр записей DNS