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

Your Website Score is


Similar Ranking

84
MySQL Fatal Error
notbig.ru
84
Спорт: футбол, хоккей, баскетбол, теннис, бокс, биатлон, Формула-1 — все новости спорта на Sports.ru
sports.ru
84
DRIVE2.RU
drive2.ru
84
Интернет-издание о высоких технологиях - CNews
cnews.ru
84
Главная страница
r45.fssprus.ru
84
Федеральная служба судебных приставов
fssprus.ru

Latest Sites

6
PLAYMUSIC.RO
playmusic.ro
19
YERKESHSHAKEYEV2015.COM УДАЛЕН - 16:20:45 23.03.20
yerkeshshakeyev2015.com
19
СТАВКИ НА СПОРТ – БУКМЕКЕРСКИЕ КОНТОРЫ. СТАВКИ ОНЛАЙН 2020
betscore.ru
14
КВЕСТ РЕАЛЬНОСТИ В БАЛТИЙСКЕ ОТ BOOMQUEST
boomquest.ru
19
MCHS-YUG.RU УДАЛЕН - 16:20:45 23.03.20
mchs-yug.ru
26
СРОК РЕГИСТРАЦИИ ДОМЕНА ИСТЁК
coolvideos.ru
31
ПРОДАЖА СТРОИТЕЛЬНЫХ И ОТДЕЛОЧНЫХ МАТЕРИАЛОВ | КРОВЛИ, ФАСАДЫ И ВСЕ КОМПЛЕКТУЮЩИЕ МАТЕРИАЛЫ | FINELUX.RU
finelux.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

84 irecommend.ru Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 65%
Best Practices Desktop Score 85%
SEO Desktop Score 90%
Progressive Web App Desktop Score 26%
Performance Mobile Score 33%
Best Practices Mobile Score 85%
SEO Mobile Score 82%
Progressive Web App Mobile Score 29%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 21 Characters
https://irecommend.ru
Google Preview Your look like this in google search result
irecommend.ru
https://irecommend.ru
Robots.txt File No Found
Sitemap.xml File No Found
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: 2008-07-15 / 12 years
Expires on: 2020-07-15 / 2 months 6 days

RU-CENTER-RU ,

Nameservers
ns1.r01.ru.
ns2.r01.ru.
Page Size Code & Text Ratio
Document Size: ~NAN B
Code Size: ~NAN B
Text Size: ~NAN B Ratio: nan%

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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint
Serve images in next-gen formats Potential savings of 29 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
Reduce the impact of third-party code Third-party code blocked the main thread for 540 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 JavaScript Potential savings of 361 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 1.7 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
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Minify JavaScript Potential savings of 2 KB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused CSS Potential savings of 54 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
Defer offscreen images Potential savings of 170 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 78 KB
Serve images that are appropriately-sized to save cellular data and improve load time
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
User Timing marks and measures 34 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Cumulative Layout Shift 0.029
Cumulative Layout Shift measures the movement of visible elements within the viewport
Time to Interactive 3.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 3.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 90 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 9 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
Preload key requests Potential savings of 1,860 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Estimated Input Latency 40 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
Keep request counts low and transfer sizes small 267 requests • 1,512 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads Total size was 1,512 KB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid an excessive DOM size 2,287 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)
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle 2.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).
Minimize main-thread work 2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.0 s
A fast page load over a cellular network ensures a good mobile user experience
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

Mobile

Mobile Screenshot
First CPU Idle 9.8 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).
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint
First Contentful Paint 1.7 s
First Contentful Paint marks the time at which the first text or image is painted
Estimated Input Latency 210 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
Page load is not fast enough on mobile networks Interactive at 13.8 s
A fast page load over a cellular network ensures a good mobile user experience
Document doesn't use legible font sizes 38.83% 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
Speed Index 7.2 s
Speed Index shows how quickly the contents of a page are visibly populated
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
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
Remove unused CSS Potential savings of 67 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
Reduce the impact of third-party code Third-party code blocked the main thread for 2,240 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
Minify JavaScript Potential savings of 2 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Remove unused JavaScript Potential savings of 370 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 4.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Keep request counts low and transfer sizes small 250 requests • 1,434 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Defer offscreen images Potential savings of 229 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Meaningful Paint 4.0 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time 960 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size 2,154 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)
Properly size images Potential savings of 6 KB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Preload key requests Potential savings of 1,260 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Tap targets are not sized appropriately 98% 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 8.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 1,434 KB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests 10 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
Largest Contentful Paint 7.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
User Timing marks and measures 12 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 13.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 3390 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay 670 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve static assets with an efficient cache policy 19 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 29 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

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