Tools & Wizards About Us
flamax.ru screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

flamax.ru

FLAMAX | Резервуары и Насосные станции пожаротушения и водоснабжения

Page Load Speed

8.8 sec in total

First Response

445 ms

Resources Loaded

7.7 sec

Page Rendered

707 ms

flamax.ru screenshot

About Website

Click here to check amazing FLAMAX content for Russia. Otherwise, check out these important facts you probably never knew about flamax.ru

Сборные резервуары для воды. Насосные станции водоснабжения и пожаротушения. Проектирование, производство и монтаж. Сервисное обслуживание резервуаров. Гарантия до 10 лет.

Visit flamax.ru

Key Findings

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

Performance Metrics

flamax.ru performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

flamax.ru

445 ms

www.flamax.ru

1750 ms

style.min.css

360 ms

slick.css

363 ms

select2.min.css

381 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 81% of them (52 requests) were addressed to the original Flamax.ru, 5% (3 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Flamax.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (62%)

Content Size

2.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flamax.ru main page is 2.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. 45% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 197.0 kB

  • Original 225.1 kB
  • After minification 138.2 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 86.9 kB, which is 39% 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 197.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 144 B

  • Original 579.6 kB
  • After minification 579.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. FLAMAX images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 779.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 395.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 779.3 kB or 66% of the original size.

CSS Optimization

-89%

Potential reduce by 849.9 kB

  • Original 959.4 kB
  • After minification 814.9 kB
  • After compression 109.5 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. Flamax.ru needs all CSS files to be minified and compressed as it can save up to 849.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (53%)

Requests Now

57

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLAMAX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

flamax.ru

flamax.ru

445 ms

www.flamax.ru

www.flamax.ru

1750 ms

style.min.css

style.min.css

360 ms

slick.css

slick.css

363 ms

select2.min.css

select2.min.css

381 ms

lightgallery.min.css

lightgallery.min.css

487 ms

light-modal.css

light-modal.css

383 ms

dropdown.min.css

dropdown.min.css

595 ms

transition.min.css

transition.min.css

632 ms

main.css

main.css

2090 ms

swiper-bundle.min.css

swiper-bundle.min.css

537 ms

style.css

style.css

610 ms

additional.css

additional.css

669 ms

reservoirs_page.css

reservoirs_page.css

868 ms

owl.carousel.min.css

owl.carousel.min.css

742 ms

owl.theme.default.min.css

owl.theme.default.min.css

729 ms

style.css

style.css

750 ms

styles.css

styles.css

880 ms

template_styles.css

template_styles.css

876 ms

red-logo.svg

red-logo.svg

871 ms

svg-icons-sprite.svg

svg-icons-sprite.svg

953 ms

imgonline-com-ua-Compressed-tvFS3SAvOtpz0Jgg.jpg

imgonline-com-ua-Compressed-tvFS3SAvOtpz0Jgg.jpg

1377 ms

montazh.jpg

montazh.jpg

6057 ms

main-slide-3.webp

main-slide-3.webp

1027 ms

ec55b9b87046cd99d8765005e20790c4.jpg

ec55b9b87046cd99d8765005e20790c4.jpg

997 ms

d192cf5f60fa823c9bcdee823add2631.jpg

d192cf5f60fa823c9bcdee823add2631.jpg

986 ms

167cf54485a845f76312138aa7e56718.jpg

167cf54485a845f76312138aa7e56718.jpg

1144 ms

a4ba26a1cf7023660b079b1b5af3dfe0.jpg

a4ba26a1cf7023660b079b1b5af3dfe0.jpg

1166 ms

8e309a432f5c56dfdb73a98103051a9c.jpg

8e309a432f5c56dfdb73a98103051a9c.jpg

1113 ms

d18bb0b3b5fe95a11914291b54f38bc7.jpg

d18bb0b3b5fe95a11914291b54f38bc7.jpg

1253 ms

rotate_icon.svg

rotate_icon.svg

1241 ms

3d_icon.svg

3d_icon.svg

1236 ms

company-history-photo.jpg

company-history-photo.jpg

1274 ms

mark-weber-logo.svg

mark-weber-logo.svg

1147 ms

form-search-icon.svg

form-search-icon.svg

1150 ms

login-icon.svg

login-icon.svg

1154 ms

close-icon.svg

close-icon.svg

1239 ms

848f0a5018c0975dc8a343187acbb0c8.svg

848f0a5018c0975dc8a343187acbb0c8.svg

1228 ms

27a0df661da06cfb95e068eb7de194b6.svg

27a0df661da06cfb95e068eb7de194b6.svg

1237 ms

640d3e239259401fac93cd91d66c6842.svg

640d3e239259401fac93cd91d66c6842.svg

1237 ms

3adde06ceb1c22fb395173b0761e12fe.svg

3adde06ceb1c22fb395173b0761e12fe.svg

1317 ms

54dd3c9b16f4adfac7a1805b4f3033a2.svg

54dd3c9b16f4adfac7a1805b4f3033a2.svg

1347 ms

088578a308e7f715549585609a4f4e0b.svg

088578a308e7f715549585609a4f4e0b.svg

1311 ms

reserv.svg

reserv.svg

1245 ms

js

js

57 ms

core.min.js

core.min.js

1774 ms

template_22df5052d66f4a8813720254bad56e60_v1.js

template_22df5052d66f4a8813720254bad56e60_v1.js

3188 ms

pump.svg

pump.svg

1329 ms

success-tick-icon.svg

success-tick-icon.svg

1306 ms

Intro-Book.woff

Intro-Book.woff

167 ms

Intro-Regular.woff

Intro-Regular.woff

209 ms

Intro-Bold.woff

Intro-Bold.woff

150 ms

Intro-Bold.woff

Intro-Bold.woff

300 ms

ba.js

ba.js

286 ms

gtm.js

gtm.js

39 ms

tag.js

tag.js

914 ms

js

js

80 ms

analytics.js

analytics.js

29 ms

fbevents.js

fbevents.js

23 ms

collect

collect

34 ms

bx_stat

bx_stat

185 ms

advert.gif

advert.gif

684 ms

sync_cookie_image_decide

sync_cookie_image_decide

139 ms

1

1

147 ms

Accessibility Review

flamax.ru accessibility score

79

Accessibility Issues

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

High

[role]s are not contained by their required parent element

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

flamax.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flamax.ru SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

flamax.ru

Open Graph description is not detected on the main page of FLAMAX. 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: