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

Your Website Score is

Similar Ranking

87
MySQL Fatal Error
livbook.ru
87
«Life.ru» — информационный портал
life.ru
87
КАНОБУ — САЙТ ПРО СОВРЕМЕННЫЕ РАЗВЛЕЧЕНИЯ
kanobu.ru
87
ФЕЙЕРВЕРКИ КУПИТЬ САЛЮТ В МОСКВЕ НЕДОРОГО МАГАЗИН ПИРОТЕХНИКИ
salut77.ru
87
DEKUZU
dekuzu.com
87
Лучшие публикации за сутки / Хабр
habr.com
87
Открытый каталог торрентов!
vstorrentino.ucoz.com

Latest Sites

19
ОБЪЯВЛЕНИЯ НА IOXI - ДОСКА ОБЪЯВЛЕНИЙ
ioxi.com.ua
41
安福啦-ANFULA | 一个简简单单的安福相册搜索!
anfula.com
19
АЛЮМ ПРОЕКТ
alyumproekt.ru
31
АВТОСЕРВИС «REFRESH-ISTRA»
refresh-istra.ru
22
ᐈ КОМПЬЮТЕРНЫЙ МАСТЕР ДЛЯ НАСЕЛЕНИЯ — С ВЫЕЗДОМ НА ДОМ В МИНСКЕ
compdoc.by
48
ИНТЕРНЕТ-МАГАЗИН САНТЕХНИКИ «ТЕПЛОВОЗ» - ИРКУТСК
teplovoz38.ru
26
НЕДОРОГОЙ ПРИВОРОТ
privorot-nedorogo.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

87 kanobu.ru Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 53%
Best Practices Desktop Score 77%
SEO Desktop Score 100%
Progressive Web App Desktop Score 70%
Performance Mobile Score 17%
Best Practices Mobile Score 77%
SEO Mobile Score 100%
Progressive Web App Mobile Score 71%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Title Tag 41 Characters
КАНОБУ — САЙТ ПРО СОВРЕМЕННЫЕ РАЗВЛЕЧЕНИЯ
Meta Description 151 Characters
Сайт про современные развлечения. Новости игр, кино и сериалов. Рецензии и обзоры игр. Каталог новых и популярных игр. Мнения и рейтинги пользователей.
Effective URL 17 Characters
https://kanobu.ru
Excerpt Page content
Канобу — сайт про современные развлечения КанобуБаза игрПлатформыPCPlayStation 4Xbox OnePlayStation 3Xbox 360Nintendo SwitchВсе платформыЖанрыЭкшенШутерыРолевыеСтратегииПриключенияВсе жанрыИгры месяцаО...
Keywords Cloud Density
вчера16 сегодня11 last6 playstation5 marvel4 игры4 спецпроект3 sony3 интервью3 аксеновым2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
вчера 16
сегодня 11
last 6
playstation 5
marvel 4
игры 4
спецпроект 3
sony 3
интервью 3
аксеновым 2
Google Preview Your look like this in google search result
КАНОБУ — САЙТ ПРО СОВРЕМЕННЫЕ РАЗВЛЕЧЕНИЯ
https://kanobu.ru
Сайт про современные развлечения. Новости игр, кино и сериалов. Рецензии и обзоры игр. Каталог новых и популярных игр. Мнения и рейтинги пользователей
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 51 years
Create on: 2007-05-21 / 13 years
Expires on: 2020-05-21 / 4 months 3 days

RU-CENTER-RU ,

Nameservers
ns1-ng.kanobu.ru.
137.74.93.62
ns2-ng.kanobu.ru.
79.137.42.203
Page Size Code & Text Ratio
Document Size: ~160.39 KB
Code Size: ~94.51 KB
Text Size: ~65.88 KB Ratio: 41.07%

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

Kanobu Kanobu Kanobu

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
Kanobu
Param short_name
Kanobu
Param description
Канобу - сайт про современные развлечения
Param dir
auto
Param lang
en-US
Param display
fullscreen
Param orientation
portrait
Param start_url
/
Param theme_color
#f2f2f2
Param background_color
#fff

Desktop

Desktop Screenshot
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids an excessive DOM size 790 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)
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify JavaScript Potential savings of 229 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Time to Interactive 4.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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
Serve images in next-gen formats Potential savings of 126 KB
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 chaining critical requests 23 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
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Preload key requests Potential savings of 700 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid enormous network payloads Total size was 2,812 KB
Large network payloads cost users real money and are highly correlated with long load times
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 170 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 22.6 s
A fast page load over a cellular network ensures a good mobile user experience
Keep request counts low and transfer sizes small 116 requests • 2,813 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Estimated Input Latency 20 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
Avoid large layout shifts No elements found
These DOM elements contribute most to the CLS of the page.
Remove unused CSS Potential savings of 511 KB
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
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Enable text compression Potential savings of 2 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First CPU Idle 3.4 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
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
Defer offscreen images Potential savings of 57 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused JavaScript Potential savings of 828 KB
Remove unused JavaScript to reduce bytes consumed by network activity
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

Mobile

Mobile Screenshot
Reduce JavaScript execution time 3.2 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 78 requests • 1,652 KB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint 4.5 s
First Meaningful Paint measures when the primary content of a page is visible
First CPU Idle 8.0 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).
Speed Index 7.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint
Minimize third-party usage Third-party code blocked the main thread for 180 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
Remove unused CSS Potential savings of 419 KB
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
Minify JavaScript Potential savings of 53 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Estimated Input Latency 660 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
Enable text compression Potential savings of 2 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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 22 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids enormous network payloads Total size was 1,649 KB
Large network payloads cost users real money and are highly correlated with long load times
Avoids an excessive DOM size 721 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,300 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 4.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 23 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
First Contentful Paint (3G) 9465 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources Potential savings of 240 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 14.5 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 17 KB
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
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
Total Blocking Time 2,410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint 10.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
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
Minimize main-thread work 6.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Page load is not fast enough on mobile networks Interactive at 14.5 s
A fast page load over a cellular network ensures a good mobile user experience
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
Preload key requests Potential savings of 630 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Avoid large layout shifts No elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript Potential savings of 305 KB
Remove unused JavaScript to reduce 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