7.2 sec in total
430 ms
6.2 sec
499 ms
Welcome to brozex.com homepage info - get ready to check BROZEX best content for Russia right away, or after learning these important things about brozex.com
«Брозэкс» — крупный производитель и поставщик строительных и отделочных материалов в Екатеринбурге и Свердловской области для оптовых покупателей.
Visit brozex.comWe analyzed Brozex.com page load time and found that the first response time was 430 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
brozex.com performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value14.8 s
0/100
25%
Value11.7 s
4/100
10%
Value2,710 ms
3/100
30%
Value0.236
53/100
15%
Value14.1 s
9/100
10%
430 ms
615 ms
1920 ms
34 ms
22 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Brozex.com, 86% (100 requests) were made to Brozex.ru and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Brozex.ru.
Page size can be reduced by 6.2 MB (72%)
8.7 MB
2.4 MB
In fact, the total size of Brozex.com main page is 8.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.9 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 300.3 kB, which is 26% 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 1.0 MB or 91% of the original size.
Potential reduce by 5.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, BROZEX needs image optimization as it can save up to 5.1 MB or 74% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 105.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 105.9 kB or 18% of the original size.
Potential reduce by 22.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. Brozex.com needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 32% of the original size.
Number of requests can be reduced by 40 (36%)
111
71
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BROZEX. 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 12 to 1 for CSS and as a result speed up the page load time.
brozex.com
430 ms
brozex.com
615 ms
brozex.ru
1920 ms
css2
34 ms
jquery.fancybox.min.css
22 ms
css2
52 ms
jquery.min.js
29 ms
jquery.fancybox.min.js
27 ms
ui.design-tokens.css
429 ms
ui.font.opensans.css
430 ms
main.popup.bundle.css
447 ms
jquery.toast.min.css
449 ms
nouislider.min.css
450 ms
brozex.css
751 ms
style.css
571 ms
style.css
573 ms
template_styles.css
596 ms
core.js
1045 ms
protobuf.js
898 ms
model.js
713 ms
core_promise.js
714 ms
rest.client.js
743 ms
pull.client.js
855 ms
jquery-1.12.4.min.js
1001 ms
main.popup.bundle.js
1041 ms
core_fx.js
898 ms
currency-core.bundle.js
999 ms
core_currency.js
1072 ms
jquery.toast.min.js
1072 ms
script.js
1142 ms
script.js
1143 ms
script.js
1190 ms
moxie.app.js
1192 ms
tmpl.js
1194 ms
brozex.js
1348 ms
nouislider.min.js
1285 ms
main.js
1286 ms
rating_likes.js
1337 ms
jquery.inputmask.min.js
1342 ms
phoneorlogin.js
1343 ms
script.js
1428 ms
script.js
1429 ms
ba.js
294 ms
tag.js
931 ms
logo-brozex-color.svg
205 ms
1bv68kga0p91xr34mvshqnhw8mwhh2dg.png
288 ms
1n56ix44e7l3d136e68w7qx4t71yo661.png
369 ms
2lsq2x4wljyasf4snzoztlukg1yug5bu.png
369 ms
n31ik3eapq2ktdbpm1u94igsyldwg3o3.png
450 ms
nm0bwmvdn54ac6124djfdzqal0548lle.png
368 ms
d35uzj5y0j95kotocqvhc8uq5g046r3a.png
432 ms
yghimsr9iltcefumtzak3chxgv63grij.png
717 ms
fslb03my56746cg4qj705m94rzz9817q.png
926 ms
hayfk0sqzexsx1m7zmvutdfsu1n9u75v.png
748 ms
c03q1adle2oasbg0q3y0m363or1hmtxk.png
604 ms
27sunwqfidef3abu32o8wf64714sffvn.png
721 ms
npf10fwmx1tboi0wovnr266mqz1zrr6f.png
927 ms
26x1660onx0bs0bqwkbs4qt3lc7d2ivi.png
755 ms
t93armqobzc2j2u61v90nfewhs617gcj.png
922 ms
s2ug6ouv2ntxy7cq94e4ro7ihfbxga6u.png
924 ms
zgtzdm59oc5hfchquy4syox8a6b6qcfo.png
926 ms
njo4kkhkc4ot707r2l3pyp1u2qj5z6zd.png
928 ms
c2zwlbpt7hgph1i3omu2cz8vvtmk89ra.png
1018 ms
te14e0p3wwi4at6f9fxsqbwt9el2xpj2.png
1018 ms
9ter7xv0z5gnr2l1wxsyoyj3fkfsbgt5.png
1042 ms
v62i2opxgqmzcc0ys9oom1m5nkbc6ccl.png
1049 ms
wupim27ez0nc81g3b6afvk1csk63vq2s.png
1051 ms
mbym5pbtof3glpaylh7i49689szpo7ud.png
1057 ms
5fngqxatz0pn47iy99gokv4d0kv5jo34.png
1154 ms
ns1mduqf0odfxv24eole2zcemckdcanl.png
1154 ms
tcocps50mg5xy0stcsprlavnsovdzx0s.png
1190 ms
0uitxn8d7kv07t1004lculorguh34iyk.png
1197 ms
5sqky36f9hbyp2aerixwbtm74x105w7d.png
1200 ms
lm09p736lm7wvmqmkqg30pubre7fj10r.png
1207 ms
frv8e6jysn70tc1e53xaygm2qz3hey07.png
1301 ms
aldkue10ma8g1kshyhf2elei3outd3bk.png
1297 ms
g0sdt9yipxyw51cdxsmjs8ldgtnvn02k.png
1338 ms
fz927h3csmozbc7z2rzljuwjnqdyevv5.png
1346 ms
6ff9x323nrhvovr8wz5kck3v78qz73na.png
1348 ms
client.js
761 ms
flqusz4c4ad6nsz0tw0uoj2459rtqsyy.png
1356 ms
font
115 ms
siptg57p8lo3nrxh5dlw001p51vj2sfd.png
1234 ms
sp5ie94epdcgdpwb0ms5eujauak813uv.jpg
1153 ms
bx_stat
194 ms
z3q3pi255tpod7vm7cijk60iemsiokia.jpg
1122 ms
1j7x2wskuls0pt7l90ubpjchg5sbd8uv.png
1130 ms
MotorCyr.woff
1132 ms
yzyakqpj9gnmfoov651c5vzzf79qblj1.jpg
1103 ms
oukhoqybdyya7c7bp2l6y5cumgcg3jdk.jpg
1134 ms
yal0rwbt5cyt1oaqi85sbmckruhhda75.jpg
979 ms
s961luzpy7g8p8kr3iywdcpgqiicyd0p.jpg
919 ms
m7z7qlmxhxve0za7o7samzxv69d99dq5.jpg
925 ms
7mtgs3ai0xerl410vf1g41r3yxemjk8x.png
901 ms
6qowlvakqd133cwycstc669umkbldlb1.jpg
901 ms
csc-event
592 ms
_health
510 ms
53kyy2czileffmtlu0wadsdwo0epgbc1.jpg
802 ms
ba2q7lqwh65lifis2vpxqu9it33150lz.jpg
803 ms
e4pmymm9ib0ahlcwmwqx0jtvrpbu5gkm.jpg
862 ms
jtsarntevfr19uo4ui6428bi4zp578lu.jpg
870 ms
zh1sj5nz255jpd3czm3tvwxjdufs971q.jpg
872 ms
ct6n5bkgvmcjfji104z2onovj67ov27s.jpg
881 ms
0x5jc17g35fwg5k3470pyjbsp0mcw2ek.jpg
867 ms
y1ivz9wn132rymw5okoj6d3ww3kmhj4p.jpg
864 ms
advert.gif
693 ms
jjoec08m72j19qt2wqlso231cvwh0i3p.jpg
895 ms
xudlrxpxtqxehhkd3vqukb5c5z5oh4zk.jpg
895 ms
hq9jkcxty3ne6rlrdecgd0y37puj40xq.jpg
897 ms
t4klos3ytpv2wnyrf2t15hakjq15zwsk.png
901 ms
b6nb2pp84fx0fvajl0ymclxn5e82kw6t.jpg
858 ms
logo-brozex-white.svg
853 ms
icons-sprite.svg
893 ms
category-populary-bg.png
895 ms
social-sprite.svg
897 ms
sync_cookie_image_decide
142 ms
brozex.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
brozex.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
brozex.com 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 Brozex.com 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 Brozex.com 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.
brozex.com
Open Graph description is not detected on the main page of BROZEX. 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: