Tools & Wizards About Us
stack.ru screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

stack.ru

Stack.ru - Капстекинг, cup stacking, спид стекинг, speed stacking

Page Load Speed

23.4 sec in total

First Response

1 sec

Resources Loaded

21.4 sec

Page Rendered

1.1 sec

stack.ru screenshot

About Website

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

Первый российский портал про капстекинг (он же cup stacking, он же speed stacking, он же sport stacking) - скоростное составление пирамид из стаканчиков

Visit stack.ru

Key Findings

We analyzed Stack.ru page load time and found that the first response time was 1 sec and then it took 22.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

stack.ru performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.229

54/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

stack.ru

1026 ms

main.css

436 ms

menu.css

453 ms

0.css

454 ms

main.js

477 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 95% of them (73 requests) were addressed to the original Stack.ru, 4% (3 requests) were made to New.stack.ru and 1% (1 request) were made to Catalog.metka.ru. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source New.stack.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.0 kB (36%)

Content Size

301.1 kB

After Optimization

193.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stack.ru main page is 301.1 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. Images take 247.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.6 kB

  • Original 40.3 kB
  • After minification 37.8 kB
  • After compression 8.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 31.6 kB or 78% of the original size.

Image Optimization

-26%

Potential reduce by 65.5 kB

  • Original 247.6 kB
  • After minification 182.1 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. Obviously, Stack needs image optimization as it can save up to 65.5 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 2.4 kB

  • Original 3.3 kB
  • After minification 2.7 kB
  • After compression 850 B

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 2.4 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 8.5 kB

  • Original 9.9 kB
  • After minification 5.2 kB
  • After compression 1.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. Stack.ru needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (62%)

Requests Now

73

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stack.ru

stack.ru

1026 ms

main.css

main.css

436 ms

menu.css

menu.css

453 ms

0.css

0.css

454 ms

main.js

main.js

477 ms

counter.php

counter.php

2633 ms

ban_072009.gif

ban_072009.gif

20091 ms

bodybg.gif

bodybg.gif

234 ms

new_head.gif

new_head.gif

442 ms

1_menu.gif

1_menu.gif

447 ms

mm1.gif

mm1.gif

445 ms

mm2.gif

mm2.gif

443 ms

1.gif

1.gif

448 ms

chap.gif

chap.gif

635 ms

2.gif

2.gif

814 ms

3.gif

3.gif

823 ms

4.gif

4.gif

822 ms

5.gif

5.gif

828 ms

6.gif

6.gif

834 ms

7.gif

7.gif

1018 ms

box.gif

box.gif

1171 ms

title.gif

title.gif

1171 ms

mbul.gif

mbul.gif

1201 ms

599_2.jpg

599_2.jpg

1192 ms

598_2.jpg

598_2.jpg

1205 ms

597_2.jpg

597_2.jpg

1392 ms

596_2.jpg

596_2.jpg

1545 ms

595_2.jpg

595_2.jpg

1590 ms

594_2.jpg

594_2.jpg

1566 ms

593_2.jpg

593_2.jpg

1589 ms

592_2.jpg

592_2.jpg

1578 ms

591_2.jpg

591_2.jpg

1753 ms

590_2.jpg

590_2.jpg

1974 ms

589_2.jpg

589_2.jpg

1984 ms

588_2.jpg

588_2.jpg

2224 ms

587_2.jpg

587_2.jpg

2226 ms

pre_fudsev.jpg

pre_fudsev.jpg

2267 ms

fin_pre.jpg

fin_pre.jpg

2692 ms

box.gif

box.gif

2464 ms

gigabyte_logo.gif

gigabyte_logo.gif

2462 ms

xerox.jpg

xerox.jpg

2669 ms

23_f.jpg

23_f.jpg

20072 ms

prizy_07.01.jpg

prizy_07.01.jpg

20072 ms

k1.jpg

k1.jpg

2681 ms

l1.jpg

l1.jpg

2686 ms

line.gif

line.gif

2635 ms

line.gif

line.gif

2442 ms

bot.gif

bot.gif

2661 ms

0line.gif

0line.gif

2653 ms

on_fm.gif

on_fm.gif

2665 ms

off_fm.gif

off_fm.gif

2686 ms

1o.gif

1o.gif

2657 ms

2o.gif

2o.gif

2479 ms

3o.gif

3o.gif

2652 ms

4o.gif

4o.gif

2662 ms

5o.gif

5o.gif

2680 ms

1.gif

1.gif

2689 ms

2.gif

2.gif

2625 ms

3.gif

3.gif

2497 ms

4.gif

4.gif

2664 ms

5.gif

5.gif

2682 ms

1o.gif

1o.gif

2700 ms

2o.gif

2o.gif

2701 ms

3o.gif

3o.gif

2631 ms

4o.gif

4o.gif

2473 ms

5o.gif

5o.gif

2630 ms

6o.gif

6o.gif

2661 ms

7o.gif

7o.gif

2678 ms

1_head.gif

1_head.gif

2685 ms

2_head.gif

2_head.gif

2635 ms

3_head.gif

3_head.gif

2423 ms

4_head.gif

4_head.gif

2610 ms

2_tree.gif

2_tree.gif

2419 ms

fon2.jpg

fon2.jpg

2676 ms

vertln.gif

vertln.gif

2443 ms

1_bot.gif

1_bot.gif

2359 ms

2_bot.gif

2_bot.gif

2355 ms

Accessibility Review

stack.ru accessibility score

81

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

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

stack.ru 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

stack.ru SEO score

99

Search Engine Optimization Advices

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

    N/A

  • Encoding

    WINDOWS-1251

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

stack.ru

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