6.1 sec in total
907 ms
4.6 sec
591 ms
Visit savia.ru now to see the best up-to-date Savia content for Russia and also check out these interesting facts you probably never knew about savia.ru
ООО «НПП Спецавиа» производит теплоносители, антифризы, тосолы, растворы для промывки и другие специальные жидкости.
Visit savia.ruWe analyzed Savia.ru page load time and found that the first response time was 907 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
savia.ru performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value10.0 s
0/100
25%
Value17.5 s
0/100
10%
Value11,770 ms
0/100
30%
Value0.728
6/100
15%
Value23.8 s
1/100
10%
907 ms
158 ms
277 ms
553 ms
406 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 71% of them (54 requests) were addressed to the original Savia.ru, 4% (3 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Savia.ru.
Page size can be reduced by 209.3 kB (8%)
2.6 MB
2.4 MB
In fact, the total size of Savia.ru main page is 2.6 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. 80% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.0 kB or 83% of the original size.
Potential reduce by 123.9 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. Savia images are well optimized though.
Potential reduce by 14.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Savia.ru has all CSS files already compressed.
Number of requests can be reduced by 34 (51%)
67
33
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Savia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
savia.ru
907 ms
page_5086a5c97e2558e044bc7706bd8a6110_v1.css
158 ms
template_a8e90a5f6d1607fb2d555698c519c188_v1.css
277 ms
core.min.js
553 ms
kernel_main_v1.js
406 ms
kernel_main_polyfill_customevent_v1.js
286 ms
dexie.bitrix.bundle.min.js
412 ms
core_ls.min.js
293 ms
core_frame_cache.min.js
398 ms
template_0ce4b0a67259aa8d009ced2c228f42fb_v1.js
411 ms
css
187 ms
jquery-latest.min.js
736 ms
jquery.form.js
520 ms
util.js
531 ms
query.js
538 ms
waiting.js
534 ms
form.js
743 ms
ajax-block.js
749 ms
init.js
750 ms
bjqs-1.3.js
751 ms
script.js
753 ms
jquery.fancybox.js
764 ms
jquery.fancybox.css
830 ms
font-awesome.min.css
832 ms
api.js
179 ms
mobile.css
836 ms
add-leads.css
838 ms
js
208 ms
video-js.css
183 ms
video.min.js
230 ms
ba.js
187 ms
recaptcha__en.js
179 ms
analytics.js
246 ms
1logo.png
417 ms
slider0.jpg
992 ms
slider1.jpg
440 ms
slider2.jpg
561 ms
slider3.jpg
558 ms
slider4-1.jpg
585 ms
pdf.png
432 ms
1.jpg
992 ms
2.jpg
985 ms
3.jpg
1253 ms
4.jpg
963 ms
5.jpg
982 ms
6.jpg
985 ms
7.jpg
985 ms
8.jpg
986 ms
9.jpg
986 ms
10.jpg
988 ms
11.jpg
990 ms
12.jpg
991 ms
13.jpg
1273 ms
14.jpg
1268 ms
gk.png
1269 ms
tag.js
988 ms
phone.png
1266 ms
slider-overlay.png
1230 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf
365 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVc.ttf
365 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf
366 ms
s-m.png
850 ms
collect
426 ms
fire2-teplonosit2.png
324 ms
fire-3-avtozap.png
429 ms
T0LilglXX7dmFVxLnq5U0vYATHFk3zX3BOisoQHNDFDeZnqKDy9hRNawN7Vh727hFzcJ5c8TILrKZfH7tIPxAFP0BpLeJPA==
6 ms
footer-bg.png
163 ms
init
906 ms
mango.js
378 ms
bx_stat
82 ms
fontawesome-webfont.woff
262 ms
advert.gif
495 ms
mango.js
824 ms
sync_cookie_image_decide
137 ms
1
145 ms
addVisit
378 ms
savia.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
savia.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
savia.ru SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Savia.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 Savia.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.
savia.ru
Open Graph description is not detected on the main page of Savia. 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: