mos.ru

mos.ru is SSL secured

Free website and domain report on mos.ru

Last Updated: 6th March, 2022 Update Now
Overview

Snoop Summary for mos.ru

This is a free and comprehensive report about mos.ru. Mos.ru is hosted in Russia on a server with an IP address of 212.11.155.166, where the local currency is RUB and Russian is the local language. Our records indicate that mos.ru is owned/operated by GKU goroda Moskvy Moskovskoe gorodskoe agentstvo po telekommunikaciyam. Mos.ru is expected to earn an estimated $27,203 USD per day from advertising revenue. The sale of mos.ru would possibly be worth $19,858,521 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Mos.ru is unbelievably popular with an estimated 2,921,686 daily unique visitors. This report was last updated 6th March, 2022.

About mos.ru

Site Preview: mos.ru mos.ru
Title: Правительство Москвы (Мэрия). Официальный сервер
Description: Общие сведения о мэрии. Телефонный справочник органов исполнительной власти. Нормативные документы. Программы правительства Москвы.
Keywords and Tags: baby capybara, government, military, mos ru, moscow, popular, site for kids, мос ру, парковка
Related Terms: mos, mos burger
Fav Icon:
Age: Over 27 years old
Domain Created: 23rd December, 1996
Domain Updated:
Domain Expires: 31st December, 2022
Review

Snoop Score

5/5 (Perfect!)

Valuation

$19,858,521 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 914
Alexa Reach: 0.0567%
SEMrush Rank (US): 81,475
SEMrush Authority Score: 83
Moz Domain Authority: 89
Moz Page Authority: 64

Rank By Country

Country Alexa Rank
Netherlands Flag Netherlands 215
Russian Federation Flag Russian Federation 28

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 62,784 0
Traffic: 23,232 0
Cost: $596 USD $0 USD
Traffic

Visitors

Daily Visitors: 2,921,686
Monthly Visitors: 88,926,924
Yearly Visitors: 1,066,415,457
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Netherlands Flag Netherlands Daily: 90,572
Monthly: 2,756,735
Yearly: 33,058,879
3.1%
Other Daily: 149,006
Monthly: 4,535,273
Yearly: 54,387,188
5.1%
Russian Federation Flag Russian Federation Daily: 2,682,108
Monthly: 81,634,916
Yearly: 978,969,390
91.8%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $27,203 USD
Monthly Revenue: $827,987 USD
Yearly Revenue: $9,929,256 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Netherlands Flag Netherlands Daily: $3,693 USD
Monthly: $112,394 USD
Yearly: $1,347,830 USD
13.6%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Russian Federation Flag Russian Federation Daily: $23,511 USD
Monthly: $715,593 USD
Yearly: $8,581,426 USD
86.4%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 153,766,341
Referring Domains: 42,536
Referring IPs: 31,648
Mos.ru has 153,766,341 backlinks according to SEMrush. 66% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve mos.ru's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of mos.ru's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://xvideos.fan/
Target: https://dgi.mos.ru/bitrix/rk.php?goto=http%3A%2F%2Fwebmd2ndopinion.com%2F__media__%2Fjs%2Fnetsoltrademark.php%3Fd%3Ds3-us-west-1.amazonaws.com%2Ffree-xnxx%2Fmoyt.html&id=3728

2
Source: https://pornberg.com/
Target: https://dgi.mos.ru/bitrix/rk.php?goto=http%3A%2F%2Fmanuper.com%2F__media__%2Fjs%2Fnetsoltrademark.php%3Fd%3Ds3-us-west-1.amazonaws.com%2Ffree-xnxx%2Fsexephotos.html&id=3728

3
Source: https://pornberg.com/
Target: https://dgi.mos.ru/bitrix/rk.php?goto=http%3A%2F%2Frissnet.us%2F__media__%2Fjs%2Fnetsoltrademark.php%3Fd%3Ds3-us-west-1.amazonaws.com%2Ffree-xnxx%2Forgasme-wanita-jepang-sampe-muncrat.html&id=3728

4
Source: https://pornberg.com/
Target: https://dgi.mos.ru/bitrix/rk.php?goto=http%3A%2F%2Fwww.4bigbearproperties.com%2F__media__%2Fjs%2Fnetsoltrademark.php%3Fd%3Ds3-us-west-1.amazonaws.com%2Ffree-xnxx%2Fimpregnates-mom.html&id=3728

5
Source: https://pornberg.com/
Target: https://dgi.mos.ru/bitrix/rk.php?goto=http%3A%2F%2Fnajib.com%2F__media__%2Fjs%2Fnetsoltrademark.php%3Fd%3D&id=3728&s3-us-west-1.amazonaws.com%2Ffree-xnxx%2Feat-cuming-cock.html

Top Ranking Keywords (US)

1
Keyword: moscow
Ranked Page: https://www.mos.ru/en/

2
Keyword: mos ru
Ranked Page: https://www.mos.ru/en/

3
Keyword: парковка
Ranked Page: https://parking.mos.ru/

4
Keyword: мос ру
Ranked Page: https://www.mos.ru/

5
Keyword: baby capybara
Ranked Page: https://www.mos.ru/en/news/item/24737073/

Domain Analysis

Value Length
Domain: mos.ru 6
Domain Name: mos 3
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time: 0.86 seconds
Load Time Comparison: Faster than 81% of sites

PageSpeed Insights

Avg. (All Categories) 72
Performance 59
Accessibility 92
Best Practices 83
SEO 91
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.mos.ru/
Updated: 6th March, 2022

1.04 seconds
First Contentful Paint (FCP)
89%
6%
5%

0.01 seconds
First Input Delay (FID)
87%
7%
6%

Simulate loading on desktop
59

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mos.ru. This includes details about optimizing page load times which can result in a better user experience.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mos.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mos.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mos.ru should consider minifying JS files.
Reduce unused CSS — Potential savings of 21 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mos.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/css/main.css
26889
21833
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 11 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://evp.mos.ru/rest/footer/v3/ru/2599
13433
11557
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mos.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 49 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
23225
https://www.mos.ru/front/markup/header-footer/js/main.js
11221
https://www.mos.ru/assets/main-page/_next/static/chunks/main-1d3724bd9d8b2450d1d4.js
10029
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
5099
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
63
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
50
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(9).jpg
0
Avoids enormous network payloads — Total size was 2,168 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(9).jpg
319795
https://www.mos.ru/front/markup/header-footer/js/main.js
268631
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
232162
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(9).jpg
174853
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(9).jpg
162143
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223871).jpg
113202
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
94272
https://www.mos.ru/assets/main-page/_next/static/media/service_bg.7a56896fc7170d652e4a07000977ef54.png
83882
https://static3.mos.ru/upload/share/fonts/PT_Serif/PT_Serif_Regular.woff2
79950
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
76514
Uses efficient cache policy on static assets — 1 resource found
Mos.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mos.ru/assets/parable/mosTizer.js
3600000
3500
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mos.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 6 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Next.js-before-hydration
Measure
0
3805.663
Next.js-hydration
Measure
3805.663
130.367
sentry-tracing-init
Mark
3716.778
sentry-tracing-init
Mark
3718.656
beforeRender
Mark
3805.685
afterHydrate
Mark
3936.073
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 63 requests • 2,168 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
63
2220054
Image
22
1224282
Script
21
665373
Font
5
203950
Stylesheet
7
61914
Document
1
48551
Other
7
15984
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 7 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.mos.ru/front/markup/header-footer/js/main.js
3130
323
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
2730
310
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
931
173
Unattributable
196
162
https://www.mos.ru/assets/main-page/_next/static/chunks/webpack-15c7704272610a9fd06c.js
1297
161
https://www.mos.ru/
662
88
Unattributable
3491
51
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mos.ru/
http/1.1
0
378.1270000618
234
0
301
text/html
https://mos.ru/
http/1.1
378.63499997184
1009.9069999997
251
0
301
text/html
https://www.mos.ru/
h2
1010.3270000545
1911.2949999981
48551
194722
200
text/html
Document
https://www.mos.ru/front/markup/header-footer/css/mos_layouts.css
h2
1928.8869999582
2819.5759999799
644
0
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/css/eca122923900ec638a9f.css
h2
1929.3349999934
2680.4600000614
10374
38486
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/css/41aad24e604e2db3a303.css
h2
1929.6040000627
2696.0770000005
14657
85402
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/chunks/webpack-15c7704272610a9fd06c.js
h2
1939.6180000622
2446.7479999876
2803
4659
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/main-1d3724bd9d8b2450d1d4.js
h2
1939.9170000106
2699.2740000132
38608
119807
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
h2
1940.2959999861
2695.3200000571
38996
130675
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/framework-aa3ca43d4cf5591b94ea.js
h2
1940.6169999857
2445.8579999628
1445
1472
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
h2
1940.9849999938
2703.850000049
74829
238002
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/231-7bf8a30faaa0d4d671dd.js
h2
1941.1059999838
2947.6700000232
50528
199290
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/index-b99eacea1697d9f08c61.js
h2
1941.2970000412
2573.4080000548
501
272
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/BUILD-6384.5.prod/_buildManifest.js
h2
1941.4350000443
2445.3280000016
649
571
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/BUILD-6384.5.prod/_ssgManifest.js
h2
1941.6590000037
2573.9690000191
363
77
200
application/javascript
Script
https://www.mos.ru/front/markup/header-footer/css/main.css
h2
1932.0130000124
2560.216999962
26889
92697
200
text/css
Stylesheet
https://www.mos.ru/front/markup/header-footer/media/small-logo.7260e7ff.svg
h2
1941.9210000196
2580.4179999977
968
495
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(9).jpg
h2
1942.1190000139
2946.4310000185
162143
161689
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(9).jpg
h2
1942.2639999539
2948.53100006
174853
174399
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(9).jpg
h2
1942.5380000612
2452.8759999666
319795
319341
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223871).jpg
h2
1942.8609999595
2944.9249999598
113202
112748
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/icons/Covid_icon(2).svg
h2
1942.9849999724
2581.4109999919
4736
8982
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/old_people_icon(1).svg
h2
1943.2340000058
2073.750999989
3241
6499
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/Moscow_Metro(1).svg
h2
1943.3580000186
2453.7380000111
972
1026
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/Stroyka_icon(2).svg
h2
1943.4990000445
2212.0450000511
1196
2458
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/OldMoscowTales.svg
h2
1943.5930000618
2446.3400000241
2045
4182
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
h2
1947.9750000173
2821.9939999981
63502
192081
200
application/javascript
Script
https://www.mos.ru/upload/share/fonts/fonts.css
http/1.1
2613.1199999945
2948.1450000312
343
0
301
text/html
https://static3.mos.ru/upload/share/fonts/fonts.css
h2
2614.1760000028
3120.1310000615
2044
15687
200
text/css
Stylesheet
https://static3.mos.ru/upload/share/fonts/fonts.css
h2
2949.9899999937
3454.8840000061
2044
15687
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
h2
3496.843000059
4507.4739999836
232162
231869
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/img.c5b628d264202b070223.png
h2
3497.5130000385
3629.7920000507
17350
17059
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
h2
3497.9509999976
3630.7710000547
76514
76222
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/decor.5c9faecb6c4a5a7b6d8a18f363b0a9e8.svg
h2
3500.8300000336
3630.4130000062
925
633
200
image/svg+xml
Image
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_Regular.woff
h2
3502.7969999937
4253.573999973
32948
32288
200
font/woff
Font
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_Medium.woff
h2
3503.991000005
4130.5560000474
33136
32476
200
font/woff
Font
https://www.mos.ru/assets/main-page/_next/static/media/Golos_Text_Regular.94ea974b38664183fcd65ae99fdc1ba9.woff2
h2
3504.9519999884
4255.3270000499
24668
24376
200
font/woff2
Font
https://static3.mos.ru/upload/share/fonts/PT_Serif/PT_Serif_Regular.woff2
h2
3505.128000048
4259.3290000223
79950
79288
200
font/woff2
Font
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_DemiBold.woff
h2
3563.2769999793
4129.9679999938
33248
32588
200
font/woff
Font
https://sentry.mos.ru/api/66/envelope/?sentry_key=37fc660b4690451ba24ae9af5610b502&sentry_version=7
3737.3340000631
4248.1929999776
0
0
-1
Fetch
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
h2
3903.8139999611
4509.0110000456
94272
382161
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/css/fb81bc2589fea866584f.css
h2
3905.2030000603
4036.2919999752
5262
23265
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/chunks/266.2037120710a08b07e343.js
h2
3906.2990000239
4037.3390000314
14683
52862
200
application/javascript
Script
https://www.mos.ru/front/markup/header-footer/js/api.js
h2
4009.3310000375
4141.5079999715
3831
8580
200
application/javascript
Script
https://stats.mos.ru/counter.js
h2
4009.6670000348
4390.7009999966
4078
0
403
text/html
Script
https://www.mos.ru/front/markup/header-footer/js/main.js
h2
4019.9019999709
4902.1920000669
268631
982854
200
application/javascript
Script
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4976659%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579359806%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
4114.1539999517
4494.9740000302
4079
7283
403
text/html
Image
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4717364%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579359807%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
4114.3440000014
4496.9259999925
4078
7283
403
text/html
Image
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4967289%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579359807%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
4114.7809999529
4496.1490000132
4077
7283
403
text/html
Image
https://www.mos.ru/assets/main-page/_next/static/media/service_bg.7a56896fc7170d652e4a07000977ef54.png
h2
4117.7080000052
4251.4669999946
83882
83590
200
image/png
Image
https://www.mos.ru/upload/common/default/script_config.js
h2
5547.9840000626
5681.4010000089
1405
3700
200
application/javascript
Script
https://www.mos.ru/shared/acs/core0521.js
h2
5594.0490000648
5933.1810000585
215
0
403
text/html
Script
https://www.mos.ru/assets/parable/mosTizer.js
h2
5642.1910000499
5770.8819999825
3500
6900
200
application/javascript
Script
https://www.mos.ru/api/newsfeed/v4/frontend/json/ru/articles/important
h2
5751.2819999829
5882.098000031
215
77
403
text/html
Fetch
https://www.mos.ru/upload/common/default/poll_banner_config.js
h2
5857.9949999694
5988.1440000609
550
231
200
application/javascript
Script
https://evp.mos.ru/rest/footer/v3/ru/2599
http/1.1
5861.1129999626
7000.0020000152
14258
13433
200
application/json
Fetch
https://www.mos.ru/upload/common/default/tsr_config.json
h2
5861.7300000042
5991.286000004
683
836
200
application/json
Fetch
https://www.mos.ru/front/markup/header-footer/media/apple_ru.04ee2b55.svg
h2
5874.5239999844
6128.9320000215
5211
9499
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/google_ru.815e3fd5.svg
h2
5874.7399999993
6003.7820000434
4875
9715
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/huawei_ru.afc5ed0c.svg
h2
5875.0530000543
6382.9380000243
6933
14146
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/lang-en.f9069aaa.svg
h2
5876.2620000634
6004.3979999609
1045
659
200
image/svg+xml
Image
https://www.mos.ru/upload/common/default/script_config.js
h2
6619.2430000519
6754.00299998
1405
3700
200
application/javascript
Script
https://www.mos.ru/upload/common/default/chat_config.js
h2
6790.2039999608
6918.8710000599
579
354
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1961.306
11.805
1973.98
9.559
2609.985
46.754
2657.921
6.299
2664.261
5.778
2727.72
5.497
3504.075
9.468
3513.561
176.216
3689.823
5.595
3699.362
322.512
4022.281
6.814
4030.383
8.517
4039.77
26.309
4067.633
93.866
4161.539
26.099
4196.373
21.355
4220.228
30.404
4251.568
40.795
4310.741
5.41
4316.193
26.917
4572.663
620.118
5192.817
40.544
5239.081
346.866
5586.012
6.451
5594.4
322.633
5917.077
48.911
5980.454
162.175
6146.501
11.556
6164.511
12.914
6177.689
15.489
6199.607
11.048
6212.293
50.695
6263.915
9.701
6430.182
6.358
6805.966
10.136
7047.099
13.74
7060.857
10.232
7072.884
37.36
7110.322
9.735
8213.624
10.374
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.0 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.141
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 226 KiB
Images can slow down the page's load time. Mos.ru should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(9).jpg
161689
135859
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223871).jpg
112748
96036
Defer offscreen images — Potential savings of 499 KiB
Time to Interactive can be slowed down by resources on the page. Mos.ru should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(9).jpg
319341
319341
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(9).jpg
174399
174399
https://www.mos.ru/front/markup/header-footer/media/huawei_ru.afc5ed0c.svg
6933
6933
https://www.mos.ru/front/markup/header-footer/media/apple_ru.04ee2b55.svg
5211
5211
https://www.mos.ru/front/markup/header-footer/media/google_ru.815e3fd5.svg
4875
4875
Reduce unused JavaScript — Potential savings of 236 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/js/main.js
268631
91810
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
63502
60657
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
94272
49421
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
74829
39408
Serve images in next-gen formats — Potential savings of 643 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
231869
210576.2
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(9).jpg
319341
116542.65
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(9).jpg
174399
79939.7
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(9).jpg
161689
74531.3
https://www.mos.ru/assets/main-page/_next/static/media/service_bg.7a56896fc7170d652e4a07000977ef54.png
83590
60286.65
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
76222
59892.7
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223871).jpg
112748
47575.25
https://www.mos.ru/assets/main-page/_next/static/media/img.c5b628d264202b070223.png
17059
9312.4
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Mos.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mos.ru/
190
https://mos.ru/
150
https://www.mos.ru/
0
Reduce JavaScript execution time — 2.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
887.151
606.889
2.356
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
619.994
542.709
6.293
Unattributable
444.753
281.512
0.252
https://www.mos.ru/front/markup/header-footer/js/main.js
350.727
314.402
16.372
https://www.mos.ru/
255.636
3.359
1.432
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/index-b99eacea1697d9f08c61.js
242.258
239.893
0.14
Minimize main-thread work — 3.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2056.623
Style & Layout
269.475
Other
268.667
Garbage Collection
118.057
Rendering
111.501
Parse HTML & CSS
89.97
Script Parsing & Compilation
45.58

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 490 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 320 ms
Users could experience a delay when interacting with the page.

