Tools & Wizards About Us
pea.ru screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

pea.ru

Производство и поставка промышленного электрооборудования

Page Load Speed

5.8 sec in total

First Response

433 ms

Resources Loaded

5.1 sec

Page Rendered

261 ms

pea.ru screenshot

About Website

Visit pea.ru now to see the best up-to-date Pea content for Russia and also check out these interesting facts you probably never knew about pea.ru

НПО Промэлектроавтоматика - комплектование, монтаж, наладка и сервисное обслуживание высоковольтного и низковольтного оборудования на промышленных предприятиях различных отраслей производства, граждан...

Visit pea.ru

Key Findings

We analyzed Pea.ru page load time and found that the first response time was 433 ms and then it took 5.4 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

pea.ru performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value2,610 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

pea.ru

433 ms

1258 ms

stylesheet_77e1914664.css

85 ms

stylespages.css

172 ms

styles.css

241 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 70% of them (78 requests) were addressed to the original Pea.ru, 5% (5 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Pea.ru.

Page Optimization Overview & Recommendations

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

Content Size

721.6 kB

After Optimization

642.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pea.ru main page is 721.6 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. 60% of websites need less resources to load. Images take 355.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 62.7 kB

  • Original 82.0 kB
  • After minification 75.9 kB
  • After compression 19.3 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 62.7 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 kB

  • Original 355.4 kB
  • After minification 353.9 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. Pea images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 11.0 kB

  • Original 211.7 kB
  • After minification 211.3 kB
  • After compression 200.8 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

-6%

Potential reduce by 4.2 kB

  • Original 72.5 kB
  • After minification 72.5 kB
  • After compression 68.3 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. Pea.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 50 (50%)

Requests Now

100

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pea.ru

pea.ru

433 ms

1258 ms

stylesheet_77e1914664.css

stylesheet_77e1914664.css

85 ms

stylespages.css

stylespages.css

172 ms

styles.css

styles.css

241 ms

jquery-1.4.4.min-71249a7f7be37e961510c082a5c21cb6.js

jquery-1.4.4.min-71249a7f7be37e961510c082a5c21cb6.js

338 ms

nice_scroll-ad6dee7a6b71997954de7aaf2ab94a61.js

nice_scroll-ad6dee7a6b71997954de7aaf2ab94a61.js

346 ms

highslide-with-html-a4b52b2b15e9605bb33a0501c84af3e4.js

highslide-with-html-a4b52b2b15e9605bb33a0501c84af3e4.js

351 ms

javascript_bd4d1f63e4-1ae6cf0c22e4039b746b3375229e6758.js

javascript_bd4d1f63e4-1ae6cf0c22e4039b746b3375229e6758.js

251 ms

style.css

style.css

264 ms

js

js

62 ms

index.xml

index.xml

699 ms

styles.css

styles.css

319 ms

addthis_widget.js

addthis_widget.js

23 ms

element.js

element.js

52 ms

custom-5f156bab2b4fea5ca8bc1576e44cc0fe.js

custom-5f156bab2b4fea5ca8bc1576e44cc0fe.js

333 ms

script-fff9178e99c3a4d13d3d37c5c0375921.js

script-fff9178e99c3a4d13d3d37c5c0375921.js

358 ms

showhide-48de7c100256d477b5aee0e460168dd7.js

showhide-48de7c100256d477b5aee0e460168dd7.js

422 ms

hide_m-835d1c01c5315540d985f24874c6719e.js

hide_m-835d1c01c5315540d985f24874c6719e.js

423 ms

menu-collapsed-b0a6f1fd0df2b3022c4d3c443c17c173.js

menu-collapsed-b0a6f1fd0df2b3022c4d3c443c17c173.js

424 ms

jquery.switchTarget.1.0-b68e66e7391c4e65da1760adc9e199bf.js

jquery.switchTarget.1.0-b68e66e7391c4e65da1760adc9e199bf.js

457 ms

gtm.js

gtm.js

71 ms

cycounter

cycounter

674 ms

top.gif

top.gif

806 ms

logo.jpg

logo.jpg

117 ms

icon_phone1.gif

icon_phone1.gif

117 ms

icon_mail1.gif

icon_mail1.gif

178 ms

icon_home1.gif

icon_home1.gif

178 ms

feedback.gif

feedback.gif

179 ms

main.jpg

main.jpg

263 ms

megalogo.jpg

megalogo.jpg

190 ms

6.jpg

6.jpg

190 ms

7.jpg

7.jpg

202 ms

9.jpg

9.jpg

228 ms

2.jpg

2.jpg

230 ms

3.jpg

3.jpg

274 ms

12.jpg

12.jpg

273 ms

8.jpg

8.jpg

281 ms

5.jpg

5.jpg

310 ms

4.jpg

4.jpg

312 ms

10.jpg

10.jpg

346 ms

14.jpg

14.jpg

356 ms

11.jpg

11.jpg

355 ms

pic_o-m_0.jpg

pic_o-m_0.jpg

599 ms

mega_proect.jpg

mega_proect.jpg

392 ms

mega_sogl.jpg

mega_sogl.jpg

398 ms

mega_servis.jpg

mega_servis.jpg

429 ms

entrance_products_2.jpg

entrance_products_2.jpg

439 ms

electro.jpg

electro.jpg

439 ms

pumps.jpg

pumps.jpg

475 ms

transform.jpg

transform.jpg

480 ms

compensation.jpg

compensation.jpg

512 ms

distrib.jpg

distrib.jpg

521 ms

bartec.jpg

bartec.jpg

522 ms

industrial.jpg

industrial.jpg

557 ms

watch.js

watch.js

2 ms

vmtec.jpg

vmtec.jpg

528 ms

js

js

60 ms

analytics.js

analytics.js

51 ms

bartec.gif

bartec.gif

531 ms

espa.gif

espa.gif

538 ms

honda.gif

honda.gif

506 ms

oez.gif

oez.gif

529 ms

ftg.gif

ftg.gif

533 ms

sdmo.gif

sdmo.gif

566 ms

collect

collect

63 ms

siemens.gif

siemens.gif

504 ms

bartec-logo.gif

bartec-logo.gif

514 ms

electroshop-logo.gif

electroshop-logo.gif

510 ms

espa-logo.gif

espa-logo.gif

537 ms

raychem-logo3.gif

raychem-logo3.gif

541 ms

vmtec-logo3.gif

vmtec-logo3.gif

558 ms

nibe-logo.gif

nibe-logo.gif

537 ms

waterkotte-logo.gif

waterkotte-logo.gif

573 ms

sdmo-logo3.gif

sdmo-logo3.gif

541 ms

aerzen-logo.gif

aerzen-logo.gif

540 ms

_YMaps-ie.css

_YMaps-ie.css

430 ms

_YMaps.js

_YMaps.js

379 ms

li_transparent_white.gif

li_transparent_white.gif

88 ms

back_form_2.jpg

back_form_2.jpg

85 ms

shakti_news.jpg

shakti_news.jpg

85 ms

chekbox.png

chekbox.png

250 ms

hit

hit

507 ms

pix_1.jpg

pix_1.jpg

113 ms

all.js

all.js

962 ms

core.js

core.js

765 ms

marker.gif

marker.gif

92 ms

bg.gif

bg.gif

223 ms

bgtmp2.gif

bgtmp2.gif

97 ms

collect

collect

18 ms

gtm.js

gtm.js

66 ms

ga.js

ga.js

22 ms

js

js

97 ms

shakti_news.jpg

shakti_news.jpg

89 ms

code.js

code.js

883 ms

index.php

index.php

896 ms

__utm.gif

__utm.gif

30 ms

bgtmp2.gif

bgtmp2.gif

189 ms

__utm.gif

__utm.gif

90 ms

dc.js

dc.js

95 ms

chekbox.png

chekbox.png

101 ms

bg.gif

bg.gif

89 ms

bgtmp2.gif

bgtmp2.gif

190 ms

hit

hit

127 ms

counter.js

counter.js

453 ms

jquery.min.js

jquery.min.js

488 ms

sync-loader.js

sync-loader.js

846 ms

counter

counter

144 ms

dyn-goal-config.js

dyn-goal-config.js

292 ms

suggest.js

suggest.js

95 ms

opensearch.js

opensearch.js

201 ms

Accessibility Review

pea.ru accessibility score

68

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.

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

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

Form elements do not have associated labels

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

pea.ru best practices score

42

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

Displays images with incorrect aspect ratio

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

pea.ru SEO score

62

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

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 Pea.ru 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 Pea.ru 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

pea.ru

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