Tools & Wizards About Us
keys.so screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

keys.so

Keys.so – сервис анализа конкурентов в SEO, Яндекс Директе и Дзене

Page Load Speed

4 sec in total

First Response

284 ms

Resources Loaded

2.4 sec

Page Rendered

1.3 sec

keys.so screenshot

About Website

Welcome to keys.so homepage info - get ready to check Keys best content for Russia right away, or after learning these important things about keys.so

Поможет узнать рекламу любых сайтов, собрать семантическое ядро, анализировать топ Яндекс и Google, входящие и исходящие ссылки сайтов.

Visit keys.so

Key Findings

We analyzed Keys.so page load time and found that the first response time was 284 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

keys.so performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value4,030 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

keys.so

284 ms

www.keys.so

37 ms

ru

633 ms

vendors~app.55bac989d7c842e206cf.css

65 ms

app.55bac989d7c842e206cf.css

34 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 74% of them (39 requests) were addressed to the original Keys.so, 9% (5 requests) were made to Vk.com and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Keys.so.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.0 kB (28%)

Content Size

260.6 kB

After Optimization

187.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Keys.so main page is 260.6 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. Only a small number of websites need less resources to load. CSS take 147.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.0 kB

  • Original 85.6 kB
  • After minification 76.6 kB
  • After compression 15.6 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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.0 kB or 82% of the original size.

JavaScript Optimization

-10%

Potential reduce by 2.9 kB

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 24.6 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

-0%

Potential reduce by 59 B

  • Original 147.5 kB
  • After minification 147.5 kB
  • After compression 147.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. Keys.so has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (42%)

Requests Now

43

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

keys.so

keys.so

284 ms

www.keys.so

www.keys.so

37 ms

ru

ru

633 ms

vendors~app.55bac989d7c842e206cf.css

vendors~app.55bac989d7c842e206cf.css

65 ms

app.55bac989d7c842e206cf.css

app.55bac989d7c842e206cf.css

34 ms

css

css

64 ms

adaptive.55bac989d7c842e206cf.css

adaptive.55bac989d7c842e206cf.css

25 ms

vendors~app.55bac989d7c842e206cf.js

vendors~app.55bac989d7c842e206cf.js

117 ms

app.55bac989d7c842e206cf.js

app.55bac989d7c842e206cf.js

115 ms

adaptive.js

adaptive.js

61 ms

support.js

support.js

840 ms

ellipse-green.svg

ellipse-green.svg

247 ms

tasks.svg

tasks.svg

249 ms

for-whom.webp

for-whom.webp

499 ms

ellipse-dark.svg

ellipse-dark.svg

253 ms

graph.svg

graph.svg

250 ms

list-item-circular.svg

list-item-circular.svg

251 ms

tools-organic.webp

tools-organic.webp

495 ms

tools-links.webp

tools-links.webp

524 ms

list.svg

list.svg

254 ms

tools-context.webp

tools-context.webp

524 ms

tools-rsya.webp

tools-rsya.webp

530 ms

pad.svg

pad.svg

255 ms

group.svg

group.svg

256 ms

chain.svg

chain.svg

258 ms

zen.svg

zen.svg

258 ms

concurents.svg

concurents.svg

266 ms

gear.svg

gear.svg

416 ms

part.svg

part.svg

435 ms

free.webp

free.webp

925 ms

sprites.webp

sprites.webp

970 ms

sk.webp

sk.webp

1000 ms

extension_chrome.svg

extension_chrome.svg

526 ms

part.svg

part.svg

541 ms

mir-light.svg

mir-light.svg

542 ms

mastercard-light.svg

mastercard-light.svg

544 ms

visa-light.svg

visa-light.svg

546 ms

sbp-light.svg

sbp-light.svg

555 ms

ya-pay-light.svg

ya-pay-light.svg

559 ms

tag.js

tag.js

204 ms

rtrg

rtrg

540 ms

KFOmCnqEu92Fr1Mu72xP.ttf

KFOmCnqEu92Fr1Mu72xP.ttf

229 ms

KFOlCnqEu92Fr1MmEU9fCRc9.ttf

KFOlCnqEu92Fr1MmEU9fCRc9.ttf

263 ms

KFOlCnqEu92Fr1MmSU5fCRc9.ttf

KFOlCnqEu92Fr1MmSU5fCRc9.ttf

258 ms

KFOkCnqEu92Fr1MmgVxFIzc.ttf

KFOkCnqEu92Fr1MmgVxFIzc.ttf

331 ms

KFOlCnqEu92Fr1MmWUlfCRc9.ttf

KFOlCnqEu92Fr1MmWUlfCRc9.ttf

287 ms

primeicons.woff

primeicons.woff

1044 ms

social-links.ttf

social-links.ttf

788 ms

advert.gif

advert.gif

711 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

249 ms

rtrg

rtrg

130 ms

rtrg

rtrg

139 ms

rtrg

rtrg

243 ms

Accessibility Review

keys.so 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

[aria-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

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

keys.so 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

keys.so SEO score

86

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

    UTF-8

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

keys.so

Open Graph data is detected on the main page of Keys. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: