Tools & Wizards About Us
savia.ru screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

savia.ru

Завод НПП Спецавиа - Производство теплоносителей и антифризов

Page Load Speed

5 sec in total

First Response

559 ms

Resources Loaded

4.2 sec

Page Rendered

255 ms

savia.ru screenshot

About Website

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.ru

Key Findings

We analyzed Savia.ru page load time and found that the first response time was 559 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

savia.ru performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

savia.ru

559 ms

savia.ru

877 ms

style.css

138 ms

style.css

275 ms

template_styles.css

414 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 76% of them (57 requests) were addressed to the original Savia.ru, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Savia.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 310.8 kB (9%)

Content Size

3.5 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Savia.ru main page is 3.5 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 67.4 kB

  • Original 79.9 kB
  • After minification 77.6 kB
  • After compression 12.5 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 67.4 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 128.4 kB

  • Original 2.6 MB
  • After minification 2.5 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. Savia images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 77.4 kB

  • Original 756.5 kB
  • After minification 756.5 kB
  • After compression 679.1 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.

CSS Optimization

-55%

Potential reduce by 37.6 kB

  • Original 67.8 kB
  • After minification 62.4 kB
  • After compression 30.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. Savia.ru needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

67

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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 26 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

savia.ru

savia.ru

559 ms

savia.ru

savia.ru

877 ms

style.css

style.css

138 ms

style.css

style.css

275 ms

template_styles.css

template_styles.css

414 ms

core.min.js

core.min.js

559 ms

kernel_main_v1.js

kernel_main_v1.js

596 ms

kernel_main_polyfill_customevent_v1.js

kernel_main_polyfill_customevent_v1.js

422 ms

dexie.bitrix.bundle.min.js

dexie.bitrix.bundle.min.js

601 ms

core_ls.min.js

core_ls.min.js

422 ms

core_frame_cache.min.js

core_frame_cache.min.js

550 ms

template_0ce4b0a67259aa8d009ced2c228f42fb_v1.js

template_0ce4b0a67259aa8d009ced2c228f42fb_v1.js

594 ms

css

css

48 ms

jquery-latest.min.js

jquery-latest.min.js

706 ms

jquery.form.js

jquery.form.js

690 ms

util.js

util.js

694 ms

query.js

query.js

701 ms

waiting.js

waiting.js

701 ms

form.js

form.js

704 ms

ajax-block.js

ajax-block.js

826 ms

init.js

init.js

831 ms

bjqs-1.3.js

bjqs-1.3.js

840 ms

script.js

script.js

841 ms

jquery.fancybox.js

jquery.fancybox.js

846 ms

jquery.fancybox.css

jquery.fancybox.css

845 ms

font-awesome.min.css

font-awesome.min.css

962 ms

api.js

api.js

47 ms

mobile.css

mobile.css

967 ms

add-leads.css

add-leads.css

979 ms

js

js

66 ms

video-js.css

video-js.css

28 ms

video.min.js

video.min.js

38 ms

ba.js

ba.js

311 ms

recaptcha__en.js

recaptcha__en.js

29 ms

js

js

56 ms

analytics.js

analytics.js

25 ms

1logo.png

1logo.png

236 ms

slider6.jpg

slider6.jpg

577 ms

slider0.jpg

slider0.jpg

588 ms

slider1.jpg

slider1.jpg

421 ms

slider2.jpg

slider2.jpg

421 ms

slider3.jpg

slider3.jpg

236 ms

slider4-1.jpg

slider4-1.jpg

440 ms

pdf.png

pdf.png

306 ms

1.jpg

1.jpg

722 ms

2.jpg

2.jpg

840 ms

3.jpg

3.jpg

841 ms

4.jpg

4.jpg

579 ms

5.jpg

5.jpg

850 ms

6.jpg

6.jpg

720 ms

7.jpg

7.jpg

729 ms

8.jpg

8.jpg

857 ms

9.jpg

9.jpg

862 ms

10.jpg

10.jpg

870 ms

11.jpg

11.jpg

981 ms

12.jpg

12.jpg

983 ms

13.jpg

13.jpg

989 ms

14.jpg

14.jpg

997 ms

gk.png

gk.png

1000 ms

tag.js

tag.js

897 ms

phone.png

phone.png

998 ms

search.png

search.png

1109 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf

133 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVc.ttf

208 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf

209 ms

collect

collect

188 ms

s-m.png

s-m.png

964 ms

fire2-teplonosit2.png

fire2-teplonosit2.png

896 ms

fire-3-avtozap.png

fire-3-avtozap.png

904 ms

footer-bg.png

footer-bg.png

878 ms

T0LilglXX7dmFVxLnq5U0vYATHFk3zX3BOisoQHNDFDeZnqKDy9hRNawN7Vh727hFzcJ5c8TILrKZfH7tIPxAFP0BpLeJPA==

T0LilglXX7dmFVxLnq5U0vYATHFk3zX3BOisoQHNDFDeZnqKDy9hRNawN7Vh727hFzcJ5c8TILrKZfH7tIPxAFP0BpLeJPA==

15 ms

bx_stat

bx_stat

188 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

875 ms

advert.gif

advert.gif

671 ms

sync_cookie_image_decide

sync_cookie_image_decide

142 ms

Accessibility Review

savia.ru accessibility score

81

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

savia.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

savia.ru SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: