Tools & Wizards About Us
krilak.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 35

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

krilak.com

Противопожарные системы | Крилак

Page Load Speed

3 sec in total

First Response

354 ms

Resources Loaded

2.4 sec

Page Rendered

188 ms

krilak.com screenshot

About Website

Click here to check amazing Krilak content. Otherwise, check out these important facts you probably never knew about krilak.com

Ассоциация Крилак предлагает комплексные противопожарные системы, которые помогут эффективно защитить от огня производственные и жилые помещения

Visit krilak.com

Key Findings

We analyzed Krilak.com page load time and found that the first response time was 354 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

krilak.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

krilak.com

354 ms

www.krilak.com

386 ms

style.css

114 ms

style.css

218 ms

style.css

218 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 86% of them (74 requests) were addressed to the original Krilak.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (929 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.7 kB (7%)

Content Size

608.0 kB

After Optimization

565.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Krilak.com main page is 608.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 461.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 28.6 kB

  • Original 36.4 kB
  • After minification 33.6 kB
  • After compression 7.8 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 28.6 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 12.7 kB

  • Original 461.2 kB
  • After minification 448.6 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. Krilak images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 105.6 kB
  • After minification 105.6 kB
  • After compression 105.6 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

-29%

Potential reduce by 1.4 kB

  • Original 4.7 kB
  • After minification 4.4 kB
  • After compression 3.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. Krilak.com needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (43%)

Requests Now

82

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

krilak.com

krilak.com

354 ms

www.krilak.com

www.krilak.com

386 ms

style.css

style.css

114 ms

style.css

style.css

218 ms

style.css

style.css

218 ms

style.css

style.css

223 ms

style.css

style.css

225 ms

styles.css

styles.css

224 ms

hot_line.png

hot_line.png

332 ms

fucher.png

fucher.png

325 ms

home.gif

home.gif

334 ms

mail.gif

mail.gif

334 ms

map.gif

map.gif

333 ms

img1.png

img1.png

446 ms

img1.jpg

img1.jpg

434 ms

img2.png

img2.png

439 ms

img2.jpg

img2.jpg

445 ms

img3.png

img3.png

555 ms

img3.jpg

img3.jpg

445 ms

img4.png

img4.png

542 ms

img4.jpg

img4.jpg

547 ms

point.gif

point.gif

556 ms

logo.gif

logo.gif

558 ms

green_line.gif

green_line.gif

558 ms

protivo.png

protivo.png

650 ms

NPO.gif

NPO.gif

657 ms

podrobnee2.gif

podrobnee2.gif

666 ms

prodaction.gif

prodaction.gif

666 ms

OK.gif

OK.gif

669 ms

9d54d45be0e65387a23b4c6dac405705.jpg

9d54d45be0e65387a23b4c6dac405705.jpg

669 ms

2d7dd349523dee7ac2470af74573cfe9.jpg

2d7dd349523dee7ac2470af74573cfe9.jpg

758 ms

23b4ee920ef52a71c5b7a077964c87a1.jpg

23b4ee920ef52a71c5b7a077964c87a1.jpg

765 ms

e49a8dd93a2ef348f1d6c410c1cea9bc.jpg

e49a8dd93a2ef348f1d6c410c1cea9bc.jpg

777 ms

podrobnee.gif

podrobnee.gif

778 ms

ramka.png

ramka.png

785 ms

pic1.jpg

pic1.jpg

785 ms

pic8.jpg

pic8.jpg

866 ms

pic6.jpg

pic6.jpg

767 ms

pic7.jpg

pic7.jpg

788 ms

pic2.jpg

pic2.jpg

678 ms

pic3.jpg

pic3.jpg

680 ms

pic4.jpg

pic4.jpg

680 ms

pic5.jpg

pic5.jpg

756 ms

analytics.js

analytics.js

36 ms

3_0_FFFFFFFF_EFEFEFFF_0_pageviews

3_0_FFFFFFFF_EFEFEFFF_0_pageviews

668 ms

tag.js

tag.js

929 ms

call.tracker.js

call.tracker.js

332 ms

hit

hit

273 ms

pic12.jpg

pic12.jpg

745 ms

collect

collect

26 ms

collect

collect

31 ms

js

js

64 ms

pic10.jpg

pic10.jpg

791 ms

pic9.jpg

pic9.jpg

793 ms

pic11.jpg

pic11.jpg

679 ms

search.gif

search.gif

752 ms

last_news.gif

last_news.gif

759 ms

6dc303ca4343ad8d2218ed320863249d.jpg

6dc303ca4343ad8d2218ed320863249d.jpg

680 ms

4498e3f6f1eb308945d53b6b5081aba7.jpg

4498e3f6f1eb308945d53b6b5081aba7.jpg

686 ms

005cb0d43f6c010b37370859c9644b9b.jpg

005cb0d43f6c010b37370859c9644b9b.jpg

759 ms

ca5c8a2e9b5e1d5c1abe20ebe6301436.jpg

ca5c8a2e9b5e1d5c1abe20ebe6301436.jpg

760 ms

top_fon.jpg

top_fon.jpg

890 ms

hit

hit

545 ms

green_oval.gif

green_oval.gif

685 ms

ugol_green_top.gif

ugol_green_top.gif

688 ms

green_fon_menu.gif

green_fon_menu.gif

682 ms

strelka.gif

strelka.gif

747 ms

ugol_green_niz.gif

ugol_green_niz.gif

753 ms

market.gif

market.gif

781 ms

cycounter

cycounter

559 ms

punctir.gif

punctir.gif

697 ms

u4_left_bottom.gif

u4_left_bottom.gif

692 ms

u4_left_top.gif

u4_left_top.gif

746 ms

u4_right_bottom.gif

u4_right_bottom.gif

752 ms

u4_right_top.gif

u4_right_top.gif

779 ms

u2_left_bottom.gif

u2_left_bottom.gif

781 ms

u2_left_top.gif

u2_left_top.gif

703 ms

u2_right_bottom.gif

u2_right_bottom.gif

696 ms

u2_right_top.gif

u2_right_top.gif

742 ms

u1_left_bottom.gif

u1_left_bottom.gif

748 ms

u1_left_top.gif

u1_left_top.gif

774 ms

u1_right_bottom.gif

u1_right_bottom.gif

775 ms

u1_right_top.gif

u1_right_top.gif

707 ms

niz_line_green.gif

niz_line_green.gif

700 ms

advert.gif

advert.gif

500 ms

counter2

counter2

127 ms

Accessibility Review

krilak.com accessibility score

35

Accessibility Issues

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

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

krilak.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

krilak.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krilak.com 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 Krilak.com 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.

Social Sharing Optimization

krilak.com

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