Tools & Wizards About Us
proto.uz screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

proto.uz

Системы безопасности в Узбекистане под ключ — Proto

Page Load Speed

5.2 sec in total

First Response

857 ms

Resources Loaded

4.1 sec

Page Rendered

232 ms

proto.uz screenshot

About Website

Click here to check amazing Proto content for Uzbekistan. Otherwise, check out these important facts you probably never knew about proto.uz

Установка и обслуживание видеонаблюдения, СКУД, пожароохранной сигнализации, СКС по всему Узбекистану. Для организаций и частных лиц.

Visit proto.uz

Key Findings

We analyzed Proto.uz page load time and found that the first response time was 857 ms and then it took 4.3 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

proto.uz performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value7,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

proto.uz

857 ms

gtm.js

63 ms

template_7410c5e0becdb3e4be9b7fba4f418f48_v1.css

289 ms

jquery-2.1.4.min.js

843 ms

bootstrap.min.js

561 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 87% of them (45 requests) were addressed to the original Proto.uz, 8% (4 requests) were made to Api-maps.yandex.ru and 4% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Proto.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.0 kB (14%)

Content Size

220.3 kB

After Optimization

190.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proto.uz main page is 220.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. 35% of websites need less resources to load. Images take 168.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 19.0 kB

  • Original 24.8 kB
  • After minification 23.7 kB
  • After compression 5.8 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 19.0 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 4.7 kB

  • Original 168.1 kB
  • After minification 163.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. Proto images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 141 B

  • Original 3.0 kB
  • After minification 3.0 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

-25%

Potential reduce by 6.1 kB

  • Original 24.3 kB
  • After minification 24.3 kB
  • After compression 18.2 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. Proto.uz needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (31%)

Requests Now

45

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proto.uz

proto.uz

857 ms

gtm.js

gtm.js

63 ms

template_7410c5e0becdb3e4be9b7fba4f418f48_v1.css

template_7410c5e0becdb3e4be9b7fba4f418f48_v1.css

289 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

843 ms

bootstrap.min.js

bootstrap.min.js

561 ms

jquery.maskedinput.js

jquery.maskedinput.js

572 ms

scripts.js

scripts.js

574 ms

lang_ru.js

lang_ru.js

578 ms

fonts.css

fonts.css

586 ms

bootstrap.min.css

bootstrap.min.css

842 ms

jquery.fancybox.js

jquery.fancybox.js

1139 ms

jquery.fancybox.css

jquery.fancybox.css

858 ms

732 ms

911 ms

1089 ms

1210 ms

ba.js

ba.js

141 ms

bg1.jpg

bg1.jpg

857 ms

proto-logo-head.png

proto-logo-head.png

281 ms

menu-top-video.png

menu-top-video.png

294 ms

menu-top-signal.png

menu-top-signal.png

285 ms

menu-top-net.png

menu-top-net.png

281 ms

menu-top-skud.png

menu-top-skud.png

289 ms

icon-blue-car.png

icon-blue-car.png

560 ms

icon-blue-stamp.png

icon-blue-stamp.png

561 ms

icon-blue-warranty.png

icon-blue-warranty.png

568 ms

icon-blue-pocket.png

icon-blue-pocket.png

578 ms

icon-blue-clock.png

icon-blue-clock.png

586 ms

icon-blue-trash.png

icon-blue-trash.png

841 ms

icon-blue-sack.png

icon-blue-sack.png

841 ms

icon-blue-gear.png

icon-blue-gear.png

852 ms

icon-white-pen.png

icon-white-pen.png

866 ms

icon-white-oscillo.png

icon-white-oscillo.png

878 ms

icon-white-gear.png

icon-white-gear.png

1120 ms

icon-white-rocket.png

icon-white-rocket.png

1121 ms

how-work-bg.png

how-work-bg.png

1136 ms

how-work.png

how-work.png

1141 ms

24h.png

24h.png

1155 ms

client-unesco.jpg

client-unesco.jpg

1171 ms

client-mikrokreditbank.jpg

client-mikrokreditbank.jpg

1399 ms

client-tdtu.jpg

client-tdtu.jpg

1400 ms

client-tshtxuz.jpg

client-tshtxuz.jpg

1420 ms

client-tms.jpg

client-tms.jpg

1426 ms

client-xb.jpg

client-xb.jpg

1442 ms

client-ipak.jpg

client-ipak.jpg

1464 ms

proto-logo-footer.png

proto-logo-footer.png

1680 ms

bx_stat

bx_stat

217 ms

blogger_sans-webfont.woff

blogger_sans-webfont.woff

1855 ms

blogger_sans-bold-webfont.woff

blogger_sans-bold-webfont.woff

1883 ms

blogger_sans-medium-webfont.woff

blogger_sans-medium-webfont.woff

1607 ms

blogger_sans-light-webfont.woff

blogger_sans-light-webfont.woff

1914 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1944 ms

Accessibility Review

proto.uz accessibility score

74

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.

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 IDs are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

proto.uz best practices score

75

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

SEO Factors

proto.uz SEO score

92

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

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proto.uz 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 Proto.uz 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

proto.uz

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