6.1 sec in total
504 ms
5.2 sec
429 ms
Welcome to screentex.ru homepage info - get ready to check Screentex best content right away, or after learning these important things about screentex.ru
Скринтекс чудо ткань Пробиус Биополярная ткань Углеродосодержащая нить (ткань) Углеродная нить (Ткань) Биополе Биоэнергетическое поле Биоэнергетика Аура Screentex Радиоотражающие материалы Электромагн...
Visit screentex.ruWe analyzed Screentex.ru page load time and found that the first response time was 504 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
screentex.ru performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.0 s
49/100
25%
Value18.7 s
0/100
10%
Value6,800 ms
0/100
30%
Value0.004
100/100
15%
Value45.6 s
0/100
10%
504 ms
648 ms
247 ms
371 ms
386 ms
Our browser made a total of 186 requests to load all elements on the main page. We found that 39% of them (73 requests) were addressed to the original Screentex.ru, 31% (57 requests) were made to St6-21.vk.com and 7% (13 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Screentex.ru.
Page size can be reduced by 1.3 MB (21%)
5.9 MB
4.7 MB
In fact, the total size of Screentex.ru main page is 5.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. Only a small number of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 77% of the original size.
Potential reduce by 272.2 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. Obviously, Screentex needs image optimization as it can save up to 272.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 525.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 525.9 kB or 21% of the original size.
Potential reduce by 428.0 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. Screentex.ru needs all CSS files to be minified and compressed as it can save up to 428.0 kB or 44% of the original size.
Number of requests can be reduced by 109 (62%)
177
68
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Screentex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
screentex.ru
504 ms
screentex.ru
648 ms
style.css
247 ms
lightbox.css
371 ms
jquery.fancybox.css
386 ms
swiper.min.css
514 ms
form.css
395 ms
jquery-latest.min.js
28 ms
es5-shims.min.js
524 ms
share.js
842 ms
platform.js
19 ms
jquery-1.10.1.min.js
643 ms
prototype.js
787 ms
scriptaculous.js
374 ms
lightbox.js
390 ms
basket.js
405 ms
jquery.fancybox.js
620 ms
swiper.min.js
764 ms
scripts.js
518 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
245 ms
footer-background.png
125 ms
close.png
125 ms
loading.gif
126 ms
prev.png
127 ms
next.png
175 ms
header_background_left.png
216 ms
header_background_border_right.png
480 ms
header_background.jpg
482 ms
logo.png
482 ms
telegram.png
481 ms
basket.png
483 ms
bask.png
483 ms
menu-background.png
487 ms
menu-line.png
487 ms
lis.png
488 ms
resizer.php
567 ms
resizer.php
536 ms
resizer.php
537 ms
resizer.php
738 ms
resizer.php
738 ms
resizer.php
712 ms
resizer.php
738 ms
resizer.php
712 ms
resizer.php
839 ms
resizer.php
1005 ms
resizer.php
915 ms
resizer.php
963 ms
resizer.php
1065 ms
resizer.php
910 ms
resizer.php
1084 ms
resizer.php
1184 ms
resizer.php
1079 ms
resizer.php
1263 ms
resizer.php
1295 ms
upload.gif
123 ms
GD-bgJx_D80
119 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
50 ms
subscribe_embed
90 ms
widget_community.php
436 ms
resizer.php
1302 ms
resizer.php
1198 ms
postmessageRelay
32 ms
effects.js
1115 ms
builder.js
1183 ms
resizer.php
1293 ms
resizer.php
1352 ms
544727282-postmessagerelay.js
41 ms
rpc:shindig_random.js
14 ms
www-subscribe-embed_split_v0.css
12 ms
www-subscribe-embed_v0.js
19 ms
www-player.css
38 ms
subscribe_button_branded_lozenge.png
29 ms
www-embed-player.js
30 ms
base.js
75 ms
cb=gapi.loaded_0
55 ms
cb=gapi.loaded_0
201 ms
resizer.php
1305 ms
resizer.php
1260 ms
ad_status.js
199 ms
hTLn9eGvHolBoYZEIgYnhFeXt5RSKUh7mTOIAh8Y734.js
142 ms
embed.js
71 ms
resizer.php
1166 ms
resizer.php
1135 ms
resizer.php
1146 ms
resizer.php
1152 ms
m1.jpg
1221 ms
loader_nav21112336040_3.js
355 ms
fonts_cnt.c7a76efe.css
936 ms
lite.6d09ff63.css
722 ms
lang3_2.js
623 ms
c3d11fba.093082a5.js
594 ms
xdm.js
606 ms
base.c26e5b58.css
630 ms
m2.jpg
1230 ms
m3.jpg
1407 ms
m4.jpg
1661 ms
m5.jpg
1671 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
50 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
66 ms
m6.jpg
1359 ms
kapsula.jpg
1412 ms
id
22 ms
cb=gapi.loaded_2
18 ms
shal.jpg
1399 ms
Create
154 ms
border_3.gif
16 ms
subscribe_embed
122 ms
spacer.gif
9 ms
bubbleSprite_3.png
102 ms
bubbleDropR_3.png
111 ms
bubbleDropB_3.png
113 ms
www-subscribe-embed-card_v0.css
6 ms
www-subscribe-embed-card_v0.js
7 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
364 ms
resizer.php
1334 ms
sharf.jpg
1317 ms
ochki.jpg
1465 ms
testform.png
1603 ms
GenerateIT
14 ms
hit
581 ms
watch.js
1 ms
browsers.png
205 ms
upload.gif
90 ms
code.js
786 ms
widget_community_messages.php
190 ms
loader_nav21112336040_3.js
155 ms
community_messages.js
116 ms
vkcom-kit.b9457c14.css
100 ms
vkcom-kit.7c3597b4.js
416 ms
react.6a15a5cc.js
227 ms
vkcom-kit-icons.6494715b.js
227 ms
vkui.1926d43a.js
229 ms
state-management.a46c500d.js
290 ms
architecture-mobx.b1015542.js
409 ms
audioplayer-lib.93b52d88.css
316 ms
audioplayer-lib.18822298.js
408 ms
palette.c6252453.css
311 ms
palette.d4043e4c.js
401 ms
sticker-lib.72942183.css
391 ms
sticker-lib.933743cc.js
402 ms
bootstrap.a54815cb.js
521 ms
core_spa.c7f6a9bc.js
535 ms
common.14f5502d.js
657 ms
f371ea0d.dbc1865d.js
489 ms
782f47a3.38fd93c4.js
508 ms
39820787.4128def5.js
496 ms
fc936a0f.a6371a57.js
577 ms
f3627a66.8147bddf.js
612 ms
emoji.ba9ac3c7.css
588 ms
emoji.9f8d52d9.js
610 ms
7f463667.b3f6bf8c.js
637 ms
ui_common.43d06ff5.css
661 ms
ui_common.78ba6732.js
695 ms
b691fd56.fcad13bf.js
692 ms
ui_media_selector.43d06ff5.css
688 ms
ui_media_selector.d8edf233.js
742 ms
f528815f.082e1657.js
747 ms
upload.ade04c10.js
737 ms
stickers.69dc6c3d.css
770 ms
stickers.632cc4ae.js
773 ms
vkui.25d6bec9.css
877 ms
lang3_0.js
404 ms
widget_community_messages.06a7f227.css
817 ms
tag.js
910 ms
notifier.fcca6e68.css
745 ms
ui_common.54e472db.css
733 ms
ui_media_selector.2e6f2ad1.css
635 ms
openapi.js
642 ms
counter
125 ms
dyn-goal-config.js
248 ms
tracker
140 ms
a2eXqowXwb0bpBsLDKHAHuuYnnbdfGjL6BqmuJ0oEra9gH4_Dv6UuG0zSy1tPeaDsEqt-A.jpg
486 ms
QulWsGFAn5k.png
591 ms
w_chat_icon.png
94 ms
w_chat_logo.png
91 ms
widgets_logo_white.svg
84 ms
chats.png
86 ms
community_messages_widget_small_logo.svg
89 ms
emoji_smile_icon.svg
85 ms
roboto400.woff
180 ms
roboto500.woff
263 ms
roboto300.woff
210 ms
roboto700.woff
206 ms
advert.gif
580 ms
log_event
17 ms
screentex.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
screentex.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
screentex.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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Screentex.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 Screentex.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.
screentex.ru
Open Graph description is not detected on the main page of Screentex. 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: