Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

spb.stolle.ru

Пироги Штолле в Санкт-Петербурге | Пироги, кулинария заказ и доставка | Кулинария и полуфабрикаты собственного производства | Куличи пасхальные

Page Load Speed

30.2 sec in total

First Response

3.8 sec

Resources Loaded

25.6 sec

Page Rendered

841 ms

spb.stolle.ru screenshot

About Website

Visit spb.stolle.ru now to see the best up-to-date Spb Stolle content for Russia and also check out these interesting facts you probably never knew about spb.stolle.ru

Пироги Штолле - заказ и доставка пирогов в Санкт-Петербурге, бесконтактная доставка пирогов до двери, online оплата в мобильном приложении и на сайте, лучшее качество в СПб.

Visit spb.stolle.ru

Key Findings

We analyzed Spb.stolle.ru page load time and found that the first response time was 3.8 sec and then it took 26.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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

spb.stolle.ru performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value25.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

spb.stolle.ru

3820 ms

css2

74 ms

owl.carousel.css

139 ms

owl.theme.default.min.css

275 ms

5dc467ba00.js

93 ms

Our browser made a total of 194 requests to load all elements on the main page. We found that 36% of them (70 requests) were addressed to the original Spb.stolle.ru, 42% (81 requests) were made to Core-renderer-tiles.maps.yandex.net and 9% (18 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Uniteller.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 631.3 kB (8%)

Content Size

7.7 MB

After Optimization

7.1 MB

In fact, the total size of Spb.stolle.ru main page is 7.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 531.9 kB

  • Original 627.5 kB
  • After minification 596.3 kB
  • After compression 95.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 531.9 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 75.2 kB

  • Original 6.6 MB
  • After minification 6.5 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. Spb Stolle images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 23.9 kB

  • Original 439.6 kB
  • After minification 439.6 kB
  • After compression 415.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 312 B

  • Original 27.6 kB
  • After minification 27.6 kB
  • After compression 27.3 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. Spb.stolle.ru has all CSS files already compressed.

Requests Breakdown

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

Requests Now

185

After Optimization

128

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

Accessibility Review

spb.stolle.ru accessibility score

85

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

spb.stolle.ru 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

spb.stolle.ru SEO score

77

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 doesn't use 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 Spb.stolle.ru 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 Spb.stolle.ru 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 data is detected on the main page of Spb Stolle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: