Google.ru - SEO Checker - Обзор веб-сайта

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

Similar Ranking

GOOGLE

google.ru

MAIL.RU: ПОЧТА, ПОИСК В ИНТЕРНЕТЕ, НОВОСТИ, ИГРЫ

mail.ru

YOUTUBE

youtube.com

СЕРВИС РАЗДАЧИ БОНУСОВ WEBMONEY

bonuswm.org

ИГРА В ИНВЕСТИЦИИ ДЛЯ НОВИЧКОВ НА ПРИМЕРЕ ETF FINEX | WORDIK.RU

wordik.ru

НОВОСТИ СЕГОДНЯ

nrus.info

Latest Sites

l-53.ru

georitual.ge

БЛОГ О КОМИКСАХ

rid-magaz.ru

graffshumsky.ru

acord.click

ОБЗОРЫ НОВИНОК ТЕХНИКИ -

eurotehnik.ru

ТЕХНО SHIFT – РЕМОНТ НОУТБУКОВ ПК И СМАРТФОНОВ

kevin-seoshnik.ru

61 google.ru Last Updated: 4 years

Success 47% of passed verification steps

Warning 23% of total warning

Errors 30% of total errors, require fast action

Mobile

Performance Desktop Score 100%

Best Practices Desktop Score 92%

SEO Desktop Score 82%

PWA Desktop Score 22%

Performance Mobile Score 77%

Best Practices Mobile Score 85%

SEO Mobile Score 85%

PWA Mobile Score 50%

Page Authority Authority 0%

Авторитет домена Авторитет домена 0%

Moz Rank 0.0/10

Показатель отказов Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 6 Characters

GOOGLE

Meta Description 0 Characters

NO DATA

Effective URL 20 Characters

http://www.google.ru

Excerpt Page content

Google ПочтаКартинкиВойти Удалить Пожаловаться на неприемлемые подсказки Сервисы Google доступны на разных языках: English РоссияВсё о GoogleРекламаДля бизнеса Как работает Google Поиск Нулевой баланс выбросов углеки...

Keywords Cloud Density

google5 поиск3 настройки2 поиска2 откл1 ваши1 данные1 поиске1 история1 справке1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
google	5
поиск	3
настройки	2
поиска	2
откл	1
ваши	1
данные	1
поиске	1
история	1
справке	1

Google Preview Your look like this in google search result

GOOGLE

http://www.google.ru

Robots.txt File Detected

http://google.ru/robots.txt

Sitemap.xml File Detected

http://google.ru/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~115.2 KB

Code Size: ~111.41 KB

Text Size: ~3.79 KB Ratio: 3.29%

Estimation Traffic and Earnings

1,309,451

Unique Visits

Daily

2,422,484

Pages Views

Daily

$4,674

Income

Daily

36,664,628

Unique Visits

Monthly

69,040,794

Pages Views

Monthly

$116,850

Income

Monthly

424,262,124

Unique Visits

Yearly

813,954,624

Pages Views

Yearly

$1,233,936

Income

Yearly

Desktop

Time to Interactive 1.2 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Reduce unused JavaScript Potential savings of 206 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

Max Potential First Input Delay 80 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Avoid non-composited animations 1 animated element found

Animations which are not composited can be janky and increase CLS

Keep request counts low and transfer sizes small 26 requests • 521 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

User Timing marks and measures 6 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Initial server response time was short Root document took 80 ms

Keep the server response time for the main document short because all other requests depend on it

Speed Index 0.5 s

Speed Index shows how quickly the contents of a page are visibly populated

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

Avoids enormous network payloads Total size was 521 KiB

Large network payloads cost users real money and are highly correlated with long load times

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

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

Largest Contentful Paint 0.7 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Properly size images Potential savings of 9 KiB

Serve images that are appropriately-sized to save cellular data and improve load time

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 0.5 s

First Contentful Paint marks the time at which the first text or image is painted

Avoids an excessive DOM size 230 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 large layout shifts 3 elements found

These DOM elements contribute most to the CLS of the page.

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

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

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

Uses efficient cache policy on static assets 0 resources found

A long cache lifetime can speed up repeat visits to your page

Avoid chaining critical requests 1 chain 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

Total Blocking Time 30 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

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

Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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 multiple page redirects Potential savings of 190 ms

Redirects introduce additional delays before the page can be loaded

Cumulative Layout Shift 0.012

Cumulative Layout Shift measures the movement of visible elements within the viewport

First Meaningful Paint 0.5 s

First Meaningful Paint measures when the primary content of a page is visible

Mobile

Minimizes main-thread work 1.6 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 20 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

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

JavaScript execution time 1.1 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Keep request counts low and transfer sizes small 36 requests • 581 KiB

To set budgets for the quantity and size of page resources, add a budget.json file

Does not use HTTPS 1 insecure request found

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

First Contentful Paint (3G) 4590 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Uses efficient cache policy on static assets 0 resources found

A long cache lifetime can speed up repeat visits to your page

Avoid large layout shifts 1 element found

These DOM elements contribute most to the CLS of the page.

Largest Contentful Paint 2.6 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Avoid non-composited animations 1 animated element found

Animations which are not composited can be janky and increase CLS

Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB

Total Blocking Time 560 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Avoids enormous network payloads Total size was 581 KiB

Large network payloads cost users real money and are highly correlated with long load times

Reduce unused JavaScript Potential savings of 199 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

First Meaningful Paint 2.3 s

First Meaningful Paint measures when the primary content of a page is visible

Avoid chaining critical requests 4 chains found

Tap targets are sized appropriately 100% 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

Avoids an excessive DOM size 267 elements

Cumulative Layout Shift 0.045

Cumulative Layout Shift measures the movement of visible elements within the viewport

First Contentful Paint 2.3 s

First Contentful Paint marks the time at which the first text or image is painted

Max Potential First Input Delay 380 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 80 ms

Keep the server response time for the main document short because all other requests depend on it

Defer offscreen images Potential savings of 5 KiB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

User Timing marks and measures 8 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Time to Interactive 5.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Speed Index 2.3 s

Speed Index shows how quickly the contents of a page are visibly populated

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 multiple page redirects Potential savings of 630 ms

Redirects introduce additional delays before the page can be loaded

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

Speed And Optimization Tips

Скорость веб-сайта оказывает огромное влияние на производительность, влияя на пользовательский опыт, коэффициенты конверсии и даже рейтинг. Уменьшая время загрузки страницы, пользователи с меньшей вероятностью будут отвлекаться, а поисковые системы с

Title сайта

Предупреждение! Ваш заголовок не оптимизирован

Description сайта

Предупреждение! Ваше описание не оптимизировано

Robots.txt

Поздравляю! На вашем сайте есть файл robots.txt

Sitemap.xml

Поздравляю! Мы нашли файл карты сайта для вашего сайта

SSL безопасный

Поздравляю! Ваш сайт поддерживает HTTPS

Заголовки

Предупреждение! На вашей странице нет заголовков H1 и H2. Заголовки H1 и H2 помогают указать поисковым системам важные темы вашей страницы.

Черный список

Поздравляю! Ваш сайт не занесен в черный список

Валидатор W3C

Поздравляю! На вашем сайте нет ошибок W3C

Ускоренные мобильные страницы (AMP)

Предупреждение! У вашего сайта нет AMP-версии

Авторитет домена

Предупреждение! Авторитет домена вашего сайта медленный. Хорошо иметь авторитет домена больше 25.

GZIP Сжатие

Предупреждение! Ваш сайт не сжат, это может замедлить реакцию посетителей.

Favicon

Предупреждение! На вашем сайте нет значка favicon

Неработающие ссылки

Поздравляю! У вас нет битых ссылок Просмотр ссылок

First 10 Links	Отношение	HTTP статус
Картинки	Внутренняя ссылка	200
https://www.google.ru/intl/ru/about/products	Внутренняя ссылка	301
Войти	Внутренняя ссылка	200
English	Внутренняя ссылка	302
Реклама	Внутренняя ссылка	301
Для бизнеса	Внутренняя ссылка	200
Настройки поиска	Внутренняя ссылка	200
Расширенный поиск	Внутренняя ссылка	301
Ваши данные в Поиске	Внутренняя ссылка	301
История поиска	Внутренняя ссылка	301

Alexa Rank

120

Global Rank

8

Russia

Traffic

Поиск

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

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере.

HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Date: Mon, 20 Dec 2021 17:34:50 GMT
Server: gws
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Transfer-Encoding: chunked
Expires: Mon, 20 Dec 2021 17:34:50 GMT
Cache-Control: private
Set-Cookie: 1P_JAR=2021-12-20-17; expires=Wed, 19-Jan-2022 17:34:50 GMT; path=/; domain=.google.ru; Secure

Записи DNS Записи ресурсов DNS, связанные с именем хоста

Просмотр записей DNS

Type	Name	Value	Class	TTL
A	google.ru	64.233.161.94	IN	300
NS	google.ru	ns3.google.com	IN	21600
NS	google.ru	ns1.google.com	IN	21600
NS	google.ru	ns2.google.com	IN	21600
NS	google.ru	ns4.google.com	IN	21600
MX	google.ru	smtp.google.com	IN	300
TXT	google.ru	v=spf1 -all	IN	300
AAAA	google.ru	2a00:1450:4010:c01::5e	IN	294

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

Similar Ranking

Latest Sites

61 google.ru Last Updated: 4 years

Desktop

Mobile

Estimation Traffic and Earnings

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

120

8

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

О нас

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

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