Tools & Wizards About Us
proto-x.net screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

proto-x.net

Proto-X – Системы видеонаблюдения российского производства

Page Load Speed

6.8 sec in total

First Response

1.1 sec

Resources Loaded

5.6 sec

Page Rendered

189 ms

proto-x.net screenshot

About Website

Visit proto-x.net now to see the best up-to-date Proto X content for Russia and also check out these interesting facts you probably never knew about proto-x.net

Российское производство AHD и IP камер и видеорегистраторов, персональных носимых видеорегистраторов и автомобильных решений для безопасности

Visit proto-x.net

Key Findings

We analyzed Proto-x.net page load time and found that the first response time was 1.1 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

proto-x.net performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.199

62/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

proto-x.net

1055 ms

fonts.css

555 ms

styles.css

1118 ms

template_style.css

570 ms

magnific-popup.css

576 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 61% of them (56 requests) were addressed to the original Proto-x.net, 9% (8 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Static-login.sendpulse.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Proto-x.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (34%)

Content Size

3.1 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Proto-x.net main page is 3.1 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. 60% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 52.6 kB

  • Original 67.2 kB
  • After minification 55.6 kB
  • After compression 14.6 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 11.6 kB, which is 17% 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 52.6 kB or 78% of the original size.

Image Optimization

-12%

Potential reduce by 153.6 kB

  • Original 1.3 MB
  • After minification 1.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. Obviously, Proto X needs image optimization as it can save up to 153.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 774.0 kB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 913.6 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 774.0 kB or 46% of the original size.

CSS Optimization

-82%

Potential reduce by 81.8 kB

  • Original 100.2 kB
  • After minification 75.9 kB
  • After compression 18.4 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-x.net needs all CSS files to be minified and compressed as it can save up to 81.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (67%)

Requests Now

78

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proto-x.net

proto-x.net

1055 ms

fonts.css

fonts.css

555 ms

styles.css

styles.css

1118 ms

template_style.css

template_style.css

570 ms

magnific-popup.css

magnific-popup.css

576 ms

magnific-popup-custom.css

magnific-popup-custom.css

581 ms

call.css

call.css

596 ms

landing-page.css

landing-page.css

829 ms

html5.js

html5.js

854 ms

jquery.js

jquery.js

1439 ms

header.js

header.js

872 ms

jquery.liFixar.js

jquery.liFixar.js

891 ms

circular-slider.min.js

circular-slider.min.js

1105 ms

circular-slider.min.css

circular-slider.min.css

1138 ms

page_ede16661d617ee64ddf07e715f24dd51_v1.css

page_ede16661d617ee64ddf07e715f24dd51_v1.css

1163 ms

template_68fce27d501ec1a55bc643a0cc004ca2_v1.css

template_68fce27d501ec1a55bc643a0cc004ca2_v1.css

1187 ms

core.min.js

core.min.js

2486 ms

dexie3.bundle.min.js

dexie3.bundle.min.js

1675 ms

core_ls.js

core_ls.js

1422 ms

core_fx.min.js

core_fx.min.js

1457 ms

core_frame_cache.min.js

core_frame_cache.min.js

1484 ms

webdebug.ruble.css

webdebug.ruble.css

1707 ms

script.js

script.js

1724 ms

943105a7531c29b603dec5c0c2915598_1.js

943105a7531c29b603dec5c0c2915598_1.js

18 ms

jquery.min.js

jquery.min.js

2039 ms

owl.carousel.min.js

owl.carousel.min.js

2075 ms

default-handler.js

default-handler.js

295 ms

loader.js

loader.js

296 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1669 ms

common.js

common.js

1706 ms

api.js

api.js

37 ms

css

css

43 ms

proto-x.net

proto-x.net

975 ms

qyRUhbK3MA

qyRUhbK3MA

224 ms

ba.js

ba.js

149 ms

background.jpg

background.jpg

358 ms

menu_back.jpg

menu_back.jpg

357 ms

recall.png

recall.png

281 ms

logoback.png

logoback.png

593 ms

logo-light-black-back.png

logo-light-black-back.png

279 ms

ru.jpg

ru.jpg

357 ms

menu_back.jpg

menu_back.jpg

556 ms

menu_separator.jpg

menu_separator.jpg

560 ms

liney.png

liney.png

573 ms

aim.png

aim.png

1440 ms

logo_protox.png

logo_protox.png

1465 ms

zavod.png

zavod.png

1110 ms

proto-x.png

proto-x.png

838 ms

pils.jpg

pils.jpg

1707 ms

news_safety_region_250px.png

news_safety_region_250px.png

1252 ms

news_uv_lamp_250px.jpg

news_uv_lamp_250px.jpg

1398 ms

russia.png

russia.png

1386 ms

1.jpg

1.jpg

1483 ms

vertical-line.png

vertical-line.png

1661 ms

youtube.png

youtube.png

1677 ms

vk.png

vk.png

1727 ms

whatsapp.png

whatsapp.png

1756 ms

twiiter.png

twiiter.png

1779 ms

insta.png

insta.png

1938 ms

call_pic.png

call_pic.png

1958 ms

captcha.php

captcha.php

2185 ms

BngRUXNadjH0qYEzV7ab-oWlsbCGwRuoefDo.woff

BngRUXNadjH0qYEzV7ab-oWlsbCGwRuoefDo.woff

33 ms

BngRUXNadjH0qYEzV7ab-oWlsbCIwRuoefDofMY.woff

BngRUXNadjH0qYEzV7ab-oWlsbCIwRuoefDofMY.woff

47 ms

BngRUXNadjH0qYEzV7ab-oWlsbCCwRuoefDofMY.woff

BngRUXNadjH0qYEzV7ab-oWlsbCCwRuoefDofMY.woff

48 ms

BngRUXNadjH0qYEzV7ab-oWlsbCLwRuoefDofMY.woff

BngRUXNadjH0qYEzV7ab-oWlsbCLwRuoefDofMY.woff

48 ms

BngSUXNadjH0qYEzV7ab-oWlsbg95AiFW_vCRs-2.woff

BngSUXNadjH0qYEzV7ab-oWlsbg95AiFW_vCRs-2.woff

101 ms

BngSUXNadjH0qYEzV7ab-oWlsbg95AiLW_vCRs-2UEU.woff

BngSUXNadjH0qYEzV7ab-oWlsbg95AiLW_vCRs-2UEU.woff

72 ms

BngSUXNadjH0qYEzV7ab-oWlsbg95AiBW_vCRs-2UEU.woff

BngSUXNadjH0qYEzV7ab-oWlsbg95AiBW_vCRs-2UEU.woff

72 ms

BngSUXNadjH0qYEzV7ab-oWlsbg95AiIW_vCRs-2UEU.woff

BngSUXNadjH0qYEzV7ab-oWlsbg95AiIW_vCRs-2UEU.woff

72 ms

PTN57F-webfont.woff

PTN57F-webfont.woff

1945 ms

MAGISTRALC-BOLD.OTF

MAGISTRALC-BOLD.OTF

1983 ms

tag.js

tag.js

1064 ms

analytics.js

analytics.js

41 ms

hit

hit

277 ms

code.js

code.js

431 ms

recaptcha__en.js

recaptcha__en.js

39 ms

collect

collect

47 ms

js

js

60 ms

qyRUhbK3MA

qyRUhbK3MA

404 ms

hit

hit

538 ms

sync-loader.js

sync-loader.js

686 ms

counter

counter

517 ms

dyn-goal-config.js

dyn-goal-config.js

579 ms

qyRUhbK3MA

qyRUhbK3MA

621 ms

hit

hit

135 ms

advert.gif

advert.gif

738 ms

sync_cookie_image_decide

sync_cookie_image_decide

134 ms

polyfill.min.js

polyfill.min.js

32 ms

901c7268815d438f661aa269721aad7b86adf62efa834d61a60197a0c5f9a61e.js

901c7268815d438f661aa269721aad7b86adf62efa834d61a60197a0c5f9a61e.js

12 ms

bundle_ru_RU.js

bundle_ru_RU.js

51 ms

tracker

tracker

129 ms

default-handler.js

default-handler.js

2 ms

Accessibility Review

proto-x.net accessibility score

57

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

proto-x.net 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

High

Page has valid source maps

SEO Factors

proto-x.net SEO score

84

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

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

High

Tap targets are not sized appropriately

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-x.net 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-x.net 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-x.net

Open Graph data is detected on the main page of Proto X. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: