Spain · Madrid Completed: Apr 16, 2026 17:34 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Rich content metadata — your pages look great everywhere.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No H1 heading found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 third-party resources (88% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/e7bd0546-67fb-4212-b6ce-8999ad0080ff)<a href="https://beavercheck.com/results/e7bd0546-67fb-4212-b6ce-8999ad0080ff"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgosuslugi.ru" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgosuslugi.ruThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your page blocks user input for 4542ms — visitors may think the site is frozen. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~20%.
Page feels frozen for 4.5s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
₽21,000 investment → ₽5.28/month returns
₽21,000
6h · 5 findings
₽5.28 /mo
~₽63 / year
No applicable regulations in this jurisdiction
₽3,500 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.0 developer hours at ₽3500/hr
Based on Russia rates (₽3500/hr)
Start here for the best return on investment
₽5.28 / month at risk
~₽63 / year if left unfixed
₽5.28 /mo
725.9 MB/mo × 7.273 RUB/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
786 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
786 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4.54 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
867 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
11.67 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| gu-st.ru/portal-st/lib-assets/fonts/Lato-Regular.woff2 | 7200.0 s | 179.4 KiB |
| gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff2 | 7200.0 s | 28.7 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| gosuslugi.ru/__jsch/static/script.js | 10.5 s | 10.0 s | 4.6 ms |
| gosuslugi.ru/ | 467 ms | 3.6 ms | 0.6 ms |
| Unattributable | 216 ms | 4.7 ms | 0.0 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 10.0 s |
| Other | 645 ms |
| Garbage Collection | 215 ms |
| Style & Layout | 155 ms |
| Rendering | 82 ms |
| Parse HTML & CSS | 6.4 ms |
| Script Parsing & Compilation | 5.2 ms |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!DOCTYPE html> | Syntax not understood |
| 2 | <html> | Syntax not understood |
| 3 | <head> | Syntax not understood |
| 4 | <title>Ошибка</title> | Syntax not understood |
| 5 | <meta http-equiv="pragma" content="no-cache"/> | Syntax not understood |
| 6 | <meta http-equiv="cache-control" content="no-cache, must-revalidate"/> | Syntax not understood |
| 7 | <meta http-equiv="cache-control" content="no-store, post-check=0, pre-check=0"/> | Syntax not understood |
| 8 | <meta http-equiv="content-type" content="text/html; charset=utf-8"/> | Syntax not understood |
| 9 | <meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1"/> | Syntax not understood |
| 10 | <meta name="viewport" content="width=device-width, initial-scale=1.0"/> | Syntax not understood |
| 11 | <meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE"/> | Syntax not understood |
| 12 | <meta name="description" content=""/> | Syntax not understood |
| 13 | <meta name="robots" content="none"/> | Syntax not understood |
| 14 | <link rel="shortcut icon" href="https://gu-st.ru/static_errors/imperva/img/favicon.ico"/> | Unknown directive |
| 15 | <link type="text/css" rel="stylesheet" href="https://gu-st.ru/static_errors/imperva/css/error.css"/> | Unknown directive |
| 16 | </head> | Syntax not understood |
| 17 | <body class="error-page"> | Syntax not understood |
| 18 | <div class="baseheader-wrap simple"> | Syntax not understood |
| 19 | <div class="page-wrap baseheader"> | Syntax not understood |
| 20 | <a href="/" class="logo" title=""> | Syntax not understood |
| 21 | ГОСУСЛУГИ | Syntax not understood |
| 22 | </a> | Syntax not understood |
| 23 | <div class="slogan"> | Syntax not understood |
| 24 | Доступ к сервисам электронного правительства | Syntax not understood |
| 25 | </div> | Syntax not understood |
| 26 | </div> | Syntax not understood |
| 27 | </div> | Syntax not understood |
| 29 | <div class="basecontent-wrap"> | Syntax not understood |
| 30 | <div class="page-wrap basecontent"> | Syntax not understood |
| 31 | <div class="base-cover simple"> | Syntax not understood |
| 32 | <section class="b-error"> | Syntax not understood |
| 33 | <h1 class="b-error__title"> | Syntax not understood |
| 34 | Во время обработки запроса произошла ошибка | Syntax not understood |
| 35 | </h1> | Syntax not understood |
| 36 | <p class="b-error__text">Код ошибки: <b class="error-code">№8525106823901541735</b></p> | Unknown directive |
| 37 | <p class="b-error__text">IP address: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/ip.js" "></script></b></p> | Unknown directive |
| 38 | <p class="b-error__text">Время инцидента: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/date.js" "></script></b></p> | Unknown directive |
| 39 | <p class="b-error__text">Приносим извинения за временные неудобства</p> | Syntax not understood |
| 41 | <div class="b-error__buttons"> | Syntax not understood |
| 42 | <a class="b-error__button" href="javascript: history.back();"> | Unknown directive |
| 43 | Вернуться назад | Syntax not understood |
| 44 | </a> | Syntax not understood |
| 45 | <a class="b-error__button b-error__button_main" href="/"> | Syntax not understood |
| 46 | Перейти на главную | Syntax not understood |
| 47 | </a> | Syntax not understood |
| 48 | </div> | Syntax not understood |
| 49 | </section> | Syntax not understood |
| 50 | </div> | Syntax not understood |
| 51 | </div> | Syntax not understood |
| 52 | </div> | Syntax not understood |
| 54 | <div class="basefooter-wrap"> | Syntax not understood |
| 55 | <div class="page-wrap basefooter"> | Syntax not understood |
| 56 | <div class="logo-dept mks"></div> | Syntax not understood |
| 57 | <div class="logo-dept rtk"></div> | Syntax not understood |
| 58 | <div class="copyright" id="copyright"></div> | Syntax not understood |
| 59 | </div> | Syntax not understood |
| 60 | </div> | Syntax not understood |
| 62 | <script type="text/javascript"> | Syntax not understood |
| 63 | var copyrightText = "Официальный интернет-портал государственных услуг, " + new Date().getFullYear() + " г."; | Syntax not understood |
| 64 | document.getElementById('copyright').innerText = copyrightText; | Syntax not understood |
| 65 | </script> | Syntax not understood |
| 67 | </body> | Syntax not understood |
| 68 | </html> | Syntax not understood |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.03 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.08 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.09 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.03 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.17 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| gu-st.ru/portal-st/lib-assets/fonts/Lato-Regular.woff2 | 7200.0 s | 0 B |
| gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff2 | 7200.0 s | 0 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| gosuslugi.ru/ | 302 ms |
| gosuslugi.ru/ | 51 ms |
| www.gosuslugi.ru/ | 0.0 ms |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| gosuslugi.ru/__jsch/static/script.js | 2.0 s | 1.9 s | 1.4 ms |
| www.gosuslugi.ru/__jsch/static/script.js | 1.4 s | 1.4 s | 1.2 ms |
| www.gosuslugi.ru/ | 116 ms | 1.9 ms | 0.3 ms |
| Unattributable | 67 ms | 0.6 ms | 0.0 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.3 s |
| Other | 220 ms |
| Style & Layout | 43 ms |
| Garbage Collection | 39 ms |
| Rendering | 19 ms |
| Script Parsing & Compilation | 2.9 ms |
| Parse HTML & CSS | 2.8 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages with WebSocket cannot enter back/forward cache. | Pending browser support |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
| Back/forward cache is disabled because WebSocket has been used. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| gu-st.ru/portal-st/styles.7d48372f563bb034.css | 17.7 KiB | 17.6 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!DOCTYPE html> | Syntax not understood |
| 2 | <html> | Syntax not understood |
| 3 | <head> | Syntax not understood |
| 4 | <title>Ошибка</title> | Syntax not understood |
| 5 | <meta http-equiv="pragma" content="no-cache"/> | Syntax not understood |
| 6 | <meta http-equiv="cache-control" content="no-cache, must-revalidate"/> | Syntax not understood |
| 7 | <meta http-equiv="cache-control" content="no-store, post-check=0, pre-check=0"/> | Syntax not understood |
| 8 | <meta http-equiv="content-type" content="text/html; charset=utf-8"/> | Syntax not understood |
| 9 | <meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1"/> | Syntax not understood |
| 10 | <meta name="viewport" content="width=device-width, initial-scale=1.0"/> | Syntax not understood |
| 11 | <meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE"/> | Syntax not understood |
| 12 | <meta name="description" content=""/> | Syntax not understood |
| 13 | <meta name="robots" content="none"/> | Syntax not understood |
| 14 | <link rel="shortcut icon" href="https://gu-st.ru/static_errors/imperva/img/favicon.ico"/> | Unknown directive |
| 15 | <link type="text/css" rel="stylesheet" href="https://gu-st.ru/static_errors/imperva/css/error.css"/> | Unknown directive |
| 16 | </head> | Syntax not understood |
| 17 | <body class="error-page"> | Syntax not understood |
| 18 | <div class="baseheader-wrap simple"> | Syntax not understood |
| 19 | <div class="page-wrap baseheader"> | Syntax not understood |
| 20 | <a href="/" class="logo" title=""> | Syntax not understood |
| 21 | ГОСУСЛУГИ | Syntax not understood |
| 22 | </a> | Syntax not understood |
| 23 | <div class="slogan"> | Syntax not understood |
| 24 | Доступ к сервисам электронного правительства | Syntax not understood |
| 25 | </div> | Syntax not understood |
| 26 | </div> | Syntax not understood |
| 27 | </div> | Syntax not understood |
| 29 | <div class="basecontent-wrap"> | Syntax not understood |
| 30 | <div class="page-wrap basecontent"> | Syntax not understood |
| 31 | <div class="base-cover simple"> | Syntax not understood |
| 32 | <section class="b-error"> | Syntax not understood |
| 33 | <h1 class="b-error__title"> | Syntax not understood |
| 34 | Во время обработки запроса произошла ошибка | Syntax not understood |
| 35 | </h1> | Syntax not understood |
| 36 | <p class="b-error__text">Код ошибки: <b class="error-code">№8525106826964900110</b></p> | Unknown directive |
| 37 | <p class="b-error__text">IP address: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/ip.js" "></script></b></p> | Unknown directive |
| 38 | <p class="b-error__text">Время инцидента: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/date.js" "></script></b></p> | Unknown directive |
| 39 | <p class="b-error__text">Приносим извинения за временные неудобства</p> | Syntax not understood |
| 41 | <div class="b-error__buttons"> | Syntax not understood |
| 42 | <a class="b-error__button" href="javascript: history.back();"> | Unknown directive |
| 43 | Вернуться назад | Syntax not understood |
| 44 | </a> | Syntax not understood |
| 45 | <a class="b-error__button b-error__button_main" href="/"> | Syntax not understood |
| 46 | Перейти на главную | Syntax not understood |
| 47 | </a> | Syntax not understood |
| 48 | </div> | Syntax not understood |
| 49 | </section> | Syntax not understood |
| 50 | </div> | Syntax not understood |
| 51 | </div> | Syntax not understood |
| 52 | </div> | Syntax not understood |
| 54 | <div class="basefooter-wrap"> | Syntax not understood |
| 55 | <div class="page-wrap basefooter"> | Syntax not understood |
| 56 | <div class="logo-dept mks"></div> | Syntax not understood |
| 57 | <div class="logo-dept rtk"></div> | Syntax not understood |
| 58 | <div class="copyright" id="copyright"></div> | Syntax not understood |
| 59 | </div> | Syntax not understood |
| 60 | </div> | Syntax not understood |
| 62 | <script type="text/javascript"> | Syntax not understood |
| 63 | var copyrightText = "Официальный интернет-портал государственных услуг, " + new Date().getFullYear() + " г."; | Syntax not understood |
| 64 | document.getElementById('copyright').innerText = copyrightText; | Syntax not understood |
| 65 | </script> | Syntax not understood |
| 67 | </body> | Syntax not understood |
| 68 | </html> | Syntax not understood |
To appear in search results, crawlers need access to your app.
Send Feedback