Разместите свои услуги бесплатно
Техническая поддержка
Помогите рублём проекту

Your Website Score is

Similar Ranking

14
Школы Алматы
alschool.kz
14
Анти ДПС - сайт для тех кто хочет посмотреть много интересного из жизни дпс
antidps.ru
14
Туристическая фирма "Авеню" г. Тверь
avenutver.ru
14
Дневники Делены « Самый крупный сайт поклонников пейринга
delenadiaries.com
14
ДОМЕН НЕ ПРИЛИНКОВАН НИ К ОДНОЙ ИЗ ДИРЕКТОРИЙ НА СЕРВЕРЕ!
fifaua.com
14
Доменное имя временно заблокировано.
interesno-tyt.ru
14
Mega Arena
megaarena.net

Latest Sites

36
ТЕЛЕКОМ ЖИЗНЬ - ЧЕСТНЫЕ НОВОСТИ О СОБЫТИЯХ В МИРЕ ТЕЛЕКОММУНИКАЦИЙ
telecomlife.ru
14
ПРОФЕССИОНАЛЬНАЯ КОСМЕТИКА В МОСКВЕ — КУПИТЬ НЕДОРОГО В ИНТЕРНЕТ-МАГАЗИНЕ HIHAIR.RU | САЙТ ДЛЯ ПАРИКМАХЕРОВ | ПРОФЕССИОНАЛЬНАЯ ДЕКОРАТИВНАЯ КОСМЕТИКА ДЛЯ ЛИЦА
hihair.ru
19
КУПИТЬ КОНДИЦИОНЕР С УСТАНОВКОЙ. КЛИМАТИЧЕСКАЯ ТЕХНИКА И ОБРУДОВАНИЕ -МАГАЗИН LENKLIMAT В СПБ
lenklimat.ru
19
ПАРФЮМ В САМАРЕ. КУПИТЬ ДУХИ ОРИГИНАЛ НЕДОРОГО НА MERCIPARFUM.RU
merciparfum.ru
14
ИНТЕРНЕТ-МАГАЗИН ФУТБОЛЬНОЙ ЭКИПИРОВКИ FOOTBALL MANIA | ФУТБОЛЬНЫЙ ЭКИПИРОВОЧНЫЙ ЦЕНТР
football-mania.ru
19
--- Х ОФИЦИАЛЬНЫЙ САЙТ ЗЕРКАЛО
casin0-x.com
19
ШКОЛА ОРАТОРСКОГО ИСКУССТВА "ТРИБУНА"
tribuna-orator.ru

Top Technologies

Nginx
Web Servers
Google Font API
Font Scripts
WordPress
CMS
Font Awesome
Font Scripts
Liveinternet
Analytics
Twitter Bootstrap
Web Frameworks
Apache
Web Servers
Google Tag Manager
Tag Managers

14 myzbs.ru Last Updated: 1 month

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

Desktop

Mobile

Performance Desktop Score 87%
Best Practices Desktop Score 79%
SEO Desktop Score 75%
Progressive Web App Desktop Score 41%
Performance Mobile Score 59%
Best Practices Mobile Score 79%
SEO Mobile Score 76%
Progressive Web App Mobile Score 43%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 15 Characters
http://myzbs.ru
Excerpt Page content
Skip to content MyZBS.ru Конструктор чат-бото...
Keywords Cloud Density
прячутся2 суперпродукты2 холодильнике2 главная2 skip1 заработка1 eggnews1 comment1 admin1 author1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
прячутся 2
суперпродукты 2
холодильнике 2
главная 2
skip 1
заработка 1
eggnews 1
comment 1
admin 1
author 1
Google Preview Your look like this in google search result
myzbs.ru
http://myzbs.ru
Skip to content MyZBS.ru Конструктор чат-бото...
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~26.82 KB
Code Size: ~18.25 KB
Text Size: ~8.57 KB Ratio: 31.97%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Properly size images Potential savings of 649 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid chaining critical requests 25 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 serving legacy JavaScript to modern browsers Potential savings of 0 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
Eliminate render-blocking resources Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint 0.9 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
Keep request counts low and transfer sizes small 48 requests • 1,265 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce initial server response time Root document took 610 ms
Keep the server response time for the main document short because all other requests depend on it
Minimizes main-thread work 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.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Time to Interactive 1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 549 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Minify CSS Potential savings of 7 KiB
Minifying CSS files can reduce network payload sizes
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused JavaScript Potential savings of 154 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids an excessive DOM size 142 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.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 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
Remove unused CSS Potential savings of 32 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
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 static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS 37 insecure requests 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 servedover 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
Cumulative Layout Shift 0.019
Cumulative Layout Shift measures the movement of visible elements within the viewport
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First CPU Idle 0.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
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 1,265 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Mobile

Mobile Screenshot
Initial server response time was short Root document took 460 ms
Keep the server response time for the main document short because all other requests depend on it
Tap targets are not sized appropriately 64% 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 142 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 5 elements found
These DOM elements contribute most to the CLS of the page.
Document uses legible font sizes 96.39% 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.077
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index 6.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Does not use HTTPS 37 insecure requests 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 servedover 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
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
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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
Minify CSS Potential savings of 7 KiB
Minifying CSS files can reduce network payload sizes
Estimated Input Latency 30 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 48 requests • 1,265 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid chaining critical requests 25 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 1,265 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 9.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First CPU Idle 5.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Serve images in next-gen formats Potential savings of 549 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Remove unused JavaScript Potential savings of 155 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Minimize third-party usage Third-party code blocked the main thread for 30 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
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Properly size images Potential savings of 486 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources Potential savings of 1,920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimizes main-thread work 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
JavaScript execution time 1.0 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
Preload key requests Potential savings of 120 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Total Blocking Time 220 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay 240 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint (3G) 6390 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Remove unused CSS Potential savings of 33 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login

Comments