Your Website Score is

Similar Ranking

89
UCLA
ucla.edu
89
СМОТРЕТЬ ФИЛЬМЫ ОНЛАЙН В ХОРОШЕМ КАЧЕСТВЕ, КИНО И ВИДЕО ФИЛЬМЫ МОЖНО СМОТРЕТЬ У НАС НА САЙТЕ. НЕ МОЖЕТЕ СКАЧАТЬ НОВИНКИ – СМОТРИТЕ ФИЛЬМЫ В ОНЛАЙН КИНОТЕАТРЕ IVI ПРЯМО СЕЙЧАС!
ivi.ru
89
ФЕДЕРАЛЬНОЕ АГЕНТСТВО НОВОСТЕЙ. НОВОСТИ СО ВСЕГО МИРА
riafan.ru
89
THE ADVERTISING PLATFORM FOR THE OPEN INTERNET | CRITEO
criteo.com
89
EL PAPA PIDE PERDÓN POR PERDER LA PACIENCIA CON UNA PEREGRINA EN EL VATICANO
aciprensa.com
89
SNAP--- - THE FASTEST WAY TO SHARE A MOMENT!
snap---.com
89
WE ARE WHAT WE DO | MEETUP
meetup.com

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1

Top Technologies

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

89 mos.ru Last Updated: 11 months

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

Desktop

Mobile

Performance Desktop Score 46%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 24%
Best Practices Mobile Score 62%
SEO Mobile Score 89%
Progressive Web App Mobile Score 33%
Page Authority Authority 62%
Domain Authority Domain Authority 91%
Moz Rank 6.2/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 28 Characters
ОФИЦИАЛЬНЫЙ САЙТ МЭРА МОСКВЫ
Meta Description 171 Characters
Новости о Москве и для Москвы из первых уст. Городские услуги, события и советы по самым актуальным вопросам — всё о столице на одном портале. Официальный сайт Мэра Москвы
Effective URL 18 Characters
https://www.mos.ru
Excerpt Page content
Официальный сайт Мэра Москвы ...
Keywords Cloud Density
дерево5 оплата4 прием4 культура4 проекты3 более3 краудсорсинг3 социальная3 московское3 долголетие3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
дерево 5
оплата 4
прием 4
культура 4
проекты 3
более 3
краудсорсинг 3
социальная 3
московское 3
долголетие 3
Google Preview Your look like this in google search result
ОФИЦИАЛЬНЫЙ САЙТ МЭРА МОСКВЫ
https://www.mos.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: 1996-12-23 / 24 years
Expires on: 2019-12-31 / 10 months 3 days

RU-CENTER-RU ,

Nameservers
ns1.mos.ru.
185.173.0.100
ns3.mos.ru.
62.112.117.5
ns4.mos.ru.
37.230.149.210
Page Size Code & Text Ratio
Document Size: ~59.31 KB
Code Size: ~32.63 KB
Text Size: ~26.69 KB Ratio: 44.99%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
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 31.8 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 100 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 43 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 622 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 2,449 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 450 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 210 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 48 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 330 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 990 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.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 167 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 121 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.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 4,411 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.9 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.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 8 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 an excessive DOM size 795 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)
Preload key requests Potential savings of 2,180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 188 requests • 4,411 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 61 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 390 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 7.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Mobile

Mobile Screenshot
Avoid enormous network payloads Total size was 4,442 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 19.2 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
Avoid chaining critical requests 7 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 an excessive DOM size 706 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)
Preload key requests Potential savings of 15,930 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 6.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 166 requests • 4,442 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 42 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 950 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 27.7 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 27.7 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 540 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 Contentful Paint (3G) 3660 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 60% 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 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
Remove unused CSS Potential savings of 46 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 729 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 3,075 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 180 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 800 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 48 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 2,580 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 6,790 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 14.3 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 127 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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
Speed Index 9.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 21.2 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 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
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Date: Tue, 26 Nov 2019 15:21:20 GMT
Cache-Control: no-cache, private
X-Session-Fingerprint: f3220f56060b22bf3d84634b853af3e8
X-Session-Fingerprint: f3220f56060b22bf3d84634b853af3e8
Set-Cookie: session-cookie=15dabf984968900d1701e223beb261f5f179496de55b769b8f5703321036d584d3f79eb35064237763a1162ed8e432bd; Max-Age=86400; Path=/; HttpOnly
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome