Tools & Wizards About Us
yandex.st screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

yandex.st

JavaScript-библиотеки — Технологии Яндекса

Page Load Speed

6.1 sec in total

First Response

589 ms

Resources Loaded

4.9 sec

Page Rendered

526 ms

yandex.st screenshot

About Website

Welcome to yandex.st homepage info - get ready to check Yandex best content for Russia right away, or after learning these important things about yandex.st

Загружайте различные JavaScript-фреймворки и библиотеки с открытым исходным кодом с серверов Яндекса по постоянным ссылкам.

Visit yandex.st

Key Findings

We analyzed Yandex.st page load time and found that the first response time was 589 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

yandex.st performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value10.8 s

21/100

10%

Network Requests Diagram

jslibs

589 ms

682 ms

text-regular.woff

553 ms

7RkupUWVEcepjeZPFv1xCDdQFhc.woff

742 ms

text-medium.woff

1034 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yandex.st, 4% (3 requests) were made to Avatars.mds.yandex.net and 3% (2 requests) were made to Yandex.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.2 kB (46%)

Content Size

982.5 kB

After Optimization

535.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Yandex.st main page is 982.5 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. 35% of websites need less resources to load. Javascripts take 511.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 400.9 kB

  • Original 470.3 kB
  • After minification 469.9 kB
  • After compression 69.4 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 400.9 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 29 B

  • Original 647 B
  • After minification 618 B

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. Yandex images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 46.3 kB

  • Original 511.5 kB
  • After minification 511.5 kB
  • After compression 465.3 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.

Requests Breakdown

Number of requests can be reduced by 63 (94%)

Requests Now

67

After Optimization

4

  • Images
  • JavaScript

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

Network Requests Diagram

jslibs

jslibs

589 ms

682 ms

text-regular.woff

text-regular.woff

553 ms

7RkupUWVEcepjeZPFv1xCDdQFhc.woff

7RkupUWVEcepjeZPFv1xCDdQFhc.woff

742 ms

text-medium.woff

text-medium.woff

1034 ms

aHTLG2tTlmAJt89PBP6ke1NjNlI.woff

aHTLG2tTlmAJt89PBP6ke1NjNlI.woff

1052 ms

text-light.woff

text-light.woff

1052 ms

p9QGkWz-vqtayeFDeI6z9Dxffpo.woff

p9QGkWz-vqtayeFDeI6z9Dxffpo.woff

1038 ms

text-bold.woff

text-bold.woff

1064 ms

6n8FrCwGXwQ5ZumBk1SCxOl2ec8.woff

6n8FrCwGXwQ5ZumBk1SCxOl2ec8.woff

931 ms

lqip_q70

lqip_q70

596 ms

%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81.svg

%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81.svg

1092 ms

%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81.svg

%D0%AF%D0%BD%D0%B4%D0%B5%D0%BA%D1%81.svg

1116 ms

index.429c039393f2eaa25a2a.js

index.429c039393f2eaa25a2a.js

1195 ms

6246.0721deed920aaee5a271.js

6246.0721deed920aaee5a271.js

1132 ms

1360.4c25c7b689bbcaf9ff81.js

1360.4c25c7b689bbcaf9ff81.js

1108 ms

init-bundle.1b6eb63fff484f843e4e.js

init-bundle.1b6eb63fff484f843e4e.js

1133 ms

css-desktop-desktop-block-css.5c96e03fc604741679a6.js

css-desktop-desktop-block-css.5c96e03fc604741679a6.js

1205 ms

1669.f809b4d151e06508295b.js

1669.f809b4d151e06508295b.js

1218 ms

2683.6004b4c4b2598ad2979b.js

2683.6004b4c4b2598ad2979b.js

1244 ms

9956.da8364215c6f60ea1e36.js

9956.da8364215c6f60ea1e36.js

1327 ms

5911.fab5ef8121af2b08417e.js

5911.fab5ef8121af2b08417e.js

1278 ms

3193.35f8ec64afe47681e93b.js

3193.35f8ec64afe47681e93b.js

1335 ms

2581.6e09d692ebd95ce56a1b.js

2581.6e09d692ebd95ce56a1b.js

1357 ms

9980.26ffe2d15bb6afeb5bbd.js

9980.26ffe2d15bb6afeb5bbd.js

1408 ms

9614.57f4367fa394c7e2b301.js

9614.57f4367fa394c7e2b301.js

1382 ms

6767.08f8ca71abf74c5463d5.js

6767.08f8ca71abf74c5463d5.js

1427 ms

1965.2975bb8b3ae40d6f1d10.js

1965.2975bb8b3ae40d6f1d10.js

1526 ms

2302.9b01a749a0be0114b0ad.js

2302.9b01a749a0be0114b0ad.js

1474 ms

7330.658f575a458713c532dc.js

7330.658f575a458713c532dc.js

1554 ms

2530.90caa4a08f30dd7e15c0.js

2530.90caa4a08f30dd7e15c0.js

1479 ms

3311.b9acc44e4a34f915454d.js

3311.b9acc44e4a34f915454d.js

1544 ms

9184.986ad7a918fe862b1fe1.js

9184.986ad7a918fe862b1fe1.js

1570 ms

8565.fd0a6135c45fa1d890e2.js

8565.fd0a6135c45fa1d890e2.js

1612 ms

LcPage.aac97e55aab0e3a7cd97.js

LcPage.aac97e55aab0e3a7cd97.js

1650 ms

9383.a2095659b79e4bd9f26e.js

9383.a2095659b79e4bd9f26e.js

1665 ms

LcScreen.173cc6dcc8a7598685d4.js

LcScreen.173cc6dcc8a7598685d4.js

1634 ms

LcGroup.8af7d304adbc1501bb79.js

LcGroup.8af7d304adbc1501bb79.js

1695 ms

LcCustomHtml.44f7c5df2f6d8979c1a4.js

LcCustomHtml.44f7c5df2f6d8979c1a4.js

1716 ms

lqip_q70

lqip_q70

706 ms

lqip_q70

lqip_q70

844 ms

3210.5c5ee17f7c218df5544f.js

3210.5c5ee17f7c218df5544f.js

1231 ms

1506.8ad122dd7948d32073a9.js

1506.8ad122dd7948d32073a9.js

1063 ms

6193.8f77058e197e538a4ce4.js

6193.8f77058e197e538a4ce4.js

892 ms

5257.ca78a49674f4a2437c1f.js

5257.ca78a49674f4a2437c1f.js

800 ms

9062.971fe5aeced95c72fa2a.js

9062.971fe5aeced95c72fa2a.js

823 ms

603.096b15f6ac83fd46ab8c.js

603.096b15f6ac83fd46ab8c.js

847 ms

9804.f1d745d33afbb7e4aecd.js

9804.f1d745d33afbb7e4aecd.js

878 ms

2592.a5afda03b0522b227c44.js

2592.a5afda03b0522b227c44.js

876 ms

9182.fe8f81b9e11f5de0a7e7.js

9182.fe8f81b9e11f5de0a7e7.js

865 ms

9717.3dcadd34e0ce2b91597d.js

9717.3dcadd34e0ce2b91597d.js

847 ms

9423.ff0ffac8303a741f8cbb.js

9423.ff0ffac8303a741f8cbb.js

869 ms

9595.82aea53648d3b7fda4a5.js

9595.82aea53648d3b7fda4a5.js

874 ms

8413.3afad19e5e3049a8c6f4.js

8413.3afad19e5e3049a8c6f4.js

901 ms

8868.30ecb853b8855099d8a6.js

8868.30ecb853b8855099d8a6.js

857 ms

4805.25bef35c138a4e8ef7fa.js

4805.25bef35c138a4e8ef7fa.js

873 ms

8164.ec1514523df6540bdaa7.js

8164.ec1514523df6540bdaa7.js

855 ms

6000.00065126a6724a87c008.js

6000.00065126a6724a87c008.js

828 ms

4706.c3d4ef30c0e712d17f6e.js

4706.c3d4ef30c0e712d17f6e.js

880 ms

1392.904065bddd9e5c81ac87.js

1392.904065bddd9e5c81ac87.js

855 ms

LcHeaderLpc.2562f1dd89ef920b8955.js

LcHeaderLpc.2562f1dd89ef920b8955.js

864 ms

LcBreadcrumbs.ef957c9b7a6676b1f421.js

LcBreadcrumbs.ef957c9b7a6676b1f421.js

859 ms

2840.f50afecb745e4ea686dd.js

2840.f50afecb745e4ea686dd.js

834 ms

1878.26e0add9049b1b267c04.js

1878.26e0add9049b1b267c04.js

816 ms

LcBodyImage.3ecb26509616c6f13283.js

LcBodyImage.3ecb26509616c6f13283.js

877 ms

4843.879e16d28507586a881c.js

4843.879e16d28507586a881c.js

844 ms

LcButtonList.61e9d5d4ba9461d37a94.js

LcButtonList.61e9d5d4ba9461d37a94.js

810 ms

LcAnchors.6409a79de307d3ee4a92.js

LcAnchors.6409a79de307d3ee4a92.js

843 ms

LcText.21b002d1a84a93a1f7f9.js

LcText.21b002d1a84a93a1f7f9.js

769 ms

778.92de3f1cdc92eb4ca847.js

778.92de3f1cdc92eb4ca847.js

809 ms

LcFeatures.8dc82448a3815881398a.js

LcFeatures.8dc82448a3815881398a.js

948 ms

LcFooterLpc.ad92324706359d8aa991.js

LcFooterLpc.ad92324706359d8aa991.js

792 ms

react-with-dom.min.js

react-with-dom.min.js

799 ms

vkontakte-2.svg

vkontakte-2.svg

868 ms

twitter-2.svg

twitter-2.svg

854 ms

youtube-2.svg

youtube-2.svg

824 ms

habr.svg

habr.svg

866 ms

Accessibility Review

yandex.st accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role] values are not valid

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

yandex.st best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yandex.st SEO score

100

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

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 Yandex.st 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 Yandex.st 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

yandex.st

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: