Tools & Wizards About Us
stank-in.ru screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

stank-in.ru

Оборудование для производства окон (ПВХ, алюминиевых и пластиковых) от компании Станкин - станки, обрабатывающий центр, пилы

Page Load Speed

8.6 sec in total

First Response

630 ms

Resources Loaded

7.1 sec

Page Rendered

879 ms

stank-in.ru screenshot

About Website

Click here to check amazing Stank In content. Otherwise, check out these important facts you probably never knew about stank-in.ru

Компания СТАНКИН является специальным представителем компании EMMEGI в России - производителя станков для производства окон из пластика и алюминия. У нас вы можете заказать оборудование для производст...

Visit stank-in.ru

Key Findings

We analyzed Stank-in.ru page load time and found that the first response time was 630 ms and then it took 8 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

stank-in.ru performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value4.1 s

86/100

10%

Network Requests Diagram

stank-in.ru

630 ms

www.stank-in.ru

782 ms

styles.css

149 ms

popup.js

291 ms

script.js

292 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 83% of them (34 requests) were addressed to the original Stank-in.ru, 5% (2 requests) were made to Counter.yadro.ru and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Counter.yadro.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.8 kB (42%)

Content Size

189.0 kB

After Optimization

109.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stank-in.ru main page is 189.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. 20% of websites need less resources to load. Javascripts take 108.0 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 14.4 kB

  • Original 20.6 kB
  • After minification 20.6 kB
  • After compression 6.2 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 14.4 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 9 B

  • Original 52.5 kB
  • After minification 52.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. Stank In images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 59.3 kB

  • Original 108.0 kB
  • After minification 106.9 kB
  • After compression 48.7 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 59.3 kB or 55% of the original size.

CSS Optimization

-78%

Potential reduce by 6.1 kB

  • Original 7.9 kB
  • After minification 6.2 kB
  • After compression 1.7 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. Stank-in.ru needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (46%)

Requests Now

37

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stank In. 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 as a result speed up the page load time.

Network Requests Diagram

stank-in.ru

stank-in.ru

630 ms

www.stank-in.ru

www.stank-in.ru

782 ms

styles.css

styles.css

149 ms

popup.js

popup.js

291 ms

script.js

script.js

292 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

474 ms

service.js

service.js

297 ms

watch.js

watch.js

1 ms

main-bg.gif

main-bg.gif

173 ms

menu01-on.gif

menu01-on.gif

235 ms

menu02-on.gif

menu02-on.gif

236 ms

menu03-on.gif

menu03-on.gif

234 ms

menu04-on.gif

menu04-on.gif

235 ms

menu01.gif

menu01.gif

767 ms

menu02.gif

menu02.gif

416 ms

menu03.gif

menu03.gif

807 ms

menu04.gif

menu04.gif

422 ms

top100.cnt

top100.cnt

2957 ms

banner-88x31-rambler-gray2.gif

banner-88x31-rambler-gray2.gif

347 ms

logo

logo

5192 ms

p.gif

p.gif

221 ms

lupa.gif

lupa.gif

222 ms

stankin2.gif

stankin2.gif

832 ms

banns.gif

banns.gif

547 ms

logo.gif

logo.gif

383 ms

icon-home.gif

icon-home.gif

383 ms

icon-mail.gif

icon-mail.gif

560 ms

icon-map.gif

icon-map.gif

552 ms

hit

hit

5159 ms

all-bg.jpg

all-bg.jpg

683 ms

t-bg.gif

t-bg.gif

693 ms

phone.gif

phone.gif

701 ms

li.gif

li.gif

704 ms

foot-r.gif

foot-r.gif

903 ms

foot-l.gif

foot-l.gif

857 ms

ga.js

ga.js

192 ms

__utm.gif

__utm.gif

29 ms

leftbg.gif

leftbg.gif

599 ms

bullit.gif

bullit.gif

599 ms

sverlo.gif

sverlo.gif

766 ms

top-img.jpg

top-img.jpg

702 ms

Accessibility Review

stank-in.ru accessibility score

56

Accessibility Issues

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

stank-in.ru best practices score

58

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

stank-in.ru 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 Stank-in.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 Stank-in.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

stank-in.ru

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