7.6 sec in total
506 ms
6.5 sec
599 ms
Click here to check amazing Zetms content. Otherwise, check out these important facts you probably never knew about zetms.ru
Компания ZETLAB разрабатывает и производит, контрольно-измерительное оборудование, сейсмостанции, цифровые тензометрические датчики, вибродатчики
Visit zetms.ruWe analyzed Zetms.ru page load time and found that the first response time was 506 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zetms.ru performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value26.9 s
0/100
25%
Value17.6 s
0/100
10%
Value1,820 ms
9/100
30%
Value0.389
26/100
15%
Value30.7 s
0/100
10%
506 ms
773 ms
823 ms
642 ms
536 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Zetms.ru, 34% (27 requests) were made to Zetlab.ru.images.1c-bitrix-cdn.ru and 27% (21 requests) were made to Zetlab.ru.css.1c-bitrix-cdn.ru. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Zetlab.ru.images.1c-bitrix-cdn.ru.
Page size can be reduced by 1.2 MB (31%)
3.9 MB
2.7 MB
In fact, the total size of Zetms.ru main page is 3.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. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 33.1 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.1 kB or 76% of the original size.
Potential reduce by 246.5 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. Zetms images are well optimized though.
Potential reduce by 794.3 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 794.3 kB or 81% of the original size.
Potential reduce by 156.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. Zetms.ru needs all CSS files to be minified and compressed as it can save up to 156.0 kB or 83% of the original size.
Number of requests can be reduced by 21 (29%)
73
52
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zetms. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
zetms.ru
506 ms
www.zetlab.ru
773 ms
jquery-1.8.0.js
823 ms
template_32eec20c540b32161e120b6f121a4842.css
642 ms
template_2d151b400be0314e985ac6ed7e528866.js
536 ms
jquery-ui-1.10.3.custom.js
932 ms
jquery.carouFredSel-6.2.1-packed.js
633 ms
lightbox.js
547 ms
jquery.uniform.min.js
546 ms
ajaxForm.js
717 ms
hash.js
644 ms
useful.lib.js
644 ms
validate.lib.js
729 ms
scripts.js
758 ms
lightbox.css
541 ms
jquery.popup.css
540 ms
uniform.default.css
540 ms
jquery.activity.min.js
468 ms
ajaxblock.js
753 ms
20603
238 ms
ba.js
235 ms
spread.php
171 ms
seperate_header.png
579 ms
close.png
114 ms
loading.gif
120 ms
prev.png
117 ms
next.png
119 ms
background.jpg
281 ms
user_login.png
282 ms
basket.png
288 ms
search.png
289 ms
FB.png
460 ms
VK.png
828 ms
ODN.png
308 ms
tweet.png
314 ms
inst.jpg
313 ms
blur_small.png
254 ms
blur_big.png
301 ms
zetlab_logo.jpg
633 ms
73a5d10c2a2e40061d806ac0fc9743fd.png
937 ms
top_plajka.png
520 ms
066ee072c6f50e1e33e8ed716850cce0.png
3883 ms
6d2bef313ab4f1435156a7077f9a7e1e.png
3166 ms
bec0ff318a5b60c88ffd4f719830109c.png
1194 ms
af3697623c83ea7d72c1bb8c243ca3bc.png
2423 ms
f55d45f898669a0bccefd5fe06bb6b8a.png
1628 ms
7b03faf66d27d75746e5e22871923b65.png
1538 ms
024fa7bcf6b614de871fa0dce25140d2.png
1696 ms
d5c6ceb237ebb08571fe4c39c2d78139.png
3463 ms
cee149bb6554a71dda7b1232573e2278.jpg
1743 ms
fe3ed57d727de1c9b86aaf572bac59dc.jpg
1825 ms
5820acaef0f60b41304a751b47051ee2.jpg
1872 ms
8e961e4b5e9adbd2856e754362d1da85.jpg
1953 ms
c7aafe2f4584190bca5e634249253d02.jpg
2117 ms
91ac515bf8bcaa811a9c7ebda77aac3e.jpg
2093 ms
1aa2888cf390bad6a69a144069c48269.jpg
3091 ms
7e178e975275cac6505550a7abfe9ec9.jpg
3308 ms
94ed9ca6a6357b80970e2bfb943dced8.jpg
2646 ms
b09e96365d8cb68b9ad4050db69000d6.jpg
2840 ms
79ef4991126a6f34055b66991a79d8cf.png
2961 ms
48b56a364482cb2b2c34da5e63e09c7e.jpg
3117 ms
923f5f527a59cf043a4fa763c2f7015d.jpg
3457 ms
catalog.png
4158 ms
pt_sans.svg
2123 ms
star.png
456 ms
star.png
3695 ms
hit
971 ms
freesetlightc.svg
1572 ms
widget_ru_RU.js
249 ms
watch.js
1 ms
analytics.js
158 ms
maska.png
212 ms
arrow_up.png
215 ms
bx_stat
1702 ms
paging_slider.png
170 ms
paging_slider_active.png
181 ms
collect
96 ms
collect
175 ms
print.css
139 ms
zetms.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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.
zetms.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
zetms.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use legible font sizes
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zetms.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Zetms.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
zetms.ru
Open Graph description is not detected on the main page of Zetms. 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: