Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

spr.kz

| Ƹ : , , |

Page Load Speed

5.7 sec in total

First Response

591 ms

Resources Loaded

4.7 sec

Page Rendered

416 ms

spr.kz screenshot

About Website

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

. : , , , , .

Visit spr.kz

Key Findings

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

Performance Metrics

spr.kz performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

spr.kz

591 ms

spr.kz

671 ms

www.spr.kz

1119 ms

home.css

340 ms

advert.js

640 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 39% of them (13 requests) were addressed to the original Spr.kz, 42% (14 requests) were made to Spr.ru and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Spr.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.7 kB (11%)

Content Size

368.5 kB

After Optimization

328.8 kB

In fact, the total size of Spr.kz main page is 368.5 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. 40% of websites need less resources to load. Images take 209.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 32.6 kB

  • Original 40.8 kB
  • After minification 40.7 kB
  • After compression 8.2 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 32.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 3.1 kB

  • Original 209.8 kB
  • After minification 206.7 kB

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. Spr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

CSS Optimization

-23%

Potential reduce by 4.0 kB

  • Original 17.5 kB
  • After minification 17.5 kB
  • After compression 13.6 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. Spr.kz needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (30%)

Requests Now

20

After Optimization

14

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

Accessibility Review

spr.kz accessibility score

86

Accessibility Issues

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

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

Links do not have a discernible name

Best Practices

spr.kz best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

spr.kz SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    HY

  • Language Claimed

    N/A

  • Encoding

    CP1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spr.kz can be misinterpreted by Google and other search engines. Our service has detected that Armenian 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 Spr.kz main page’s claimed encoding is cp1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Spr. 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: