Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

spartak.by

Кондитерская фабрика «Спартак» - официальный сайт

Page Load Speed

21.7 sec in total

First Response

842 ms

Resources Loaded

19.1 sec

Page Rendered

1.7 sec

spartak.by screenshot

About Website

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

Кондитерская фабрика «Спартак» является крупнейшим производителем кондитерских изделий в Беларуси. Купить шоколад и карамель, печенье, вафли в фирменных магазинах Спартак в городах Беларуси.

Visit spartak.by

Key Findings

We analyzed Spartak.by page load time and found that the first response time was 842 ms and then it took 20.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

spartak.by performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

spartak.by

842 ms

css

250 ms

font-awesome.min.css

270 ms

core.css

365 ms

popup.css

388 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 90% of them (135 requests) were addressed to the original Spartak.by, 3% (5 requests) were made to Maps.googleapis.com and 1% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (11.8 sec) belongs to the original domain Spartak.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 799.6 kB (13%)

Content Size

6.0 MB

After Optimization

5.2 MB

In fact, the total size of Spartak.by main page is 6.0 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. 70% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 29.5 kB

  • Original 36.7 kB
  • After minification 29.8 kB
  • After compression 7.1 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 6.9 kB, which is 19% 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 29.5 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 253.4 kB

  • Original 5.3 MB
  • After minification 5.0 MB

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

JavaScript Optimization

-68%

Potential reduce by 408.8 kB

  • Original 599.7 kB
  • After minification 509.1 kB
  • After compression 190.9 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 408.8 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 107.8 kB

  • Original 128.2 kB
  • After minification 117.8 kB
  • After compression 20.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. Spartak.by needs all CSS files to be minified and compressed as it can save up to 107.8 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

145

After Optimization

100

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

Accessibility Review

spartak.by accessibility score

71

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

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.

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

spartak.by 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

spartak.by SEO score

85

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 Spartak.by 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 Spartak.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 Spartak. 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: