Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

Page Load Speed

17.4 sec in total

First Response

1.2 sec

Resources Loaded

15.2 sec

Page Rendered

876 ms

socket.by screenshot

About Website

Welcome to socket.by homepage info - get ready to check Socket best content for Belarus right away, or after learning these important things about socket.by

Интернет магазин Socket.by в Минске. Продажа бытовой, видео-, аудио- и компьютерной техники по доступным ценам. Доставка по Минску и Беларуси. Скидки, акции.

Visit socket.by

Key Findings

We analyzed Socket.by page load time and found that the first response time was 1.2 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

socket.by performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

socket.by

1248 ms

www.socket.by

2450 ms

page_b9cbabd16c6c6d5f0836b1f6fe9ecad4.css

897 ms

template_666a11c857334f346570e6b9128b05e1.css

895 ms

style.css

2145 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 51% of them (46 requests) were addressed to the original Socket.by, 13% (12 requests) were made to Widgets.livetex.ru and 12% (11 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 793.3 kB (51%)

Content Size

1.6 MB

After Optimization

757.0 kB

In fact, the total size of Socket.by main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 674.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 159.5 kB

  • Original 179.2 kB
  • After minification 93.3 kB
  • After compression 19.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 85.9 kB, which is 48% 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 159.5 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 45.5 kB

  • Original 582.6 kB
  • After minification 537.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. Socket images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 493.4 kB

  • Original 674.1 kB
  • After minification 598.6 kB
  • After compression 180.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 493.4 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 94.8 kB

  • Original 114.4 kB
  • After minification 92.6 kB
  • After compression 19.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. Socket.by needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (31%)

Requests Now

74

After Optimization

51

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

Accessibility Review

socket.by accessibility score

79

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

socket.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

socket.by SEO score

91

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

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

    UTF-8

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

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