1tv.kz

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

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.

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.

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

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.

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

A long cache lifetime can speed up repeat visits to your page. Learn more.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

These DOM elements contribute most to the CLS of the page.

This is the largest contentful element painted within the viewport. Learn More

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

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.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

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.

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.

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.

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.

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.

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

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

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.

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

Screen reader users rely on frame titles to describe the contents of frames. Learn more.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

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.

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.

Low-contrast text is difficult or impossible for many users to read. Learn more.