Tools & Wizards About Us

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

next.kz

NEXT

Page Load Speed

11.3 sec in total

First Response

896 ms

Resources Loaded

7.6 sec

Page Rendered

2.8 sec

About Website

Visit next.kz now to see the best up-to-date NEXT content for Kazakhstan and also check out these interesting facts you probably never knew about next.kz

Visit next.kz

Key Findings

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

Performance Metrics

next.kz performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value41.9 s

0/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value7.1 s

51/100

10%

Network Requests Diagram

next.kz

896 ms

next.kz

958 ms

tilda-fallback-1.0.min.js

190 ms

tilda-grid-3.0.min.css

44 ms

tilda-blocks-page35531439.min.css

239 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Next.kz, 43% (35 requests) were made to Static.wixstatic.com and 23% (19 requests) were made to Static.tildacdn.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Static.tildacdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 604.8 kB (3%)

Content Size

19.7 MB

After Optimization

19.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Next.kz main page is 19.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 19.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 126.0 kB

  • Original 143.7 kB
  • After minification 142.5 kB
  • After compression 17.7 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 126.0 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 478.4 kB

  • Original 19.5 MB
  • After minification 19.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. NEXT images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 54 B

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 2.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 284 B

  • Original 4.2 kB
  • After minification 4.2 kB
  • After compression 4.0 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. Next.kz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (24%)

Requests Now

75

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

next.kz accessibility score

85

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

next.kz best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

next.kz SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Next.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 Next.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 description is not detected on the main page of NEXT. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: