Tools & Wizards About Us
fortochka.biz screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fortochka.biz

Пластиковые окна купить в Ростове-на-Дну - цены на металлопластиковые окна, акции и скидки на окна ПВХ | Форточка

Page Load Speed

30.5 sec in total

First Response

667 ms

Resources Loaded

28.6 sec

Page Rendered

1.2 sec

fortochka.biz screenshot

About Website

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

Компания «Форточка» предлагает широкий ассортимент металлопластиковых окон по приятным ценам! Вы можете купить пластиковые окна в одном из наших салонов.

Visit fortochka.biz

Key Findings

We analyzed Fortochka.biz page load time and found that the first response time was 667 ms and then it took 29.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fortochka.biz performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

fortochka.biz

667 ms

fortochka-okna.ru

860 ms

skin_glavn.css

363 ms

style-reset.css

380 ms

header.css

432 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fortochka.biz, 75% (41 requests) were made to Fortochka-okna.ru and 11% (6 requests) were made to Meedget.ru. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.7 kB (26%)

Content Size

1.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fortochka.biz 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. 30% of websites need less resources to load. Images take 940.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 58.3 kB

  • Original 73.0 kB
  • After minification 72.1 kB
  • After compression 14.7 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 58.3 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 940.0 kB
  • After minification 906.4 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. Fortochka images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 253.5 kB

  • Original 374.7 kB
  • After minification 346.9 kB
  • After compression 121.2 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 253.5 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 26.3 kB

  • Original 32.9 kB
  • After minification 27.1 kB
  • After compression 6.6 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. Fortochka.biz needs all CSS files to be minified and compressed as it can save up to 26.3 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

50

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fortochka.biz

fortochka.biz

667 ms

fortochka-okna.ru

fortochka-okna.ru

860 ms

skin_glavn.css

skin_glavn.css

363 ms

style-reset.css

style-reset.css

380 ms

header.css

header.css

432 ms

footer.css

footer.css

431 ms

style.css

style.css

427 ms

style-map-mainpage.css

style-map-mainpage.css

408 ms

colorbox.css

colorbox.css

586 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

946 ms

watch_visor.js

watch_visor.js

225 ms

client.min.js

client.min.js

943 ms

mainpage_click.js

mainpage_click.js

764 ms

action.js

action.js

703 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

1513 ms

jquery.colorbox.js

jquery.colorbox.js

866 ms

share.js

share.js

80 ms

watch_visor.js

watch_visor.js

20336 ms

ga.js

ga.js

21 ms

__utm.gif

__utm.gif

18 ms

logo.gif

logo.gif

1232 ms

call_zamer.png

call_zamer.png

215 ms

top_menu_splitter.png

top_menu_splitter.png

202 ms

windows-step1.jpg

windows-step1.jpg

492 ms

windows-step2.jpg

windows-step2.jpg

274 ms

windows-step3.png

windows-step3.png

491 ms

kitchens-step1.jpg

kitchens-step1.jpg

407 ms

kitchens-step2.jpg

kitchens-step2.jpg

419 ms

kitchens-step3.jpg

kitchens-step3.jpg

1207 ms

jaluzi-step1.jpg

jaluzi-step1.jpg

630 ms

jaluzi-step2.jpg

jaluzi-step2.jpg

840 ms

jaluzi-step3.jpg

jaluzi-step3.jpg

688 ms

balcony-banner.png

balcony-banner.png

6044 ms

40percemt-color.png

40percemt-color.png

1367 ms

spring45.png

spring45.png

1282 ms

ac2.gif

ac2.gif

2675 ms

map_main.png

map_main.png

6524 ms

vagno.jpg

vagno.jpg

1832 ms

kondensat.jpg

kondensat.jpg

1452 ms

aksploataciya.jpg

aksploataciya.jpg

1775 ms

header_main_bg.gif

header_main_bg.gif

1612 ms

1.jpg

1.jpg

2824 ms

windows.png

windows.png

3272 ms

kitchen.png

kitchen.png

3787 ms

jaluzi.png

jaluzi.png

3285 ms

jquery2.js

jquery2.js

365 ms

b-share-icon.png

b-share-icon.png

70 ms

watch.js

watch.js

0 ms

control_left.png

control_left.png

3046 ms

control_right.png

control_right.png

3204 ms

overlay.png

overlay.png

3377 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

197 ms

MeedgetInit

MeedgetInit

620 ms

menu_icon2.png

menu_icon2.png

169 ms

jquery.fancybox.css

jquery.fancybox.css

202 ms

Accessibility Review

fortochka.biz accessibility score

51

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fortochka.biz 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

fortochka.biz SEO score

62

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

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 Fortochka.biz 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 Fortochka.biz 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

fortochka.biz

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