Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

31.kz

Официальный сайт 31 канала

Page Load Speed

5.9 sec in total

First Response

641 ms

Resources Loaded

4.8 sec

Page Rendered

437 ms

31.kz screenshot

About Website

Click here to check amazing 31 content for Kazakhstan. Otherwise, check out these important facts you probably never knew about 31.kz

Смотрите ваши любимые шоу, сериалы и фильмы онлайн!

Visit 31.kz

Key Findings

We analyzed 31.kz page load time and found that the first response time was 641 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

31.kz performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.964

2/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

31.kz

641 ms

31.kz

1223 ms

vendor.css+common.css.pagespeed.cc.-XH2z2VTWK.css

531 ms

js

53 ms

critical.js

566 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 45% of them (14 requests) were addressed to the original 31.kz, 16% (5 requests) were made to 31kz-player.daitsuna.net and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain 31.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 564.2 kB (66%)

Content Size

853.6 kB

After Optimization

289.5 kB

In fact, the total size of 31.kz main page is 853.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 756.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 78.7 kB

  • Original 92.7 kB
  • After minification 92.4 kB
  • After compression 13.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.7 kB or 85% of the original size.

JavaScript Optimization

-64%

Potential reduce by 482.3 kB

  • Original 756.5 kB
  • After minification 756.5 kB
  • After compression 274.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 482.3 kB or 64% of the original size.

CSS Optimization

-70%

Potential reduce by 3.1 kB

  • Original 4.5 kB
  • After minification 4.4 kB
  • After compression 1.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 31.kz needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (37%)

Requests Now

27

After Optimization

17

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 31. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

31.kz accessibility score

79

Accessibility Issues

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.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

31.kz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

31.kz SEO score

98

Search Engine Optimization Advices

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 31.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 31.kz main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of 31. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: