Egov.kz Site Title
Қазақстан Республикасының Электрондық үкіметі |
Egov.kz Test Results
Egov.kz Mobile Performance: 20/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 4,920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Serve images in next-gen formats. Potential savings of 650 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 437 KiB
Optimized images load faster and consume less cellular data. Learn more.
Remove unused CSS. Potential savings of 89 KiB
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. Learn more.
Avoid multiple page redirects. Potential savings of 810 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Minify CSS. Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Remove unused JavaScript. Potential savings of 87 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 750 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. Learn more.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Serve static assets with an efficient cache policy
106 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
5.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid an excessive DOM size
1,089 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoids enormous network payloads
Total size was 2,532 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid long main-thread tasks
15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
126 requests • 2,532 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
45 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Egov.kz Mobile SEO: 67/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Document doesn't have a valid `hreflang`
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
87% 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. Learn more.
Egov.kz Mobile Best Practices: 50/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
110 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Egov.kz Mobile Progressive Web App: 11/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 1440px does not match the window size of 360px.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
110 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 10.7 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Egov.kz Mobile Accessibility: 75/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.egov.com
www.egov.net
www.egov.org
www.egov.info
www.egov.biz
www.egov.us
www.egov.mobi
www.gov.kz
www.egov.kz
www.wgov.kz
www.ewgov.kz
www.wegov.kz
www.sgov.kz
www.esgov.kz
www.segov.kz
www.dgov.kz
www.edgov.kz
www.degov.kz
www.rgov.kz
www.ergov.kz
www.regov.kz
www.eov.kz
www.efov.kz
www.egfov.kz
www.efgov.kz
www.evov.kz
www.egvov.kz
www.evgov.kz
www.etov.kz
www.egtov.kz
www.etgov.kz
www.ebov.kz
www.egbov.kz
www.ebgov.kz
www.eyov.kz
www.egyov.kz
www.eygov.kz
www.ehov.kz
www.eghov.kz
www.ehgov.kz
www.egv.kz
www.egiv.kz
www.egoiv.kz
www.egiov.kz
www.egkv.kz
www.egokv.kz
www.egkov.kz
www.eglv.kz
www.egolv.kz
www.eglov.kz
www.egpv.kz
www.egopv.kz
www.egpov.kz
www.ego.kz
www.egoc.kz
www.egovc.kz
www.egocv.kz
www.egof.kz
www.egovf.kz
www.egofv.kz
www.egog.kz
www.egovg.kz
www.egogv.kz
www.egob.kz
www.egovb.kz
www.egobv.kz
www.egov.net
www.egov.org
www.egov.info
www.egov.biz
www.egov.us
www.egov.mobi
www.gov.kz
www.egov.kz
www.wgov.kz
www.ewgov.kz
www.wegov.kz
www.sgov.kz
www.esgov.kz
www.segov.kz
www.dgov.kz
www.edgov.kz
www.degov.kz
www.rgov.kz
www.ergov.kz
www.regov.kz
www.eov.kz
www.efov.kz
www.egfov.kz
www.efgov.kz
www.evov.kz
www.egvov.kz
www.evgov.kz
www.etov.kz
www.egtov.kz
www.etgov.kz
www.ebov.kz
www.egbov.kz
www.ebgov.kz
www.eyov.kz
www.egyov.kz
www.eygov.kz
www.ehov.kz
www.eghov.kz
www.ehgov.kz
www.egv.kz
www.egiv.kz
www.egoiv.kz
www.egiov.kz
www.egkv.kz
www.egokv.kz
www.egkov.kz
www.eglv.kz
www.egolv.kz
www.eglov.kz
www.egpv.kz
www.egopv.kz
www.egpov.kz
www.ego.kz
www.egoc.kz
www.egovc.kz
www.egocv.kz
www.egof.kz
www.egovf.kz
www.egofv.kz
www.egog.kz
www.egovg.kz
www.egogv.kz
www.egob.kz
www.egovb.kz
www.egobv.kz