Your Website Score is

Similar Ranking

87
.NET |---. CROSS-PLATFORM. OPEN SOURCE.
windows.net
87
CCM - ONLINE COMMUNITY
ccm.net
87
GOOGLE
google.fi
87
東洋経済オンライン | 経済ニュースの新基準
toyokeizai.net
87
店铺浏览-淘宝网
janeeyre.tmall.com
87
COMO CRIAR UM SITE GRÁTIS | DESCUBRA COMO CRIAR UM SITE GRÁTIS - WEBNODE
webnode.com.br
87
WELCOME TO PYTHON.ORG
python.org

Latest Sites

36
CASINO REVIEWS AND GAME BONUSES - JENNYCASINO.COM
jennycasino.com
54
AMAZON.COM
amazon.com
6
LOGIN | POWER OF DREAM
powerofdream.co.id
7
BITMINEROPTIONS
bitmineroptions.com
7
欢迎访问本网站
gtr.com
19
OMEGAPRO FOREX
omegaprofx.com
5
LUXCITI : TIENDA ONLINE DE PRODUCTOS DE PELUQUERÍA, COMPRAS ONLINE ESPAÑA
luxciti.es

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

87 irecommend.ru Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 57%
Best Practices Desktop Score 62%
SEO Desktop Score 90%
Progressive Web App Desktop Score 27%
Performance Mobile Score 27%
Best Practices Mobile Score 62%
SEO Mobile Score 82%
Progressive Web App Mobile Score 30%
Page Authority Authority 55%
Domain Authority Domain Authority 89%
Moz Rank 5.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 34 Characters
IRECOMMEND.RU | ОТЗЫВЫ ПОКУПАТЕЛЕЙ
Meta Description 92 Characters
Отзывы о товарах и услугах, уникальные фото, опыт владельцев! Читайте отзывы реальных людей!
Effective URL 21 Characters
https://irecommend.ru
Excerpt Page content
IRecommend.ru | Отзывы покупателей ...
Meta Keywords 5 Detected
Отзывы косметика техника отели опыт использования
Keywords Cloud Density
фото46 меня25 всем16 когда12 привет11 очень10 крем9 после9 люблю9 всех8
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
фото 46
меня 25
всем 16
когда 12
привет 11
очень 10
крем 9
после 9
люблю 9
всех 8
Google Preview Your look like this in google search result
IRECOMMEND.RU | ОТЗЫВЫ ПОКУПАТЕЛЕЙ
https://irecommend.ru
Отзывы о товарах и услугах, уникальные фото, опыт владельцев! Читайте отзывы реальных людей!
Robots.txt File Detected
http://irecommend.ru/robots.txt
Sitemap.xml File Detected
http://irecommend.ru/sitemap.xml
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-14 / 13 years
Expires on: 2020-07-14 / 6 months 7 days

RU-CENTER-RU ,

Nameservers
ns1.r01.ru.
ns2.r01.ru.
Page Size Code & Text Ratio
Document Size: ~293.78 KB
Code Size: ~214.59 KB
Text Size: ~79.19 KB Ratio: 26.96%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Reduce JavaScript execution time 1.4 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
Defer offscreen images Potential savings of 277 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 48 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.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).
Avoid enormous network payloads Total size was 2,696 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
Avoid an excessive DOM size 2,392 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)
Minify JavaScript Potential savings of 166 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 294 requests • 2,958 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 51 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 5.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 24.0 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS Potential savings of 680 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
Serve images in next-gen formats Potential savings of 133 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
User Timing marks and measures 32 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 470 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 60 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 32 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 390 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
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Mobile

Mobile Screenshot
Reduce the impact of third-party code Third-party code blocked the main thread for 3,810 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
Total Blocking Time 2,910 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 7.6 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
Defer offscreen images Potential savings of 327 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 4 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 8.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 15.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).
Avoids enormous network payloads Total size was 2,637 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 13.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
Avoid an excessive DOM size 2,191 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)
Minify JavaScript Potential savings of 166 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 278 requests • 2,899 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 47 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 720 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 23.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive at 23.9 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 3720 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 280 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
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
Document doesn't use legible font sizes 54.99% 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
Remove unused CSS Potential savings of 692 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
Serve images in next-gen formats Potential savings of 133 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
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
Reduce server response times (TTFB) Root document took 650 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 570 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 32 KB
Optimized images load faster and consume less cellular data

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Server: openresty
Date: Thu, 28 Nov 2019 01:35:14 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Content-Security-Policy: default-src 'self' https://*.googlesyndication.com; script-src 'self' 'unsafe-eval' 'unsafe-inline'  connect.facebook.net www.googletagservices.com yandex.st *.doubleclick.net *.googleadservices.com  *.googlesyndication.com *.criteo.com *.criteo.net vk.com *.vk.com *.imgsmail.ru *.google.com *.google.ru connect.mail.ru *.connect.mail.ru *.ok.ru *.adriver.ru *.r-99.com cdn.mxpnl.com *.doubleclick.net *.google-analytics.com *.googleapis.com *.googleadservices.com *.googletagservices.com *.gstatic.com yandex.ru *.yandex.ru yastatic.net cdnjs.cloudflare.com  *.yandex.net oimenkr.com *.2mdn.net 2mdn.net   *.twitter.com *.google.com.ua *.google.by *.google.cz *.google.kz *.google.de *.google.es js.mamydirect.com  abp.smartadcheck.de *.ampproject.org  *.adfox.ru mc.webvisor.org *.google.ge *.google.ee *.google.me *.google.co.uk *.google.be *.google.no *.google.bg *.google.fr *.google.az *.google.is *.google.lu *.google.in *.google.lv *.google.nl *.google.iq *.google.dk *.google.kg *.google.com.tr *.google.fi *.google.md *.google.me *.google.gr *.google.it *.google.pl *.google.co.il *.google.hu *.google.ae *.google.co.ve *.google.ch *.google.co.uz *.google.co.th *.betweendigital.com yastat.net; object-src 'self' *; style-src 'unsafe-inline' 'unsafe-eval' 'self'  *; img-src 'self' data: blob: * ; media-src 'self' *; frame-src 'self' *.googlesyndication.com *.facebook.com  facebook.com vk.com *.vk.com apis.google.com connect.odnoklassniki.ru *.ok.ru connect.mail.ru accounts.google.com  *.doubleclick.net  *.doubleclick.net  *.youtube.com www.google.com *.criteo.com  *.criteo.net *.gstatic.com yandex.ru *.yandex.ru *.r-99.com oimenkr.com *.oimenkr.com   *.yandexadexchange.net yandexadexchange.net *.2mdn.net 2mdn.net *.twitter.com yastatic.net *.yandex.net *.googletagservices.com *.vimeo.com *.hpmdnetwork.ru ams.creativecdn.com *.betweendigital.com *.archive.org archive.org yastat.net *.adfox.ru; font-src 'self' data: blob: * ; connect-src 'self' *
X-Frame-Options: SameOrigin
Cache-Control: private, max-age=300
X-Varnish: 4006297056 4006296996
age: 0
X-Varnish-Cache: HIT
X-Varnish-Cache_hit_count: 2
Vary: Cookie
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A irecommend.ru 188.40.17.83 IN 5924
NS irecommend.ru ns2.r01.ru IN 5999
NS irecommend.ru ns1.r01.ru IN 5999
MX irecommend.ru alt1.aspmx.l.google.com IN 5999
MX irecommend.ru alt2.aspmx.l.google.com IN 5999
MX irecommend.ru aspmx2.googlemail.com IN 5999
MX irecommend.ru aspmx3.googlemail.com IN 5999
MX irecommend.ru aspmx4.googlemail.com IN 5999
MX irecommend.ru aspmx5.googlemail.com IN 5999
MX irecommend.ru aspmx.l.google.com IN 5999
TXT irecommend.ru mailru-verification: a3c57c0a5668cdeb IN 5999
TXT irecommend.ru yandex-verification: 4fc01d165ce1129c IN 5999
TXT irecommend.ru yandex-verification: dc93153679476dcc IN 5999
TXT irecommend.ru google-site-verification=mc7vyupxjhdgwB_Ueu5IhvZZfMRe6UueoSw4mCRHFJA IN 5999
TXT irecommend.ru v=spf1 a ip4:148.251.0.103 ip4:148.251.0.102 include:_spf.google.com ptr ~all IN 5999
TXT irecommend.ru wmail-verification: 3078b3719a19af18 IN 5999

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome