Your Website Score is

Similar Ranking

91
카카오
kakao.com
91
NEWS.COM.AU — AUSTRALIA’S #1 NEWS SITE
news.com.au
91
INÍCIO - INEP
inep.gov.br
91
CENTERS FOR DISEASE CONTROL AND PREVENTION
cdc.gov
91
LIVE, BREAKING NEWS TODAY: LATEST NATIONAL HEADLINES, WORLD NEWS AND MORE FROM CBSNEWS.COM AND WATCH THE CBSN LIVE NEWS STREAM 24X7
cbsnews.com
91
NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION | U.S. DEPARTMENT OF COMMERCE
noaa.gov
91
STOCK MARKETS, BUSINESS NEWS, FINANCIALS, EARNINGS - CNBC
cnbc.com

Latest Sites

14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com
14
NGF LEGAL – CORPORATE LAWYER AGENCY
ngflegal.com
14
GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED
globallogisticslimited.com
50
THE GUY R COOK REPORT BLOG
guyrcook.com
26
CLOKIDS
clokids.shop

Top Technologies

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

91 gosuslugi.ru Last Updated: 11 months

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

Desktop

Mobile

Performance Desktop Score 96%
Best Practices Desktop Score 85%
SEO Desktop Score 90%
Progressive Web App Desktop Score 62%
Performance Mobile Score 90%
Best Practices Mobile Score 85%
SEO Mobile Score 92%
Progressive Web App Mobile Score 63%
Page Authority Authority 67%
Domain Authority Domain Authority 93%
Moz Rank 6.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 49 Characters
ПОРТАЛ ГОСУДАРСТВЕННЫХ УСЛУГ РОССИЙСКОЙ ФЕДЕРАЦИИ
Meta Description 49 Characters
Портал государственных услуг Российской Федерации
Effective URL 24 Characters
https://www.gosuslugi.ru
Excerpt Page content
Портал государственных услуг Российской Федерациичто вы ищете?НайтиУслугиОплатаПоддержкаЛичный кабинет Введите название услуги или ведомстваНайти Суперсервисы: госуслуги без бумажных документов и виз...
Keywords Cloud Density
вопросы7 услуги7 услуг6 госуслуг6 госуслуги5 государственных4 получить4 портал4 гражданина3 задолженность3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
вопросы 7
услуги 7
услуг 6
госуслуг 6
госуслуги 5
государственных 4
получить 4
портал 4
гражданина 3
задолженность 3
Google Preview Your look like this in google search result
ПОРТАЛ ГОСУДАРСТВЕННЫХ УСЛУГ РОССИЙСКОЙ ФЕДЕРАЦИИ
https://www.gosuslugi.ru
Портал государственных услуг Российской Федерации
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 51 years
Create on: 2008-09-01 / 12 years
Expires on: 2020-09-01 / 2 months 24 days

RU-CENTER-RU ,

Nameservers
ns1.gosuslugi.ru.
109.207.2.218
ns2.gosuslugi.ru.
213.59.255.175
ns4-l2.nic.ru.
ns8-l2.nic.ru.
Page Size Code & Text Ratio
Document Size: ~64.37 KB
Code Size: ~41.37 KB
Text Size: ~23 KB Ratio: 35.73%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 530 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Preload key requests Potential savings of 300 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 37 requests • 375 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 10 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 36 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Reduce server response times (TTFB) Root document took 720 ms
Time To First Byte identifies the time at which your server sends a response
Minimize third-party usage Third-party code blocked the main thread for 10 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 375 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted

Mobile

Mobile Screenshot
Keep request counts low and transfer sizes small 37 requests • 392 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 4 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 400 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First Contentful Paint (3G) 1710 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 90 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 98.51% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 24 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Server response times are low (TTFB) Root document took 180 ms
Time To First Byte identifies the time at which your server sends a response
Reduce the impact of third-party code Third-party code blocked the main thread for 570 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 620 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 392 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 555 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Preload key requests Potential savings of 1,410 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Set-Cookie: userSelectedLanguage=ru; Domain=.gosuslugi.ru; Path=/; Expires=Sun, 08 Oct 2293 23:32:53 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 61215
ETag: W/"ef1f-Vb+9w9VRjajjmtSgpRnndhIEGWc"
Date: Tue, 24 Dec 2019 23:32:53 GMT
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome