Tools & Wizards About Us
rline.kz screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

rline.kz

Продажа раций, Радиостанций, антенн, рации Алматы, Купить, Продам, Алмата, Казахстан | Rline.kz

Page Load Speed

9.6 sec in total

First Response

565 ms

Resources Loaded

8.4 sec

Page Rendered

584 ms

rline.kz screenshot

About Website

Welcome to rline.kz homepage info - get ready to check Rline best content for Kazakhstan right away, or after learning these important things about rline.kz

Рации Алматы, Рации в Казахстане. Ремонт и обслуживание. Большой выбор раций и Аксессуаров. Рации для Охраны Алмата

Visit rline.kz

Key Findings

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

Performance Metrics

rline.kz performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

rline.kz

565 ms

rline.kz

1515 ms

jquery.fancybox.css

367 ms

jquery.jscrollpane.css

551 ms

glass.css

553 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 86% of them (130 requests) were addressed to the original Rline.kz, 3% (4 requests) were made to Sipnet.ru and 2% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rline.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 514.6 kB (13%)

Content Size

3.9 MB

After Optimization

3.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rline.kz main page is 3.9 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. 55% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 367.8 kB

  • Original 409.0 kB
  • After minification 314.4 kB
  • After compression 41.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. This page needs HTML code to be minified as it can gain 94.7 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 367.8 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 20.4 kB

  • Original 3.1 MB
  • After minification 3.1 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. Rline images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 103.0 kB

  • Original 358.3 kB
  • After minification 358.2 kB
  • After compression 255.3 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 103.0 kB or 29% of the original size.

CSS Optimization

-44%

Potential reduce by 23.4 kB

  • Original 53.1 kB
  • After minification 50.8 kB
  • After compression 29.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. Rline.kz needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (45%)

Requests Now

146

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rline.kz

rline.kz

565 ms

rline.kz

rline.kz

1515 ms

jquery.fancybox.css

jquery.fancybox.css

367 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

551 ms

glass.css

glass.css

553 ms

style.css

style.css

554 ms

template_styles.css

template_styles.css

558 ms

simpla.css

simpla.css

561 ms

jquery.js

jquery.js

1112 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

734 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

734 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

735 ms

glass.js

glass.js

739 ms

script(1).js

script(1).js

743 ms

iefix.js

iefix.js

919 ms

script(2).js

script(2).js

918 ms

script(3).js

script(3).js

918 ms

script(5).js

script(5).js

923 ms

script(6).js

script(6).js

926 ms

banners.css

banners.css

1099 ms

banners.js

banners.js

1101 ms

ctrlnavigate.js

ctrlnavigate.js

1100 ms

jquery-ui.min.js

jquery-ui.min.js

1107 ms

ajax_cart.js

ajax_cart.js

1110 ms

baloon.js

baloon.js

1280 ms

baloon.css

baloon.css

1290 ms

jquery.autocomplete-min.js

jquery.autocomplete-min.js

1286 ms

js

js

57 ms

catalog.js

catalog.js

1290 ms

menu.catalog.css

menu.catalog.css

1291 ms

jquery-ui-1.9.0.custom.min.js

jquery-ui-1.9.0.custom.min.js

1478 ms

filter.min.js

filter.min.js

1645 ms

ajax_compare.js

ajax_compare.js

1469 ms

catalog.compare.result.js

catalog.compare.result.js

1472 ms

catalog.compare.result.css

catalog.compare.result.css

1474 ms

catalog.compare.list.css

catalog.compare.list.css

1475 ms

share.js

share.js

382 ms

callme.js

callme.js

1653 ms

webrtc_client.css

webrtc_client.css

930 ms

conversion.js

conversion.js

84 ms

style(1).css

style(1).css

1109 ms

style(2).css

style(2).css

1113 ms

style(3).css

style(3).css

1113 ms

style(4).css

style(4).css

1116 ms

style(5).css

style(5).css

1280 ms

style(6).css

style(6).css

1289 ms

style(7).css

style(7).css

1285 ms

style(8).css

style(8).css

1288 ms

style(9).css

style(9).css

1117 ms

style(10).css

style(10).css

1118 ms

style(11).css

style(11).css

1281 ms

style(12).css

style(12).css

1289 ms

list.css

list.css

1284 ms

tag.js

tag.js

1124 ms

style.css

style.css

186 ms

core.js

core.js

187 ms

logo.png

logo.png

378 ms

rasii.png

rasii.png

379 ms

gsm2.png

gsm2.png

376 ms

antenna3.png

antenna3.png

376 ms

antenna2.png

antenna2.png

378 ms

spytnik.png

spytnik.png

377 ms

asessyar.png

asessyar.png

564 ms

kabel.png

kabel.png

562 ms

yselitel.png

yselitel.png

563 ms

izm.png

izm.png

561 ms

ysenka.png

ysenka.png

560 ms

button_off.png

button_off.png

557 ms

preobraz.png

preobraz.png

740 ms

35457789_w640_h2048_optoma_logo.jpg

35457789_w640_h2048_optoma_logo.jpg

742 ms

beeline.jpg

beeline.jpg

1113 ms

N_deF9d6Gng.jpg

N_deF9d6Gng.jpg

991 ms

21867.jpg

21867.jpg

991 ms

LTE.jpg

LTE.jpg

744 ms

h31JFqxI0BA.jpg

h31JFqxI0BA.jpg

1467 ms

sm_2gsm.jpg

sm_2gsm.jpg

990 ms

KdLs62E282I.jpg

KdLs62E282I.jpg

1300 ms

ouTV7t643KA_1.jpg

ouTV7t643KA_1.jpg

1289 ms

sIdBy7NsW58.jpg

sIdBy7NsW58.jpg

1479 ms

nwIfiyhfWNQ.jpg

nwIfiyhfWNQ.jpg

1300 ms

91eacad2cad5711a6c9f47fa083d4aa3.160x160.jpg

91eacad2cad5711a6c9f47fa083d4aa3.160x160.jpg

1298 ms

hxwkhjdpjwg.160x160.jpg

hxwkhjdpjwg.160x160.jpg

1473 ms

sfdf5.160x160.jpg

sfdf5.160x160.jpg

1483 ms

GSM_900_1800_____51ecac7da72f7_1.160x160.png

GSM_900_1800_____51ecac7da72f7_1.160x160.png

1484 ms

5722a49401bc978d9c8d1f1848af6dab.160x160.jpg

5722a49401bc978d9c8d1f1848af6dab.160x160.jpg

1484 ms

Puxing%20PX-359.160x160.jpg

Puxing%20PX-359.160x160.jpg

1649 ms

i-274.160x160.jpg

i-274.160x160.jpg

1655 ms

seft.160x160.jpg

seft.160x160.jpg

1664 ms

Yosan_CB_200__4e434f4c57c0e.160x160.jpg

Yosan_CB_200__4e434f4c57c0e.160x160.jpg

1667 ms

AnyTone_AT_628G__4d087eeeefd4a.160x160.jpg

AnyTone_AT_628G__4d087eeeefd4a.160x160.jpg

1667 ms

AnyTone_AT_288__4e20159eea0a1.160x160.jpg

AnyTone_AT_288__4e20159eea0a1.160x160.jpg

1669 ms

AnyTone_AT_289U_4e7822a8c5824.160x160.jpg

AnyTone_AT_289U_4e7822a8c5824.160x160.jpg

1829 ms

webrtc_client.min.js

webrtc_client.min.js

351 ms

icon-phone-white2.svg

icon-phone-white2.svg

473 ms

257 ms

ga.js

ga.js

257 ms

watch.js

watch.js

6 ms

form.html

form.html

1468 ms

cb-145.160x160.jpg

cb-145.160x160.jpg

1475 ms

earpiece2.160x160.jpg

earpiece2.160x160.jpg

1478 ms

es604.160x160.jpg

es604.160x160.jpg

1478 ms

948174762e91ac12573ae02d1042ea51.160x160.jpg

948174762e91ac12573ae02d1042ea51.160x160.jpg

1480 ms

delitel1-3.160x160.jpg

delitel1-3.160x160.jpg

1637 ms

34 ms

__utm.gif

__utm.gif

12 ms

35 ms

4444444444444444.160x160.jpg

4444444444444444.160x160.jpg

1467 ms

91c005ef5024c21471967f830c47c29d.160x160.jpg

91c005ef5024c21471967f830c47c29d.160x160.jpg

1476 ms

fyav.160x160.png

fyav.160x160.png

1479 ms

aaa_1.160x160.jpg

aaa_1.160x160.jpg

1477 ms

aaa.160x160.jpg

aaa.160x160.jpg

1479 ms

111_2.160x160.jpg

111_2.160x160.jpg

1635 ms

05.160x160.jpg

05.160x160.jpg

1467 ms

10_23.160x160.jpg

10_23.160x160.jpg

1481 ms

7.160x160.jpg

7.160x160.jpg

1483 ms

4_16.160x160.jpg

4_16.160x160.jpg

1237 ms

qca-02-2.160x160.jpg

qca-02-2.160x160.jpg

1238 ms

aaff3afe36ea35871e524e381ed1af08.160x160.jpg

aaff3afe36ea35871e524e381ed1af08.160x160.jpg

1388 ms

advert.gif

advert.gif

670 ms

ottzlibhfsg-1.160x160.jpg

ottzlibhfsg-1.160x160.jpg

1280 ms

20160818_124056.160x160.jpg

20160818_124056.160x160.jpg

1115 ms

bb11.png

bb11.png

1107 ms

bb22.png

bb22.png

1107 ms

bb33.png

bb33.png

1109 ms

bb44.png

bb44.png

1097 ms

logo_foot.png

logo_foot.png

1101 ms

icon_fb.png

icon_fb.png

1110 ms

icon_vk.png

icon_vk.png

1109 ms

yt.png

yt.png

1107 ms

captcha.php

captcha.php

1158 ms

sync_cookie_image_decide

sync_cookie_image_decide

158 ms

image.php

image.php

1106 ms

image.php

image.php

1106 ms

1.jpg

1.jpg

1108 ms

5289.jpg

5289.jpg

1292 ms

AT628.jpg

AT628.jpg

1293 ms

PT260.jpg

PT260.jpg

1160 ms

sync_cookie_image_decide

sync_cookie_image_decide

135 ms

Lexen.jpg

Lexen.jpg

1288 ms

icons.png

icons.png

1105 ms

dropdown.png

dropdown.png

1110 ms

qb.png

qb.png

1163 ms

da.png

da.png

1276 ms

image.php

image.php

1296 ms

bttn.png

bttn.png

1130 ms

area_darken.png

area_darken.png

1124 ms

1

1

132 ms

eqFtjsjqba

eqFtjsjqba

713 ms

lazyload-min.js

lazyload-min.js

32 ms

detector.js

detector.js

512 ms

eqFtjsjqba

eqFtjsjqba

190 ms

Accessibility Review

rline.kz accessibility score

78

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

rline.kz SEO score

93

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

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

rline.kz

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