Tools & Wizards About Us
fasel.ru screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fasel.ru

Фасадный декор из пенопласта (пенополистирола) купить по доступной цене

Page Load Speed

5.1 sec in total

First Response

487 ms

Resources Loaded

3.8 sec

Page Rendered

801 ms

fasel.ru screenshot

About Website

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

Производство и продажа фасадного декора из пенопласта (пенополистирола), доставка и монтаж на фасады домов. Москва, доступные цены. Звоните!

Visit fasel.ru

Key Findings

We analyzed Fasel.ru page load time and found that the first response time was 487 ms and then it took 4.6 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

fasel.ru performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value3,420 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

fasel.ru

487 ms

fasel.ru

492 ms

www.fasel.ru

472 ms

www.fasel.ru

516 ms

css

47 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 74% of them (56 requests) were addressed to the original Fasel.ru, 9% (7 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fasel.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.7 kB (3%)

Content Size

2.3 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fasel.ru main page is 2.3 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 46.7 kB

  • Original 56.9 kB
  • After minification 48.8 kB
  • After compression 10.3 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 8.1 kB, which is 14% 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 46.7 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 30.9 kB

  • Original 2.0 MB
  • After minification 2.0 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. Fasel images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

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

-0%

Potential reduce by 15 B

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 13.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. Fasel.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (16%)

Requests Now

62

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fasel.ru

fasel.ru

487 ms

fasel.ru

fasel.ru

492 ms

www.fasel.ru

www.fasel.ru

472 ms

www.fasel.ru

www.fasel.ru

516 ms

css

css

47 ms

250 ms

jquery.min.js

jquery.min.js

463 ms

api.js

api.js

43 ms

548 ms

scripts.js

scripts.js

355 ms

all.min.css

all.min.css

360 ms

watch.js

watch.js

0 ms

header-bg2.jpg

header-bg2.jpg

706 ms

logo.png

logo.png

184 ms

icon-phone.png

icon-phone.png

184 ms

87c51c8b_a42f2f42.png

87c51c8b_a42f2f42.png

182 ms

c065665b_a42f2f42.png

c065665b_a42f2f42.png

183 ms

fd054feb_a42f2f42.png

fd054feb_a42f2f42.png

319 ms

4f2593fb_a42f2f42.png

4f2593fb_a42f2f42.png

319 ms

7245ba4b_a42f2f42.png

7245ba4b_a42f2f42.png

318 ms

35e5c09b_a42f2f42.png

35e5c09b_a42f2f42.png

318 ms

0885e92b_a42f2f42.png

0885e92b_a42f2f42.png

429 ms

pluses-bg.jpg

pluses-bg.jpg

430 ms

fasel-primer.png

fasel-primer.png

1024 ms

pluses-1.png

pluses-1.png

427 ms

pluses-2.png

pluses-2.png

424 ms

pluses-3.png

pluses-3.png

539 ms

pluses-4.png

pluses-4.png

546 ms

pluses-5.png

pluses-5.png

547 ms

pluses-6.png

pluses-6.png

547 ms

icon1.png

icon1.png

653 ms

icon2.png

icon2.png

663 ms

icon3.png

icon3.png

661 ms

icon4.png

icon4.png

665 ms

icon5.png

icon5.png

769 ms

icon6.png

icon6.png

777 ms

b79f6b1f_780af0eb.jpg

b79f6b1f_780af0eb.jpg

780 ms

73ffe618_780af0eb.jpg

73ffe618_780af0eb.jpg

782 ms

19aba54a_780af0eb.jpg

19aba54a_780af0eb.jpg

821 ms

d7d82431_780af0eb.jpg

d7d82431_780af0eb.jpg

884 ms

ae5d66b3_780af0eb.jpg

ae5d66b3_780af0eb.jpg

1003 ms

61ecd0f0_780af0eb.jpg

61ecd0f0_780af0eb.jpg

898 ms

questions-bg.jpg

questions-bg.jpg

900 ms

019f707a_ed09763c.jpg

019f707a_ed09763c.jpg

939 ms

8825e650_ed09763c.jpg

8825e650_ed09763c.jpg

996 ms

247cb539_ed09763c.jpg

247cb539_ed09763c.jpg

1016 ms

recaptcha__ru.js

recaptcha__ru.js

147 ms

v5.png

v5.png

754 ms

1ddb1071_df32e11f.jpg

1ddb1071_df32e11f.jpg

969 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVc.ttf

134 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVc.ttf

145 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVc.ttf

246 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVc.ttf

280 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVc.ttf

334 ms

2c330aec_df32e11f.jpg

2c330aec_df32e11f.jpg

1006 ms

analytics.js

analytics.js

212 ms

fa-solid-900.woff

fa-solid-900.woff

1163 ms

fa-regular-400.woff

fa-regular-400.woff

940 ms

8a440158_df32e11f.jpg

8a440158_df32e11f.jpg

959 ms

4fe33fd6_df32e11f.jpg

4fe33fd6_df32e11f.jpg

958 ms

fallback

fallback

73 ms

fallback

fallback

86 ms

e9943462_df32e11f.jpg

e9943462_df32e11f.jpg

826 ms

d87c2eff_df32e11f.jpg

d87c2eff_df32e11f.jpg

862 ms

logo-footer.png

logo-footer.png

919 ms

visa.png

visa.png

1056 ms

collect

collect

23 ms

fallback__ltr.css

fallback__ltr.css

7 ms

css

css

22 ms

js

js

77 ms

logo_48.png

logo_48.png

11 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

6 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

5 ms

sber.png

sber.png

836 ms

mir.png

mir.png

833 ms

master.png

master.png

871 ms

Accessibility Review

fasel.ru accessibility score

70

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

fasel.ru best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fasel.ru SEO score

90

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

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

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fasel.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Fasel.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

fasel.ru

Open Graph data is detected on the main page of Fasel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: