6.2 sec in total
508 ms
5.4 sec
288 ms
Welcome to ecotexe.ru homepage info - get ready to check Ecotexe best content for Russia right away, or after learning these important things about ecotexe.ru
Экотекс - домашний текстиль: производство и продажа текстиля оптом
Visit ecotexe.ruWe analyzed Ecotexe.ru page load time and found that the first response time was 508 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ecotexe.ru performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value15.4 s
0/100
25%
Value12.0 s
4/100
10%
Value1,610 ms
12/100
30%
Value0.959
3/100
15%
Value17.4 s
4/100
10%
508 ms
949 ms
66 ms
33 ms
135 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ecotexe.ru, 86% (65 requests) were made to Ecotex.ru and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Ecotex.ru.
Page size can be reduced by 335.1 kB (9%)
3.7 MB
3.4 MB
In fact, the total size of Ecotexe.ru main page is 3.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. 55% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 48.2 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 7.9 kB, which is 13% 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 48.2 kB or 79% of the original size.
Potential reduce by 200.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. Ecotexe images are well optimized though.
Potential reduce by 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.8 kB or 18% of the original size.
Potential reduce by 6.1 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. Ecotexe.ru needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 32% of the original size.
Number of requests can be reduced by 27 (39%)
70
43
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecotexe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
ecotexe.ru
508 ms
ecotex.ru
949 ms
js
66 ms
fbevents.js
33 ms
style.css
135 ms
responsive.css
255 ms
owl.carousel.min.js
355 ms
scripts.js
484 ms
style.css
358 ms
style.css
358 ms
style.css
363 ms
style.css
371 ms
style.css
465 ms
style.css
474 ms
style.css
474 ms
styles.css
480 ms
core.js
736 ms
dexie3.bundle.js
701 ms
core_ls.js
592 ms
core_fx.js
591 ms
core_frame_cache.js
598 ms
protobuf.js
727 ms
model.js
711 ms
pull.client.js
851 ms
js
48 ms
analytics.js
14 ms
collect
12 ms
reset.css
586 ms
owl.carousel.css
685 ms
icons.css
697 ms
ba.js
285 ms
project-logo.svg
122 ms
project-logo-mobile.svg
118 ms
login-2.png
119 ms
q81kehpqvg459oj5dppusvawhlscutst.jpg
239 ms
z074zjepcrphn4m2c2tos5de0evg1jcc.jpg
241 ms
bfb715a105ca413a0a35a832bfb7ee00.jpg
122 ms
93m4h9rsbe0pxqafm619frd4a3s5t6ew.jpg
352 ms
wybfqwpa58zr64mojwr8bdhy0uaq5zd4.jpg
361 ms
nudhtw89m4w29ahhiqgzsx65gm2lc6rm.jpg
469 ms
l21tk6h8kzy2cz33c39rf5cycvxopssf.jpg
359 ms
g5svey91l0v3wcla6iw4e6kx0yf1inbv.jpg
594 ms
jfg3o9fl4plrgnntxu5j4ad47y818f9l.jpg
484 ms
2wrhjqgx9yqmvrbout5iy0wv0wl5pqxt.jpg
592 ms
1uobsgc66szey9cle3msnipff464qn3o.jpg
698 ms
pnx9lyltrtuv0xw58w07oqtd02rht3qc.jpg
826 ms
c7xryw7lf602p2e3lfsjif5drk1eazv6.jpg
712 ms
35fjosk0q7nsdclbwbza5v6ojvdvbf45.jpg
3050 ms
isc3sac8dnqwb5fomawe0or71cx6r150.png
941 ms
3yh6vli8ti5rq6nag7jx7cx2eld2dtam.jpg
713 ms
k159qg9nm4lgtj31kds45glr2b6d92o1.jpg
817 ms
5b9cn0mn2fz071m3ajq6vzh95d2y7t90.png
835 ms
enbmpzxjqnbtuzbv7iqnx3d6voxw6ghq.jpg
835 ms
ea755us2ef6gygytn9e35dk5qhqbaq4x.jpg
936 ms
lwj19rmkwbtl9jcluco0pplzi7xjmh4a.jpg
945 ms
jcxt57msjk60t82w3iatj7btm5fl8l0v.jpg
956 ms
uminuu2rms8jktuz4naprr3yzxtzsomt.jpg
955 ms
jqxk5ae9g4kqcn5jm1wppmqypqdvsb0a.jpg
1058 ms
7dkbdj4s73ie3l5i7djmp26ihdw1zyxb.jpg
1060 ms
ad7d964d8b73affab39e98a35408c175.jpg
1069 ms
123fd309d013097bd3f32338054b8e1b.jpg
1078 ms
o0tt4p22ki80qdkzq7u3cyp7ob8eyriy.png
1305 ms
8vpgoobbow9oqklwa6e2gd47lczwuonm.jpg
1179 ms
mjos9k580c7vylz7wmq46idhmi15lyhn.jpg
1182 ms
xtiw1pgxeqwogyz212uhywkc1jhootg9.jpg
1195 ms
i7n32c8k8ccaurzg24qtk27p8hfrgtiv.jpg
1201 ms
3ryvpdvoq2ywjt8t0bo8m761gtm625uh.png
1378 ms
tag.js
838 ms
ProximaNova-Regular.woff
1198 ms
icomoon.ttf
1203 ms
ProximaNova-Light.woff
1216 ms
hy9gksqb18wr26v5itglsox2puhrtep5.jpg
1313 ms
icon-checkmark-circle.svg
1197 ms
bx_stat
192 ms
advert.gif
532 ms
1
134 ms
ecotexe.ru 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
Links do not have a discernible name
ecotexe.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ecotexe.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecotexe.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Ecotexe.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.
ecotexe.ru
Open Graph description is not detected on the main page of Ecotexe. 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: