gov.ru

gov.ru may not be SSL secured

Free website and domain report on gov.ru

Last Updated: 22nd May, 2022 Update Now
Overview

Snoop Summary for gov.ru

This is a free and comprehensive report about gov.ru. Gov.ru is hosted in Moscow, Moscow in Russia on a server with an IP address of 95.173.128.90, where RUB is the local currency and the local language is Russian. Our records indicate that gov.ru is owned/operated by Spetssvyaz FSO RF. Gov.ru has the potential to be earning an estimated $5 USD per day from advertising revenue. If gov.ru was to be sold it would possibly be worth $3,329 USD (based on the daily revenue potential of the website over a 24 month period). Gov.ru is quite popular with an estimated 1,595 daily unique visitors. This report was last updated 22nd May, 2022.

About gov.ru

Site Preview: gov.ru gov.ru
Title: Официальная Россия
Description: Russian Government official information, official documents, draft laws, îôèöèàëüíûå èíôîðìàöèîííûå èñòî÷íèêè îðãàíîâ ãîñóäàðñòâåííîé âëàñòè Ðîññèéñêîé Ôåäåðàöèè, îôèöèàëüíûå äîêóìåíòû, çàêîíîäàòåëüíûå àêòû
Keywords and Tags: decree act kremlin moscow administration president ministry department Ðîññèÿ Ìîñêâà Êðåìëü ïðàâèòåëüñòâî àäìèíèñòðàöèÿ ïðåçèäåíò Ïðåçèäåíò ïàðëàìåíò ìèíèñòåðñòâà âåäîìñòâà îâîñòè çàêîíîïðîåêò çàêîíîïðîåêòû çàêîí çàêîíû óêàç óêàçû, government, military, official news, russia, russian government
Related Terms: draft, ieee, ieee citation, ieee xplore
Fav Icon:
Age: Over 26 years old
Domain Created: 10th July, 1997
Domain Updated:
Domain Expires: 31st July, 2022
Review

Snoop Score

2/5

Valuation

$3,329 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 502,323
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,595
Monthly Visitors: 48,558
Yearly Visitors: 582,305
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $138 USD
Yearly Revenue: $1,660 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

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

Page Speed Analysis

Average Load Time: 3.57 seconds
Load Time Comparison: Faster than 30% of sites

PageSpeed Insights

Avg. (All Categories) 61
Performance 96
Accessibility 54
Best Practices 75
SEO 82
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://gov.ru/
Updated: 22nd May, 2022

0.54 seconds
First Contentful Paint (FCP)
96%
2%
2%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.3 s
The time taken for the page to become fully interactive.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.3 s
The time taken for the primary content of the page to be rendered.
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://gov.ru/
http/1.1
0
374.49900002684
2797
9605
200
text/html
Document
http://gov.ru/styles_ru.css
http/1.1
387.03600002918
696.9430000172
1265
987
200
text/css
Stylesheet
http://gov.ru/main/img/blank.gif
http/1.1
387.3930000118
696.29000005079
320
43
200
image/gif
Image
http://gov.ru/main/img/gerbrf3.gif
http/1.1
390.31600003364
757.19300005585
3479
3199
200
image/gif
Image
http://gov.ru/main/img/or2.gif
http/1.1
390.44400001876
637.41600001231
7773
7492
200
image/gif
Image
http://gov.ru/main/img/flagrf3.gif
http/1.1
390.59200003976
703.17900000373
746
467
200
image/gif
Image
http://gov.ru/main/img/sogv1.gif
http/1.1
390.76700003352
756.90600002417
1732
1452
200
image/gif
Image
http://gov.ru/main/img/polosa2_1.gif
http/1.1
391.10200002324
702.04500004184
321
44
200
image/gif
Image
http://gov.ru/main/img/english.gif
http/1.1
391.31500001531
702.39900000161
452
174
200
image/gif
Image
http://gov.ru/main/img/kn_sh1.jpg
http/1.1
391.6100000497
758.06600000942
4370
4089
200
image/jpeg
Image
http://gov.ru/main/img/kn_foiv.jpg
http/1.1
391.88300003298
856.28200002247
3861
3580
200
image/jpeg
Image
http://gov.ru/main/img/kn_fsrf.jpg
http/1.1
392.04200002132
773.83200003533
4395
4113
200
image/jpeg
Image
http://gov.ru/main/img/kn_svrf.jpg
http/1.1
392.27500004927
852.15800005244
4199
3918
200
image/jpeg
Image
http://gov.ru/main/img/kn-sbrf_ru.jpg
http/1.1
392.37800001865
638.11800000258
26692
26409
200
image/jpeg
Image
http://gov.ru/main/img/kn-cik_ru.jpg
http/1.1
392.68300001277
880.0700000138
31882
31599
200
image/jpeg
Image
http://gov.ru/main/img/kn-ach_ru.jpg
http/1.1
392.82000000821
880.455000035
31101
30818
200
image/jpeg
Image
http://gov.ru/main/img/kn-prok_ru.jpg
http/1.1
393.00600002753
974.02200003853
29610
29327
200
image/jpeg
Image
http://gov.ru/main/img/obm_ru.jpg
http/1.1
393.13500002027
824.30300000124
28843
28560
200
image/jpeg
Image
http://gov.ru/main/img/ROS2.jpg
http/1.1
393.41400004923
999.23800001852
48957
48674
200
image/jpeg
Image
http://gov.ru/main/img/polosa2_2.gif
http/1.1
393.6340000364
718.18000002531
321
44
200
image/gif
Image
http://gov.ru/main/img/isp2.gif
http/1.1
393.78000004217
704.06100002583
977
698
200
image/gif
Image
http://gov.ru/main/img/visitor.gif
http/1.1
394.01100005489
760.16400003573
895
616
200
image/gif
Image
http://gov.ru/main/img/webmaster.gif
http/1.1
394.34200001415
766.55200001551
539
260
200
image/gif
Image
http://gov.ru/main/img/symbols_box.png
http/1.1
699.33900004253
823.61000002129
7127
6846
200
image/png
Image
http://gov.ru/main/img/awards_box.png
http/1.1
699.57700005034
945.40600001346
5116
4835
200
image/png
Image
http://gov.ru/main/img/acts_box.png
http/1.1
699.8560000211
942.68500001635
6016
5735
200
image/png
Image
http://gov.ru/main/img/objects_box.png
http/1.1
700.00000001164
823.25800001854
6558
6277
200
image/png
Image
http://gov.ru/main/img/rsnet_box.png
http/1.1
700.15400002012
892.51300005708
5318
5037
200
image/png
Image
http://gov.ru/main/img/links_box.png
http/1.1
700.34300000407
822.93900003424
4553
4272
200
image/png
Image
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)
415.371
6.09
736.292
17.24
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.

Other

Eliminate render-blocking resources — Potential savings of 60 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gov.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)
http://gov.ru/styles_ru.css
1265
70
Properly size images
Images can slow down the page's load time. Gov.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gov.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gov.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gov.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gov.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 134 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://gov.ru/main/img/ROS2.jpg
48674
24929
http://gov.ru/main/img/kn-cik_ru.jpg
31599
24341
http://gov.ru/main/img/kn-ach_ru.jpg
30818
24306
http://gov.ru/main/img/kn-prok_ru.jpg
29327
22713
http://gov.ru/main/img/obm_ru.jpg
28560
21430
http://gov.ru/main/img/kn-sbrf_ru.jpg
26409
19662
Serve images in next-gen formats — Potential savings of 161 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)
http://gov.ru/main/img/ROS2.jpg
48674
37166.55
http://gov.ru/main/img/kn-cik_ru.jpg
31599
27663.7
http://gov.ru/main/img/kn-ach_ru.jpg
30818
27278.8
http://gov.ru/main/img/kn-prok_ru.jpg
29327
25730.3
http://gov.ru/main/img/obm_ru.jpg
28560
24597.5
http://gov.ru/main/img/kn-sbrf_ru.jpg
26409
22784.65
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
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 380 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)
http://gov.ru/
375.495
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Gov.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gov.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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://gov.ru/main/img/ROS2.jpg
0
Avoids enormous network payloads — Total size was 264 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://gov.ru/main/img/ROS2.jpg
48957
http://gov.ru/main/img/kn-cik_ru.jpg
31882
http://gov.ru/main/img/kn-ach_ru.jpg
31101
http://gov.ru/main/img/kn-prok_ru.jpg
29610
http://gov.ru/main/img/obm_ru.jpg
28843
http://gov.ru/main/img/kn-sbrf_ru.jpg
26692
http://gov.ru/main/img/or2.gif
7773
http://gov.ru/main/img/symbols_box.png
7127
http://gov.ru/main/img/objects_box.png
6558
http://gov.ru/main/img/acts_box.png
6016
Uses efficient cache policy on static assets — 28 resources found
Gov.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)
http://gov.ru/main/img/ROS2.jpg
2592000000
48957
http://gov.ru/main/img/kn-cik_ru.jpg
2592000000
31882
http://gov.ru/main/img/kn-ach_ru.jpg
2592000000
31101
http://gov.ru/main/img/kn-prok_ru.jpg
2592000000
29610
http://gov.ru/main/img/obm_ru.jpg
2592000000
28843
http://gov.ru/main/img/kn-sbrf_ru.jpg
2592000000
26692
http://gov.ru/main/img/or2.gif
2592000000
7773
http://gov.ru/main/img/symbols_box.png
2592000000
7127
http://gov.ru/main/img/objects_box.png
2592000000
6558
http://gov.ru/main/img/acts_box.png
2592000000
6016
http://gov.ru/main/img/rsnet_box.png
2592000000
5318
http://gov.ru/main/img/awards_box.png
2592000000
5116
http://gov.ru/main/img/links_box.png
2592000000
4553
http://gov.ru/main/img/kn_fsrf.jpg
2592000000
4395
http://gov.ru/main/img/kn_sh1.jpg
2592000000
4370
http://gov.ru/main/img/kn_svrf.jpg
2592000000
4199
http://gov.ru/main/img/kn_foiv.jpg
2592000000
3861
http://gov.ru/main/img/gerbrf3.gif
2592000000
3479
http://gov.ru/main/img/sogv1.gif
2592000000
1732
http://gov.ru/styles_ru.css
2592000000
1265
http://gov.ru/main/img/isp2.gif
2592000000
977
http://gov.ru/main/img/visitor.gif
2592000000
895
http://gov.ru/main/img/flagrf3.gif
2592000000
746
http://gov.ru/main/img/webmaster.gif
2592000000
539
http://gov.ru/main/img/english.gif
2592000000
452
http://gov.ru/main/img/polosa2_1.gif
2592000000
321
http://gov.ru/main/img/polosa2_2.gif
2592000000
321
http://gov.ru/main/img/blank.gif
2592000000
320
Avoids an excessive DOM size — 138 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
138
Maximum DOM Depth
11
Maximum Child Elements
11
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gov.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time
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.
Minimizes main-thread work — 0.1 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)
Other
33.593
Style & Layout
14.742
Rendering
10.411
Parse HTML & CSS
4.889
Script Evaluation
4.402
Script Parsing & Compilation
1.042
Garbage Collection
0.764
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 — 29 requests • 264 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
29
270215
Image
27
266153
Document
1
2797
Stylesheet
1
1265
Media
0
0
Font
0
0
Script
0
0
Other
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
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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.

Metrics

Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.

Other

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of gov.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.
`<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 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"]`
Gov.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

Links do not 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.

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.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that gov.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 29 insecure requests 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://gov.ru/
Allowed
http://gov.ru/styles_ru.css
Allowed
http://gov.ru/main/img/blank.gif
Allowed
http://gov.ru/main/img/gerbrf3.gif
Allowed
http://gov.ru/main/img/or2.gif
Allowed
http://gov.ru/main/img/flagrf3.gif
Allowed
http://gov.ru/main/img/sogv1.gif
Allowed
http://gov.ru/main/img/polosa2_1.gif
Allowed
http://gov.ru/main/img/english.gif
Allowed
http://gov.ru/main/img/kn_sh1.jpg
Allowed
http://gov.ru/main/img/kn_foiv.jpg
Allowed
http://gov.ru/main/img/kn_fsrf.jpg
Allowed
http://gov.ru/main/img/kn_svrf.jpg
Allowed
http://gov.ru/main/img/kn-sbrf_ru.jpg
Allowed
http://gov.ru/main/img/kn-cik_ru.jpg
Allowed
http://gov.ru/main/img/kn-ach_ru.jpg
Allowed
http://gov.ru/main/img/kn-prok_ru.jpg
Allowed
http://gov.ru/main/img/obm_ru.jpg
Allowed
http://gov.ru/main/img/ROS2.jpg
Allowed
http://gov.ru/main/img/polosa2_2.gif
Allowed
http://gov.ru/main/img/isp2.gif
Allowed
http://gov.ru/main/img/visitor.gif
Allowed
http://gov.ru/main/img/webmaster.gif
Allowed
http://gov.ru/main/img/symbols_box.png
Allowed
http://gov.ru/main/img/awards_box.png
Allowed
http://gov.ru/main/img/acts_box.png
Allowed
http://gov.ru/main/img/objects_box.png
Allowed
http://gov.ru/main/img/rsnet_box.png
Allowed
http://gov.ru/main/img/links_box.png
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://gov.ru/main/img/polosa2_1.gif
500 x 4
1 x 4
500 x 4
http://gov.ru/main/img/polosa2_2.gif
500 x 4
1 x 4
500 x 4

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
82

SEO

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

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

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.

Content Best Practices

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.
0

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 gov.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.

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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.
Does not provide 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.
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) 59
Performance 95
Accessibility 54
Best Practices 75
SEO 69
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://gov.ru/
Updated: 22nd May, 2022

0.88 seconds
First Contentful Paint (FCP)
92%
4%
4%

0.25 seconds
First Input Delay (FID)
2%
96%
2%

Simulate loading on mobile
95

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 100 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
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://gov.ru/
http/1.1
0
374.58399985917
2804
9605
200
text/html
Document
http://gov.ru/styles_ru.css
http/1.1
390.74599999003
755.82999992184
1265
987
200
text/css
Stylesheet
http://gov.ru/main/img/blank.gif
http/1.1
391.52799989097
761.44000003114
320
43
200
image/gif
Image
http://gov.ru/main/img/gerbrf3.gif
http/1.1
396.21199993417
523.30100000836
3479
3199
200
image/gif
Image
http://gov.ru/main/img/or2.gif
http/1.1
396.63199987262
646.00399998017
7773
7492
200
image/gif
Image
http://gov.ru/main/img/flagrf3.gif
http/1.1
396.83500002138
651.87399997376
746
467
200
image/gif
Image
http://gov.ru/main/img/sogv1.gif
http/1.1
397.24799990654
649.96499987319
1732
1452
200
image/gif
Image
http://gov.ru/main/img/polosa2_1.gif
http/1.1
397.58799993433
527.25699986331
321
44
200
image/gif
Image
http://gov.ru/main/img/english.gif
http/1.1
397.96400000341
714.18999996968
452
174
200
image/gif
Image
http://gov.ru/main/img/kn_sh1.jpg
http/1.1
398.2079999987
649.34600004926
4370
4089
200
image/jpeg
Image
http://gov.ru/main/img/kn_foiv.jpg
http/1.1
398.52100005373
648.98100006394
3861
3580
200
image/jpeg
Image
http://gov.ru/main/img/kn_fsrf.jpg
http/1.1
399.19699984603
651.50799998082
4395
4113
200
image/jpeg
Image
http://gov.ru/main/img/kn_svrf.jpg
http/1.1
399.41099984571
652.22200006247
4199
3918
200
image/jpeg
Image
http://gov.ru/main/img/kn-sbrf_ru.jpg
http/1.1
399.83899984509
772.8740000166
26692
26409
200
image/jpeg
Image
http://gov.ru/main/img/kn-cik_ru.jpg
http/1.1
400.45000007376
771.30899997428
31882
31599
200
image/jpeg
Image
http://gov.ru/main/img/kn-ach_ru.jpg
http/1.1
400.94599989243
649.66899994761
31101
30818
200
image/jpeg
Image
http://gov.ru/main/img/kn-prok_ru.jpg
http/1.1
401.1500000488
768.01300002262
29610
29327
200
image/jpeg
Image
http://gov.ru/main/img/obm_ru.jpg
http/1.1
401.26299997792
770.51299996674
28843
28560
200
image/jpeg
Image
http://gov.ru/main/img/ROS2.jpg
http/1.1
401.64399985224
890.58899995871
48957
48674
200
image/jpeg
Image
http://gov.ru/main/img/polosa2_2.gif
http/1.1
401.99699997902
650.66400007345
321
44
200
image/gif
Image
http://gov.ru/main/img/isp2.gif
http/1.1
402.32699993066
650.2539999783
977
698
200
image/gif
Image
http://gov.ru/main/img/visitor.gif
http/1.1
403.34399999119
768.53100000881
895
616
200
image/gif
Image
http://gov.ru/main/img/webmaster.gif
http/1.1
403.93799985759
652.99399988726
539
260
200
image/gif
Image
http://gov.ru/main/img/symbols_box.png
http/1.1
759.45200002752
882.71300005727
7127
6846
200
image/png
Image
http://gov.ru/main/img/awards_box.png
http/1.1
759.82500007376
883.14300007187
5116
4835
200
image/png
Image
http://gov.ru/main/img/acts_box.png
http/1.1
760.07099985145
949.26999998279
6016
5735
200
image/png
Image
http://gov.ru/main/img/objects_box.png
http/1.1
760.40999987163
883.63699987531
6558
6277
200
image/png
Image
http://gov.ru/main/img/rsnet_box.png
http/1.1
760.80399984494
883.97199986503
5318
5037
200
image/png
Image
http://gov.ru/main/img/links_box.png
http/1.1
761.17799989879
884.5760000404
4553
4272
200
image/png
Image
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)
433.176
10.152
443.928
5.608
450.01
7.884
813.013
15.017
829.629
24.288
855.715
5.319
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.

Other

Eliminate render-blocking resources — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gov.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)
http://gov.ru/styles_ru.css
1265
180
Properly size images
Images can slow down the page's load time. Gov.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gov.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gov.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gov.ru should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gov.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
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 380 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)
http://gov.ru/
375.58
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Gov.ru should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gov.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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://gov.ru/main/img/ROS2.jpg
0
Avoids enormous network payloads — Total size was 264 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://gov.ru/main/img/ROS2.jpg
48957
http://gov.ru/main/img/kn-cik_ru.jpg
31882
http://gov.ru/main/img/kn-ach_ru.jpg
31101
http://gov.ru/main/img/kn-prok_ru.jpg
29610
http://gov.ru/main/img/obm_ru.jpg
28843
http://gov.ru/main/img/kn-sbrf_ru.jpg
26692
http://gov.ru/main/img/or2.gif
7773
http://gov.ru/main/img/symbols_box.png
7127
http://gov.ru/main/img/objects_box.png
6558
http://gov.ru/main/img/acts_box.png
6016
Uses efficient cache policy on static assets — 28 resources found
Gov.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)
http://gov.ru/main/img/ROS2.jpg
2592000000
48957
http://gov.ru/main/img/kn-cik_ru.jpg
2592000000
31882
http://gov.ru/main/img/kn-ach_ru.jpg
2592000000
31101
http://gov.ru/main/img/kn-prok_ru.jpg
2592000000
29610
http://gov.ru/main/img/obm_ru.jpg
2592000000
28843
http://gov.ru/main/img/kn-sbrf_ru.jpg
2592000000
26692
http://gov.ru/main/img/or2.gif
2592000000
7773
http://gov.ru/main/img/symbols_box.png
2592000000
7127
http://gov.ru/main/img/objects_box.png
2592000000
6558
http://gov.ru/main/img/acts_box.png
2592000000
6016
http://gov.ru/main/img/rsnet_box.png
2592000000
5318
http://gov.ru/main/img/awards_box.png
2592000000
5116
http://gov.ru/main/img/links_box.png
2592000000
4553
http://gov.ru/main/img/kn_fsrf.jpg
2592000000
4395
http://gov.ru/main/img/kn_sh1.jpg
2592000000
4370
http://gov.ru/main/img/kn_svrf.jpg
2592000000
4199
http://gov.ru/main/img/kn_foiv.jpg
2592000000
3861
http://gov.ru/main/img/gerbrf3.gif
2592000000
3479
http://gov.ru/main/img/sogv1.gif
2592000000
1732
http://gov.ru/styles_ru.css
2592000000
1265
http://gov.ru/main/img/isp2.gif
2592000000
977
http://gov.ru/main/img/visitor.gif
2592000000
895
http://gov.ru/main/img/flagrf3.gif
2592000000
746
http://gov.ru/main/img/webmaster.gif
2592000000
539
http://gov.ru/main/img/english.gif
2592000000
452
http://gov.ru/main/img/polosa2_1.gif
2592000000
321
http://gov.ru/main/img/polosa2_2.gif
2592000000
321
http://gov.ru/main/img/blank.gif
2592000000
320
Avoids an excessive DOM size — 138 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
138
Maximum DOM Depth
11
Maximum Child Elements
11
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gov.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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)
Unattributable
233.512
14.944
0.772
http://gov.ru/
175.672
8.504
4.3
Minimizes main-thread work — 0.4 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)
Other
259.936
Style & Layout
46.204
Rendering
43.092
Parse HTML & CSS
34.32
Script Evaluation
23.448
Script Parsing & Compilation
5.072
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 — 29 requests • 264 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
29
270222
Image
27
266153
Document
1
2804
Stylesheet
1
1265
Media
0
0
Font
0
0
Script
0
0
Other
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
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 1 long task 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)
Unattributable
733
97
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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.
First Contentful Paint (3G) — 1560 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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.

Metrics

Largest Contentful Paint — 2.9 s
The timing of the largest text or image that is painted.

Other

Efficiently encode images — Potential savings of 134 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://gov.ru/main/img/ROS2.jpg
48674
24929
http://gov.ru/main/img/kn-cik_ru.jpg
31599
24341
http://gov.ru/main/img/kn-ach_ru.jpg
30818
24306
http://gov.ru/main/img/kn-prok_ru.jpg
29327
22713
http://gov.ru/main/img/obm_ru.jpg
28560
21430
http://gov.ru/main/img/kn-sbrf_ru.jpg
26409
19662
Serve images in next-gen formats — Potential savings of 161 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)
http://gov.ru/main/img/ROS2.jpg
48674
37166.55
http://gov.ru/main/img/kn-cik_ru.jpg
31599
27663.7
http://gov.ru/main/img/kn-ach_ru.jpg
30818
27278.8
http://gov.ru/main/img/kn-prok_ru.jpg
29327
25730.3
http://gov.ru/main/img/obm_ru.jpg
28560
24597.5
http://gov.ru/main/img/kn-sbrf_ru.jpg
26409
22784.65

Other

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of gov.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.
`<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 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"]`
Gov.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
Failing Elements

Names and labels

Links do not 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.

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.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that gov.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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 29 insecure requests 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://gov.ru/
Allowed
http://gov.ru/styles_ru.css
Allowed
http://gov.ru/main/img/blank.gif
Allowed
http://gov.ru/main/img/gerbrf3.gif
Allowed
http://gov.ru/main/img/or2.gif
Allowed
http://gov.ru/main/img/flagrf3.gif
Allowed
http://gov.ru/main/img/sogv1.gif
Allowed
http://gov.ru/main/img/polosa2_1.gif
Allowed
http://gov.ru/main/img/english.gif
Allowed
http://gov.ru/main/img/kn_sh1.jpg
Allowed
http://gov.ru/main/img/kn_foiv.jpg
Allowed
http://gov.ru/main/img/kn_fsrf.jpg
Allowed
http://gov.ru/main/img/kn_svrf.jpg
Allowed
http://gov.ru/main/img/kn-sbrf_ru.jpg
Allowed
http://gov.ru/main/img/kn-cik_ru.jpg
Allowed
http://gov.ru/main/img/kn-ach_ru.jpg
Allowed
http://gov.ru/main/img/kn-prok_ru.jpg
Allowed
http://gov.ru/main/img/obm_ru.jpg
Allowed
http://gov.ru/main/img/ROS2.jpg
Allowed
http://gov.ru/main/img/polosa2_2.gif
Allowed
http://gov.ru/main/img/isp2.gif
Allowed
http://gov.ru/main/img/visitor.gif
Allowed
http://gov.ru/main/img/webmaster.gif
Allowed
http://gov.ru/main/img/symbols_box.png
Allowed
http://gov.ru/main/img/awards_box.png
Allowed
http://gov.ru/main/img/acts_box.png
Allowed
http://gov.ru/main/img/objects_box.png
Allowed
http://gov.ru/main/img/rsnet_box.png
Allowed
http://gov.ru/main/img/links_box.png
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://gov.ru/main/img/ROS2.jpg
400 x 200
400 x 200
800 x 400
http://gov.ru/main/img/or2.gif
216 x 68
216 x 68
432 x 136
http://gov.ru/main/img/obm_ru.jpg
110 x 130
110 x 130
220 x 260
http://gov.ru/main/img/kn-sbrf_ru.jpg
108 x 130
108 x 130
216 x 260
http://gov.ru/main/img/kn_foiv.jpg
116 x 116
116 x 116
232 x 232
http://gov.ru/main/img/kn_fsrf.jpg
114 x 116
114 x 116
228 x 232
http://gov.ru/main/img/kn_sh1.jpg
114 x 116
114 x 116
228 x 232
http://gov.ru/main/img/kn_svrf.jpg
112 x 116
112 x 116
224 x 232
http://gov.ru/main/img/kn-ach_ru.jpg
99 x 130
99 x 130
198 x 260
http://gov.ru/main/img/kn-cik_ru.jpg
99 x 130
99 x 130
198 x 260
http://gov.ru/main/img/kn-prok_ru.jpg
99 x 130
99 x 130
198 x 260
http://gov.ru/main/img/sogv1.gif
443 x 12
443 x 12
886 x 24
http://gov.ru/main/img/flagrf3.gif
87 x 59
87 x 59
174 x 118
http://gov.ru/main/img/gerbrf3.gif
59 x 72
59 x 72
118 x 144
http://gov.ru/main/img/polosa2_1.gif
500 x 4
1 x 4
1000 x 8
http://gov.ru/main/img/polosa2_2.gif
500 x 4
1 x 4
1000 x 8
http://gov.ru/main/img/isp2.gif
162 x 12
162 x 12
324 x 24
http://gov.ru/main/img/visitor.gif
155 x 12
155 x 12
310 x 24
http://gov.ru/main/img/webmaster.gif
88 x 12
88 x 12
176 x 24
http://gov.ru/main/img/english.gif
39 x 7
39 x 7
78 x 14

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
69

SEO

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

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

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.
Document doesn't use 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 not 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

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.
0

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 gov.ru. This includes details about web app manifests.

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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.ru on mobile screens.
Does not provide 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.
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: 95.173.128.90
Continent: Europe
Country: Russia
Russia Flag
Region: Moscow
City: Moscow
Longitude: 37.6177
Latitude: 55.7482
Currencies: RUB
Languages: Russian

Web Hosting Provider

Name IP Address
RUSSIAN STATE INTERNET NETWORK
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Spetssvyaz FSO RF
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: Unknown
WOT Rating:
WOT Trustworthiness: 89/100
WOT Child Safety: 92/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
gov.ru. 95.173.128.90 IN 1800

NS Records

Host Nameserver Class TTL
gov.ru. bcl.dns.ripn.net. IN 1800
gov.ru. acl.dns.ripn.net. IN 1800
gov.ru. ns2.gov.ru. IN 1800
gov.ru. ccl.dns.ripn.net. IN 1800
gov.ru. ns.gov.ru. IN 1800

MX Records

Priority Host Server Class TTL
30 gov.ru. mx4.gov.ru. IN 1800
20 gov.ru. mx3.gov.ru. IN 1800

SOA Records

Domain Name Primary NS Responsible Email TTL
gov.ru. ns.gov.ru. ncc.gov.ru. 1800

TXT Records

Host Value Class TTL
gov.ru. v=spf1 IN 1800
gov.ru. RGIN IN 1800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
server: nginx
date: 22nd May, 2022
content-type: text/html
expires: 21st June, 2022
cache-control: max-age=2592000
vary: Accept-Encoding

Whois Lookup

Created: 10th July, 1997
Changed:
Expires: 31st July, 2022
Registrar: CC-RU
Status:
Nameservers: acl.dns.ripn.net
bcl.dns.ripn.net
ccl.dns.ripn.net
ns.gov.ru
ns2.gov.ru
Owner Organization: Special Communications and Information Service of the Federal Guard Service of the Russian Federation (Spetssvyaz FSO RF)
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: GOV.RU
nserver: acl.dns.ripn.net.
nserver: bcl.dns.ripn.net.
nserver: ccl.dns.ripn.net.
nserver: ns2.gov.ru. 95.173.128.80
nserver: ns.gov.ru. 95.173.128.77
state: REGISTERED, DELEGATED, VERIFIED
org: Special Communications and Information Service of the Federal Guard Service of the Russian Federation (Spetssvyaz FSO RF)
registrar: CC-RU
admin-contact: http://www.cctld.ru
created: 1997-07-10T08:07:13Z
paid-till: 2022-07-31T21:00:00Z
free-date: 2022-09-01
source: TCI

Last updated on 2022-05-22T19:06:31Z

Nameservers

Name IP Address
acl.dns.ripn.net 193.232.66.15
bcl.dns.ripn.net 194.85.84.15
ccl.dns.ripn.net 193.232.82.15
ns.gov.ru 95.173.128.77
ns2.gov.ru 95.173.128.80
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$229,995 USD 4/5
$364,377 USD 3/5
$14,721 USD 3/5
$19,858,521 USD 5/5
$13,377,571 USD 5/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$10 USD
$1,149 USD 2/5
$880 USD
$3,244 USD 1/5
$1,831 USD 2/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$164 USD