7.3 sec in total
1.2 sec
5.2 sec
880 ms
Welcome to eldr.ru homepage info - get ready to check Eldr best content for Russia right away, or after learning these important things about eldr.ru
Магазин электронных компонентов «Электродруг». Большой ассортимент, выгодные цены. Купить электронные компоненты и приборы в Москве с бесплатной доставкой при заказе от 20000 руб.
Visit eldr.ruWe analyzed Eldr.ru page load time and found that the first response time was 1.2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eldr.ru performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value9.8 s
0/100
25%
Value18.8 s
0/100
10%
Value2,680 ms
4/100
30%
Value1.439
0/100
15%
Value29.4 s
0/100
10%
1234 ms
750 ms
54 ms
108 ms
216 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 90% of them (107 requests) were addressed to the original Eldr.ru, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Eldr.ru.
Page size can be reduced by 308.3 kB (16%)
1.9 MB
1.6 MB
In fact, the total size of Eldr.ru main page is 1.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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 272.7 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 272.7 kB or 83% of the original size.
Potential reduce by 25.0 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. Eldr images are well optimized though.
Potential reduce by 201 B
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.
Potential reduce by 10.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. Eldr.ru needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 27% of the original size.
Number of requests can be reduced by 67 (58%)
116
49
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eldr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
eldr.ru
1234 ms
www.eldr.ru
750 ms
gtm.js
54 ms
ui.design-tokens.css
108 ms
ui.font.opensans.css
216 ms
main.popup.bundle.css
316 ms
template_7cc56da4372cc30ecd9802ac95113ddf_v1.css
337 ms
jquery.fancybox-1.3.1.css
336 ms
core.js
648 ms
dexie3.bundle.js
550 ms
core_ls.js
343 ms
core_fx.js
419 ms
core_frame_cache.js
442 ms
protobuf.js
663 ms
model.js
451 ms
rest.client.js
523 ms
pull.client.js
555 ms
jquery-1.12.4.min.js
676 ms
main.popup.bundle.js
732 ms
jquery.min.1.9.1.js
660 ms
forma.js
674 ms
slides.min.jquery.js
753 ms
script.js
761 ms
jquery.carouFredSel-5.6.4-packed.js
764 ms
jquery.cookie.js
770 ms
jquery.slideViewerPro.1.5.js
784 ms
jquery.timers.js
834 ms
jquery.fancybox-1.3.1.pack.js
859 ms
swfobject.min.js
867 ms
newyear.js
870 ms
script.js
873 ms
script.js
893 ms
script.js
937 ms
script.js
965 ms
script.js
975 ms
script.js
977 ms
main.css
979 ms
require.min.js
1002 ms
custom.css
1044 ms
responsive.css
995 ms
responsive.js
888 ms
ba.js
300 ms
analytics.js
16 ms
app.js
114 ms
collect
52 ms
collect
74 ms
tag.js
964 ms
blackbg.png
138 ms
xxx.jpg
137 ms
otpr.png
136 ms
bg.jpg
138 ms
371225.png
445 ms
logo.png
159 ms
cart.png
211 ms
phone.png
213 ms
input.png
218 ms
submit.png
218 ms
z59y6yyglxu0gxaxcfppwg4ujdd7exey.png
266 ms
iut8c798z7eczpjkoyictbxhnuy0zasa.png
315 ms
rdvmy0hznowkiksk07n5rnqqm31j1umf.png
320 ms
1sfolxcl3aq6ngfbmams7l8p6u7t205i.png
336 ms
lwbaizr1a4li3fu8gqe2xgxetfme4mgw.png
330 ms
80xvblr7i5j1xst6yluyvi7t2ate6su0.png
374 ms
ssnu23mcb621yj2z0args208tren8omo.png
418 ms
aqyf91k1rlll2kl44f6jky8mcixesgej.png
427 ms
znunnw9iswp31a2fvsw6sb22rge63fdd.png
442 ms
6iql32u3q2hk7lf9oc5z5ldf0892v11h.png
443 ms
vurqncstns98xl365zjjqm8ptwch4akd.png
481 ms
0dbdtyww2z3tnjagha2c64cqzum2mp5s.png
522 ms
jltnwuf4xw1yp10tch34rw5jtkz6egcx.png
534 ms
mi8ryfscojuyy927v8njjs3vpf6eyv7n.png
548 ms
jt2vw00doh22mfah4ufnl53qno2vnsxz.png
673 ms
l3iah9fyvc7eu3l999xshv89qmy13xxj.png
548 ms
nzjnugzi9egsjyvav0kk5kyhu47sfxxv.png
587 ms
3e3bn089jnmv9ytd9xgbqmc3m52jknrg.png
626 ms
70xh8jcvcjiouy9m8wwi9rcglohqxi9b.png
640 ms
44l65iwo7y0h8e7gch3kcboifmt67t8u.png
656 ms
kv3kj4uj28qzo8zatmitu7rxndqacfzq.png
654 ms
7mmf2dq2pihijelxrqnbdvyimtckj7nw.png
694 ms
f26edcbf235145d4f42218806147699b.jpg
712 ms
77adcb7a733b4a33561e96a793407090.jpg
727 ms
js
105 ms
cf547a3ccf9a9c271b3c5f38b610e197.JPG
741 ms
76679139f8a86196c6d9ec6c5b737ba1.JPG
710 ms
hit
543 ms
jquery.form.min.js
652 ms
jquery.mask.min.js
670 ms
baseform.min.js
705 ms
a74feff716c807d0c924295e27f1593a.JPG
703 ms
fc3b8862b14358112edae9923cf273d0.JPG
719 ms
bx_stat
190 ms
catmenu.php
721 ms
7abe17845d7d7cec5935257ebec92292.jpg
688 ms
9fadb09f3ba852885c845f70f8bb73ea.jpg
699 ms
3392cabd4e60b05cbbd01e3014d07b03.jpeg
1071 ms
nhejliislumijg4e2cv5t5yc39bpf2fl.jpg
776 ms
um3o3hfhwzhzeuzt6bpm0u8gav9ljohb.jpg
728 ms
2255c3d5b34946eba94b4146b7d86ab1.jpg
724 ms
967975f52826cc9fb5619e7931662187.jpg
713 ms
7qap9barv9vvxyn4gi5kx5shz9igm95f.jpg
707 ms
4r0mx1socpc4emq0h10dz7ktgc1zlw3q.jpg
702 ms
polo2.jpg
684 ms
str.jpg
691 ms
cat.jpg
690 ms
pp.jpg
692 ms
slblock.jpg
739 ms
slblock.jpg
727 ms
footer.jpg
705 ms
polo3.jpg
707 ms
polo.jpg
692 ms
slbg.jpg
745 ms
bx_loader.gif
737 ms
l.png
711 ms
r.png
706 ms
noconflict.js
565 ms
advert.gif
694 ms
jquery.min.js
114 ms
sync_cookie_image_decide
145 ms
GNB25GxqNx
225 ms
eldr.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
eldr.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
eldr.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eldr.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 Eldr.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.
eldr.ru
Open Graph description is not detected on the main page of Eldr. 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: