Tools & Wizards About Us
prg.kz screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

prg.kz

ИС Параграф – крупнейшая справочная система в РК

Page Load Speed

3.6 sec in total

First Response

680 ms

Resources Loaded

2.7 sec

Page Rendered

140 ms

prg.kz screenshot

About Website

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

ИС Параграф объединяет в себе несколько информационных блоков – от специфических для юристов, бухгалтеров и медиков, до ежедневно нужной справочной информации. Переходите на сайт.

Visit prg.kz

Key Findings

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

Performance Metrics

prg.kz performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

prg.kz

680 ms

index.php

586 ms

webfont.js

29 ms

webfont.js

376 ms

default.css

377 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 61% of them (25 requests) were addressed to the original Prg.kz, 7% (3 requests) were made to C.zero.kz and 5% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source C.zero.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 493.0 kB (79%)

Content Size

627.3 kB

After Optimization

134.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prg.kz main page is 627.3 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. 25% of websites need less resources to load. HTML takes 368.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 320.8 kB

  • Original 368.9 kB
  • After minification 362.0 kB
  • After compression 48.1 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 320.8 kB or 87% of the original size.

Image Optimization

-48%

Potential reduce by 38.7 kB

  • Original 80.1 kB
  • After minification 41.4 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. Obviously, Prg needs image optimization as it can save up to 38.7 kB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 65.3 kB

  • Original 96.4 kB
  • After minification 82.8 kB
  • After compression 31.1 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 65.3 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 68.1 kB

  • Original 81.9 kB
  • After minification 65.1 kB
  • After compression 13.8 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. Prg.kz needs all CSS files to be minified and compressed as it can save up to 68.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (47%)

Requests Now

36

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prg.kz

prg.kz

680 ms

index.php

index.php

586 ms

webfont.js

webfont.js

29 ms

webfont.js

webfont.js

376 ms

default.css

default.css

377 ms

styles.css

styles.css

786 ms

jquery.min.js

jquery.min.js

75 ms

engine.css

engine.css

572 ms

advert.js

advert.js

385 ms

libs.js

libs.js

560 ms

events.js

events.js

563 ms

mobilyslider.js

mobilyslider.js

578 ms

jquery.maphilight.js

jquery.maphilight.js

745 ms

load_con.js

load_con.js

752 ms

share42.js

share42.js

805 ms

analytics.js

analytics.js

10 ms

z.js

z.js

871 ms

gpt.js

gpt.js

8 ms

home.png

home.png

198 ms

watch.js

watch.js

6 ms

header_line.png

header_line.png

193 ms

topmenu_block_r.png

topmenu_block_r.png

196 ms

pravmedia.png

pravmedia.png

193 ms

tabs_r.png

tabs_r.png

199 ms

logo.png

logo.png

196 ms

pubads_impl_83.js

pubads_impl_83.js

18 ms

collect

collect

87 ms

bigicon_lawyer.png

bigicon_lawyer.png

351 ms

bigicon_continent.png

bigicon_continent.png

356 ms

bigicon_accountant.png

bigicon_accountant.png

351 ms

bigicon_medicine.png

bigicon_medicine.png

354 ms

bigicon_info.png

bigicon_info.png

356 ms

icons.png

icons.png

378 ms

client.js

client.js

258 ms

css

css

67 ms

container.html

container.html

43 ms

collect

collect

87 ms

ads

ads

131 ms

app3.js

app3.js

627 ms

z.js

z.js

184 ms

z.png

z.png

196 ms

Accessibility Review

prg.kz accessibility score

68

Accessibility Issues

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

prg.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

prg.kz SEO score

62

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prg.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Prg.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

prg.kz

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