Tools & Wizards About Us
for.ru screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

for.ru

Конструктор сайтов бесплатный | Конструктор интернет-магазинов

Page Load Speed

7.2 sec in total

First Response

497 ms

Resources Loaded

6.4 sec

Page Rendered

326 ms

for.ru screenshot

About Website

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

Создать сайт своими руками любой тематики, от сайта визитки до интернет магазина, без знания программирования, вы можете с помощью сервиса For.ru

Visit for.ru

Key Findings

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

Performance Metrics

for.ru performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

for.ru

497 ms

for.ru

528 ms

css

28 ms

migrate.css

368 ms

style.css

370 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 94% of them (65 requests) were addressed to the original For.ru, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Cdn.freekassa.ru. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain For.ru.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of For.ru main page is 1.4 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. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.3 kB

  • Original 42.1 kB
  • After minification 40.9 kB
  • After compression 9.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 32.3 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

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

JavaScript Optimization

-1%

Potential reduce by 389 B

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

-5%

Potential reduce by 1.1 kB

  • Original 22.0 kB
  • After minification 22.0 kB
  • After compression 20.9 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. For.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (14%)

Requests Now

63

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

for.ru

for.ru

497 ms

for.ru

for.ru

528 ms

css

css

28 ms

migrate.css

migrate.css

368 ms

style.css

style.css

370 ms

owl.carousel.min.css

owl.carousel.min.css

369 ms

owl.theme.default.min.css

owl.theme.default.min.css

391 ms

s.css

s.css

525 ms

jquery.js

jquery.js

658 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

734 ms

modernizr.js

modernizr.js

758 ms

owl.carousel.min.js

owl.carousel.min.js

761 ms

main.js

main.js

783 ms

big-dark-1.png

big-dark-1.png

199 ms

logo.png

logo.png

423 ms

hdr-toconstr.png

hdr-toconstr.png

367 ms

flags.png

flags.png

507 ms

top-bg.png

top-bg.png

633 ms

i-top-r-lp.png

i-top-r-lp.png

523 ms

i-top-r-sh.png

i-top-r-sh.png

523 ms

i-top-r-si.png

i-top-r-si.png

889 ms

cube.png

cube.png

801 ms

i-preim1.png

i-preim1.png

886 ms

i-preim2.png

i-preim2.png

888 ms

i-preim3.png

i-preim3.png

914 ms

i-preim4.png

i-preim4.png

998 ms

i-preim5.png

i-preim5.png

1181 ms

i-preim6.png

i-preim6.png

1252 ms

hviolabg.jpg

hviolabg.jpg

1253 ms

25.jpg

25.jpg

1497 ms

64.jpg

64.jpg

1643 ms

78.jpg

78.jpg

1377 ms

0.jpg

0.jpg

2031 ms

29.jpg

29.jpg

1982 ms

80.jpg

80.jpg

1620 ms

89.jpg

89.jpg

2107 ms

90.jpg

90.jpg

2017 ms

61.jpg

61.jpg

2592 ms

57.jpg

57.jpg

2251 ms

94.jpg

94.jpg

2348 ms

96.jpg

96.jpg

2523 ms

111.jpg

111.jpg

2551 ms

81.jpg

81.jpg

2593 ms

9.jpg

9.jpg

2773 ms

110.jpg

110.jpg

2867 ms

11.jpg

11.jpg

3030 ms

112.jpg

112.jpg

3073 ms

90.jpg

90.jpg

3078 ms

46.jpg

46.jpg

3080 ms

112.jpg

112.jpg

3130 ms

font

font

128 ms

watch.js

watch.js

1 ms

archangelsk-regular.ttf

archangelsk-regular.ttf

3158 ms

icomoon.ttf

icomoon.ttf

3006 ms

65.jpg

65.jpg

2940 ms

37.jpg

37.jpg

2926 ms

108.jpg

108.jpg

2942 ms

98.jpg

98.jpg

3156 ms

66.jpg

66.jpg

3113 ms

7.jpg

7.jpg

3045 ms

106.jpg

106.jpg

2926 ms

15.jpg

15.jpg

2970 ms

hcyanbg.jpg

hcyanbg.jpg

3001 ms

i-seobanner.jpg

i-seobanner.jpg

3573 ms

i-seobanner-btn.png

i-seobanner-btn.png

2998 ms

i-girl.jpg

i-girl.jpg

3095 ms

i-partner.jpg

i-partner.jpg

3168 ms

logo-white.png

logo-white.png

2929 ms

ftr-li.png

ftr-li.png

2814 ms

Accessibility Review

for.ru accessibility score

73

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.

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

Links do not have a discernible name

Best Practices

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

for.ru SEO score

85

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

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

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

for.ru

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