Other

Reduce initial server response time — Root document took 900 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mos.ru/
901.953
Avoid an excessive DOM size — 2,440 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
2440
Maximum DOM Depth
18
Maximum Child Elements
146
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mos.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mos.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mos.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
Next.js
11.1.3
Preact
10
core-js
core-js-global@3.19.0; core-js-global@3.9.0; core-js-pure@2.6.12; core-js-pure@3.11.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mos.ru/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://sentry.mos.ru/api/66/envelope/?sentry_key=37fc660b4690451ba24ae9af5610b502&sentry_version=7' from origin 'https://www.mos.ru' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.mos.ru/front/markup/header-footer/js/main.js
https://www.mos.ru/front/markup/header-footer/js/main.js.map
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
https://www.mos.ru/front/markup/header-footer/js/template.js.map
https://www.mos.ru/front/markup/header-footer/js/api.js
https://www.mos.ru/front/markup/header-footer/js/api.js.map
https://www.mos.ru/assets/parable/mosTizer.js
https://www.mos.ru/assets/parable/mosTizer.js.map
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mos.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mos.ru. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 64
Performance 22
Accessibility 86
Best Practices 83
SEO 89
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.mos.ru/
Updated: 6th March, 2022

1.36 seconds
First Contentful Paint (FCP)
85%
9%
6%

0.20 seconds
First Input Delay (FID)
64%
19%
17%

Simulate loading on mobile
22

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mos.ru. This includes details about optimizing page load times which can result in a better user experience.

Other

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mos.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mos.ru should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 11 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://evp.mos.ru/rest/footer/v3/ru/2599
13433
11557
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 160 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mos.ru/
162.474
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mos.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(10).jpg
0
Avoids enormous network payloads — Total size was 1,601 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.mos.ru/front/markup/header-footer/js/main.js
268631
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
232162
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
100236
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
94346
https://static3.mos.ru/upload/share/fonts/PT_Serif/PT_Serif_Regular.woff2
79950
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
76514
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
67697
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(10).jpg
65613
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
65054
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
63502
Uses efficient cache policy on static assets — 1 resource found
Mos.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.mos.ru/assets/parable/mosTizer.js
3600000
3500
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mos.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 6 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Next.js-before-hydration
Measure
0
2188.593
Next.js-hydration
Measure
2188.593
145.294
sentry-tracing-init
Mark
2102.186
sentry-tracing-init
Mark
2103.854
beforeRender
Mark
2188.613
afterHydrate
Mark
2333.914
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 61 requests • 1,601 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
61
1639627
Script
20
656718
Image
21
653852
Font
5
203950
Stylesheet
7
60559
Document
1
48551
Other
7
15997
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 20 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
11190
1683
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
6196
934
https://www.mos.ru/front/markup/header-footer/js/main.js
13590
872
https://www.mos.ru/assets/main-page/_next/static/chunks/webpack-15c7704272610a9fd06c.js
5471
643
https://www.mos.ru/front/markup/header-footer/js/main.js
14593
406
Unattributable
15061
255
Unattributable
15380
172
https://www.mos.ru/
2233
168
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
3690
164
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
8340
144
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
4775
132
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
5340
131
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
14462
131
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
4676
99
Unattributable
701
94
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
4590
86
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/index-b99eacea1697d9f08c61.js
6114
82
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
4014
63
Unattributable
3902
59
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
3961
53
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mos.ru/
http/1.1
0
376.59899983555
249
0
301
text/html
https://mos.ru/
http/1.1
376.96200003847
1009.8359999247
236
0
301
text/html
https://www.mos.ru/
h2
1010.2339996956
1171.714999713
48551
194722
200
text/html
Document
https://www.mos.ru/front/markup/header-footer/css/mos_layouts.css
h2
1188.0910000764
1316.5799998678
636
0
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/css/eca122923900ec638a9f.css
h2
1188.5329997167
1320.3329998069
9040
38486
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/css/41aad24e604e2db3a303.css
h2
1189.0859999694
1327.459000051
14644
85402
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/chunks/webpack-15c7704272610a9fd06c.js
h2
1198.4339999035
1333.5710000247
2423
4659
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/main-1d3724bd9d8b2450d1d4.js
h2
1198.9239999093
1332.9320000485
38608
119807
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
h2
1199.2750000209
1342.7099999972
38859
130675
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/framework-aa3ca43d4cf5591b94ea.js
h2
1199.4599997997
1335.6689997017
1064
1472
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
h2
1199.9049996957
1588.7529999018
67697
238002
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/231-7bf8a30faaa0d4d671dd.js
h2
1200.0839998946
1344.302999787
50505
199290
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/index-b99eacea1697d9f08c61.js
h2
1200.3289996646
1580.2380000241
882
272
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/BUILD-6384.5.prod/_buildManifest.js
h2
1200.506999623
1334.3789996579
649
571
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/BUILD-6384.5.prod/_ssgManifest.js
h2
1200.780000072
1334.9889996462
363
77
200
application/javascript
Script
https://www.mos.ru/front/markup/header-footer/css/main.css
h2
1191.3829999976
1325.1799996942
26889
92697
200
text/css
Stylesheet
https://www.mos.ru/front/markup/header-footer/media/small-logo.7260e7ff.svg
h2
1201.1809996329
1333.9109998196
968
495
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(10).jpg
h2
1201.5599999577
1338.0060000345
52553
52101
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(10).jpg
h2
1201.864999719
1339.6349996328
65613
65161
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
h2
1202.0419999026
1338.8899997808
100236
99783
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
h2
1202.2529998794
1456.2829998322
65054
64602
200
image/jpeg
Image
https://www.mos.ru/upload/newsfeed/icons/Covid_icon(2).svg
h2
1202.4109996855
1337.3079998419
4736
8982
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/old_people_icon(1).svg
h2
1202.7289997786
1336.4339997061
3241
6499
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/Moscow_Metro(1).svg
h2
1202.9099999927
1335.3659999557
972
1026
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/Stroyka_icon(2).svg
h2
1203.1079996377
1336.7959996685
1196
2458
200
image/svg+xml
Image
https://www.mos.ru/upload/newsfeed/icons/OldMoscowTales.svg
h2
1203.2669996843
1336.0249996185
2045
4182
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
h2
1206.2749997713
1340.7919998281
63502
192081
200
application/javascript
Script
https://www.mos.ru/upload/share/fonts/fonts.css
http/1.1
1328.9259998128
1581.7809998989
355
0
301
text/html
https://static3.mos.ru/upload/share/fonts/fonts.css
h2
1329.1839999147
1707.1059998125
2044
15687
200
text/css
Stylesheet
https://static3.mos.ru/upload/share/fonts/fonts.css
h2
1582.0359997451
1961.4140000194
2044
15687
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
h2
2002.6419996284
2140.3339998797
232162
231869
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/img.c5b628d264202b070223.png
h2
2003.0699996278
2133.6339996196
17350
17059
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
h2
2003.7650000304
2137.4860000797
76514
76222
200
image/png
Image
https://www.mos.ru/assets/main-page/_next/static/media/decor.5c9faecb6c4a5a7b6d8a18f363b0a9e8.svg
h2
2007.4439998716
2134.5529998653
925
633
200
image/svg+xml
Image
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_Regular.woff
h2
2009.4979996793
2637.78299978
32948
32288
200
font/woff
Font
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_Medium.woff
h2
2009.7509999759
2270.1929998584
33136
32476
200
font/woff
Font
https://www.mos.ru/assets/main-page/_next/static/media/Golos_Text_Regular.94ea974b38664183fcd65ae99fdc1ba9.woff2
h2
2010.1109999232
2139.130000025
24668
24376
200
font/woff2
Font
https://static3.mos.ru/upload/share/fonts/PT_Serif/PT_Serif_Regular.woff2
h2
2010.4199997149
2388.5809998028
79950
79288
200
font/woff2
Font
https://static3.mos.ru/upload/share/fonts/Golos_Text/Golos_Text_DemiBold.woff
h2
2032.7899996191
2161.4270000719
33248
32588
200
font/woff
Font
https://sentry.mos.ru/api/66/envelope/?sentry_key=37fc660b4690451ba24ae9af5610b502&sentry_version=7
2118.9069999382
3574.6589996852
0
0
-1
Fetch
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
h2
2294.8399996385
2446.8689998612
94346
382161
200
application/javascript
Script
https://www.mos.ru/assets/main-page/_next/static/css/fb81bc2589fea866584f.css
h2
2296.3199997321
2426.6009996645
5262
23265
200
text/css
Stylesheet
https://www.mos.ru/assets/main-page/_next/static/chunks/266.2037120710a08b07e343.js
h2
2297.8089996614
2427.4140000343
15031
52862
200
application/javascript
Script
https://www.mos.ru/front/markup/header-footer/js/api.js
h2
2415.5279998668
2545.3160000034
3831
8580
200
application/javascript
Script
https://stats.mos.ru/counter.js
h2
2416.0929997452
4071.5129999444
4078
0
403
text/html
Script
https://www.mos.ru/front/markup/header-footer/js/main.js
h2
2424.4379997253
2571.6069997288
268631
982854
200
application/javascript
Script
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4976659%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579389743%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
2545.9320000373
3580.4240000434
4078
7283
403
text/html
Image
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4717364%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579389744%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
2546.3849999942
3579.4139998034
4077
7283
403
text/html
Image
https://stats.mos.ru/eds.gif?o=%7B%22bannerId%22%3A4967289%2C%22eventType%22%3A%22bannerLoad%22%2C%22eventTime%22%3A1646579389744%2C%22eventSrc%22%3A%22https%3A%2F%2Fwww.mos.ru%2F%22%7D
h2
2547.5939996541
4071.9779999927
4076
7283
403
text/html
Image
https://www.mos.ru/shared/acs/core0521.js
h2
4134.7639998421
4583.8799998164
215
0
403
text/html
Script
https://www.mos.ru/assets/parable/mosTizer.js
h2
4203.6480000243
4333.3429996856
3500
6900
200
application/javascript
Script
https://www.mos.ru/api/newsfeed/v4/frontend/json/ru/articles/important
h2
4341.5009998716
4472.1519998275
215
77
403
text/html
Fetch
https://www.mos.ru/upload/common/default/poll_banner_config.js
h2
4490.7559999265
4621.0519997403
550
231
200
application/javascript
Script
https://evp.mos.ru/rest/footer/v3/ru/2599
http/1.1
4493.8010000624
5625.8519999683
14259
13433
200
application/json
Fetch
https://www.mos.ru/upload/common/default/tsr_config.json
h2
4494.5429996587
4624.3309997953
683
836
200
application/json
Fetch
https://www.mos.ru/front/markup/header-footer/media/apple_ru.04ee2b55.svg
h2
4513.1569998339
4642.3949999735
5211
9499
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/google_ru.815e3fd5.svg
h2
4513.6130000465
4641.8059999123
4875
9715
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/huawei_ru.afc5ed0c.svg
h2
4513.9729999937
4643.1640000083
6925
14146
200
image/svg+xml
Image
https://www.mos.ru/front/markup/header-footer/media/lang-en.f9069aaa.svg
h2
4516.6980000213
4645.5749999732
1045
659
200
image/svg+xml
Image
https://www.mos.ru/upload/common/default/script_config.js
h2
5066.4240000769
5196.3609997183
1405
3700
200
application/javascript
Script
https://www.mos.ru/upload/common/default/chat_config.js
h2
5397.47299999
5529.6049998142
579
354
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1227.88
10.73
1239.514
8.641
1248.466
5.031
1379.545
5.606
2016.762
10.379
2027.157
84.205
2111.772
321.327
2433.44
6.815
2440.542
35.998
2491.53
42.916
2534.493
65.517
2606.642
49.307
2656.71
20.455
2677.221
5.78
2688.466
33.039
2721.537
13.757
2737.95
841.318
3579.378
41.011
3620.404
9.259
3634.443
466.997
4101.63
12.012
4118.282
5.652
4126.185
435.847
4562.168
65.439
4648.291
202.791
4856.837
23.495
4896.684
20.024
4920.763
10.855
4933.484
63.717
4998.253
13.769
5679.327
14.761
5694.906
12.78
5707.743
42.95
5750.996
17.882
7066.415
13.276
7749.653
15.632
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Cumulative Layout Shift — 0.222
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images — Potential savings of 69 KiB
Images can slow down the page's load time. Mos.ru should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
99783
24907
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(10).jpg
65161
16265
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
64602
16125
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(10).jpg
52101
13005
Reduce unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mos.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/css/main.css
26889
23406
https://www.mos.ru/assets/main-page/_next/static/css/41aad24e604e2db3a303.css
14644
11838
Avoid serving legacy JavaScript to modern browsers — Potential savings of 49 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
23225
https://www.mos.ru/front/markup/header-footer/js/main.js
11221
https://www.mos.ru/assets/main-page/_next/static/chunks/main-1d3724bd9d8b2450d1d4.js
10029
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
5103
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
57
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
50

Metrics

First Contentful Paint — 3.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 13.5 s
The time taken for the page to become fully interactive.
Speed Index — 9.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 4,070 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 4.8 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 1,680 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.1 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 1,060 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mos.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.mos.ru/front/markup/header-footer/css/main.css
26889
300
Defer offscreen images — Potential savings of 252 KiB
Time to Interactive can be slowed down by resources on the page. Mos.ru should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
99783
99783
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
76222
76222
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
64602
64602
https://www.mos.ru/front/markup/header-footer/media/huawei_ru.afc5ed0c.svg
6925
6925
https://www.mos.ru/front/markup/header-footer/media/apple_ru.04ee2b55.svg
5211
5211
https://www.mos.ru/front/markup/header-footer/media/google_ru.815e3fd5.svg
4875
4875
Reduce unused JavaScript — Potential savings of 232 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/front/markup/header-footer/js/main.js
268631
91963
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
63502
60657
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
94346
49431
https://www.mos.ru/assets/main-page/_next/static/chunks/786-f2122b56dbcccb47129c.js
67697
35667
Serve images in next-gen formats — Potential savings of 378 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.mos.ru/assets/main-page/_next/static/media/img.e59637ba453a79d12569.png
231869
210576.2
https://www.mos.ru/assets/main-page/_next/static/media/img.817bed958ee0f70e625a.png
76222
59892.7
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
99783
33532.25
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(10).jpg
65161
26757.2
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
64602
25261.3
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(10).jpg
52101
21677.55
https://www.mos.ru/assets/main-page/_next/static/media/img.c5b628d264202b070223.png
17059
9312.4
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Mos.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mos.ru/
630
https://mos.ru/
480
https://www.mos.ru/
0
Avoid an excessive DOM size — 2,439 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
2439
Maximum DOM Depth
18
Maximum Child Elements
146
Reduce JavaScript execution time — 10.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/_app-644b73ef286322472805.js
4338.8
3036.588
9.816
https://www.mos.ru/assets/main-page/_next/static/chunks/199.64213adf97bbf3260226.js
3364.596
2930.88
27.532
https://www.mos.ru/front/markup/header-footer/js/main.js
2695.844
2481.352
77.92
Unattributable
1144.456
594.796
1.164
https://www.mos.ru/assets/main-page/_next/static/chunks/pages/index-b99eacea1697d9f08c61.js
1055.196
1044.388
0.628
https://www.mos.ru/
596.76
11.624
5.42
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
146.756
48.748
15.312
https://www.mos.ru/assets/main-page/_next/static/chunks/main-1d3724bd9d8b2450d1d4.js
105.312
94.856
10.456
Minimize main-thread work — 13.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
10312.304
Other
1024.868
Style & Layout
930.132
Garbage Collection
575.792
Rendering
457.78
Script Parsing & Compilation
193.104
Parse HTML & CSS
153.384
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_avtozapolnenie-na-0603(10).jpg
https://www.mos.ru/upload/newsfeed/newsfeed/glavnayaYstinenkov(10).jpg
https://www.mos.ru/upload/newsfeed/newsfeed/pyls_nalichniki(10).jpg
https://www.mos.ru/upload/newsfeed/newsfeed/GL(223874).jpg
First Contentful Paint (3G) — 7020 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mos.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mos.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Contrast

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mos.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
Next.js
11.1.3
Preact
10
core-js
core-js-global@3.19.0; core-js-global@3.9.0; core-js-pure@2.6.12; core-js-pure@3.11.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mos.ru/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Access to fetch at 'https://sentry.mos.ru/api/66/envelope/?sentry_key=37fc660b4690451ba24ae9af5610b502&sentry_version=7' from origin 'https://www.mos.ru' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.mos.ru/front/markup/header-footer/js/main.js
https://www.mos.ru/front/markup/header-footer/js/main.js.map
https://www.mos.ru/front/markup/header-footer/js/markup_layouts.min.js?
https://www.mos.ru/front/markup/header-footer/js/template.js.map
https://www.mos.ru/front/markup/header-footer/js/api.js
https://www.mos.ru/front/markup/header-footer/js/api.js.map
https://www.mos.ru/assets/parable/mosTizer.js
https://www.mos.ru/assets/parable/mosTizer.js.map
89

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mos.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 65% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
28x18
28x18
30x18
30x18
164x16
164x16
164x16
164x16
164x16
38x18
42x18
42x18
62x18
62x18
88x18
88x18
73x18
63x18
58x18
59x18
78x18
75x18
85x18
102x18
107x18
78x18
82x18
65x18
62x18
89x18
68x18
68x18
50x18
56x18
56x18
89x18
62x18

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
40

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mos.ru. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mos.ru on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 212.11.155.166
Continent: Europe
Country: Russia
Russia Flag
Region:
City:
Longitude: 37.6068
Latitude: 55.7386
Currencies: RUB
Languages: Russian

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization: GKU goroda Moskvy Moskovskoe gorodskoe agentstvo po telekommunikaciyam
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 88/100
WOT Child Safety: 90/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.mos.ru
Issued By: GlobalSign RSA OV SSL CA 2018
Valid From: 25th June, 2019
Valid To: 25th June, 2020
Subject: CN = *.mos.ru
O = Department of Information Technology of Moscow
L = Moscow
S = RU
Hash: c3c75bc1
Issuer: CN = GlobalSign RSA OV SSL CA 2018
O = GlobalSign nv-sa
S = BE
Version: 2
Serial Number: 28640183754124153206804627705
Serial Number (Hex): 5C8A9AD0548CC3001638C0F9
Valid From: 25th June, 2024
Valid To: 25th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:F8:EF:7F:F2:CD:78:67:A8:DE:6F:8F:24:8D:88:F1:87:03:02:B3:EB
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.globalsign.com/gsrsaovsslca2018.crl

Certificate Policies: Policy: 1.3.6.1.4.1.4146.1.20
CPS: https://www.globalsign.com/repository/
Policy: 2.23.140.1.2.2

Authority Information Access: CA Issuers - URI:http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
OCSP - URI:http://ocsp.globalsign.com/gsrsaovsslca2018

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
Timestamp : Jun 25 15:33:51.091 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7E:07:87:54:DE:4C:17:6F:E4:B2:32:2B:
D3:39:8A:79:20:21:24:62:F8:69:8E:59:94:A2:A4:E8:
F5:99:98:47:02:21:00:D9:5D:9A:75:AA:EF:BA:19:66:
DB:BB:C5:A2:3E:6A:E0:36:BB:86:BC:CC:11:8C:4A:13:
5C:71:7E:BF:32:65:C5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Jun 25 15:33:51.180 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:45:48:53:A9:1B:8B:7A:F1:9E:52:D2:97:
12:53:E5:30:80:C5:53:2B:12:80:BE:0F:FA:AE:42:6F:
00:5A:EB:F1:02:21:00:F0:C3:84:6D:3E:98:FD:65:29:
17:AF:B6:4B:48:9B:BC:9A:AA:9B:9A:7D:C5:85:48:C9:
C0:27:72:9E:7D:CE:71
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mos.ru
DNS:*.mos.ru
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mos.ru. 94.79.51.14 IN 300
mos.ru. 212.11.155.166 IN 300
mos.ru. 212.11.155.167 IN 300
mos.ru. 212.11.155.165 IN 300
mos.ru. 94.79.51.12 IN 300
mos.ru. 94.79.51.13 IN 300

NS Records

Host Nameserver Class TTL
mos.ru. ns3.mos.ru. IN 3600
mos.ru. ns4.mos.ru. IN 3600
mos.ru. ns1.mos.ru. IN 3600

SRV Records

Priority Weight Port Target Class TTL
10 50 5061 dit-uc1-exw-e-s2.mos.ru. IN 3600

MX Records

Priority Host Server Class TTL
10 mos.ru. mx01.mos.ru. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
mos.ru. ns1.mos.ru. domains.it.mos.ru. 3600

TXT Records

Host Value Class TTL
mos.ru. ugcfUdGQWPaTZ6LEhvJVXJbo0vnVP/eUSLiVszaOreK9b0JgGQOQqK+GjhjHxBTOWqrTbKIF/ncrGiOG9rUhuw== IN 3600
mos.ru. yandex-verification: IN 3600
mos.ru. google-site-verification=zUOQwgdFfXkRSgu50v_p8uBwYJrY_HNYgESQIkSJmGk IN 3600
mos.ru. v=spf1 IN 3600
mos.ru. MS=ms95580307 IN 3600
mos.ru. google-site-verification=EgkuJTEuiGJDP1C6QIPRfC5WunbBihbxht-jjl6nNHc IN 3600
mos.ru. mailru-verification: IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 11th May, 2020
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, private
Connection: keep-alive
Vary: Accept-Encoding
X-Session-Fingerprint: 3eba1679e5090ad67b17fce1a7ede071
Set-Cookie: *
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff

Whois Lookup

Created: 23rd December, 1996
Changed:
Expires: 31st December, 2022
Registrar: RU-CENTER-RU
Status:
Nameservers: ns1.mos.ru
ns3.mos.ru
ns4.mos.ru
Owner Organization: GKU MOSGORTELEKOM
Full Whois: % By submitting a query to TCI's Whois Service
% you agree to abide by the following terms of use:
% https://www.tcinet.ru/documents/whois.pdf (in Russian)

domain: MOS.RU
nserver: ns1.mos.ru. 185.173.0.100
nserver: ns3.mos.ru. 212.11.159.250
nserver: ns4.mos.ru. 62.112.117.5
state: REGISTERED, DELEGATED, VERIFIED
org: GKU MOSGORTELEKOM
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 1996-12-23T09:49:03Z
paid-till: 2022-12-31T21:00:00Z
free-date: 2023-02-01
source: TCI

Last updated on 2022-03-06T15:06:32Z

Nameservers

Name IP Address
ns1.mos.ru 185.173.0.100
ns3.mos.ru 212.11.159.250
ns4.mos.ru 62.112.117.5
Related

Subdomains

Domain Subdomain
ag
dtu
pgu

Similar Sites

Domain Valuation Snoop Score
0/5
$50,885 USD 3/5
0/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$649 USD
0/5
$6,619 USD 3/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5