Tools & Wizards About Us
stolle.ru screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

stolle.ru

Пироги Штолле. Заказ и доставка пирогов, доставка обедов.

Page Load Speed

5.2 sec in total

First Response

1 sec

Resources Loaded

3.8 sec

Page Rendered

301 ms

stolle.ru screenshot

About Website

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

Сеть пироговых Штолле - заказ и доставка пирогов.

Visit stolle.ru

Key Findings

We analyzed Stolle.ru page load time and found that the first response time was 1 sec and then it took 4.1 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

stolle.ru performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,100 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.287

42/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

stolle.ru

1031 ms

system.base.css

126 ms

system.menus.css

251 ms

system.messages.css

252 ms

system.theme.css

251 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 90% of them (62 requests) were addressed to the original Stolle.ru, 6% (4 requests) were made to Mc.yandex.ru and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Stolle.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 338.9 kB (11%)

Content Size

3.0 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stolle.ru main page is 3.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. 30% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 19.9 kB

  • Original 28.1 kB
  • After minification 27.1 kB
  • After compression 8.3 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 19.9 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 14.6 kB

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

JavaScript Optimization

-67%

Potential reduce by 227.3 kB

  • Original 341.3 kB
  • After minification 292.1 kB
  • After compression 114.0 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 227.3 kB or 67% of the original size.

CSS Optimization

-79%

Potential reduce by 77.1 kB

  • Original 97.1 kB
  • After minification 75.4 kB
  • After compression 20.0 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. Stolle.ru needs all CSS files to be minified and compressed as it can save up to 77.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (75%)

Requests Now

67

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 28 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stolle.ru

stolle.ru

1031 ms

system.base.css

system.base.css

126 ms

system.menus.css

system.menus.css

251 ms

system.messages.css

system.messages.css

252 ms

system.theme.css

system.theme.css

251 ms

comment.css

comment.css

255 ms

date.css

date.css

255 ms

datepicker.1.7.css

datepicker.1.7.css

253 ms

field.css

field.css

374 ms

node.css

node.css

372 ms

search.css

search.css

375 ms

uc_order.css

uc_order.css

376 ms

uc_product.css

uc_product.css

377 ms

uc_store.css

uc_store.css

378 ms

user.css

user.css

494 ms

views.css

views.css

497 ms

ckeditor.css

ckeditor.css

499 ms

collapsiblock.css

collapsiblock.css

501 ms

colorbox_default_style.css

colorbox_default_style.css

502 ms

ctools.css

ctools.css

503 ms

jquery.ui.core.css

jquery.ui.core.css

617 ms

jquery.ui.theme.css

jquery.ui.theme.css

621 ms

flexslider.css

flexslider.css

623 ms

uc_ajax_cart.css

uc_ajax_cart.css

626 ms

style.css

style.css

631 ms

jquery.js

jquery.js

752 ms

jquery.once.js

jquery.once.js

739 ms

drupal.js

drupal.js

748 ms

jquery.cookie.js

jquery.cookie.js

748 ms

jquery.form.js

jquery.form.js

749 ms

ajax.js

ajax.js

766 ms

admin_devel.js

admin_devel.js

862 ms

ru_FOU55zuRc28IKDawOVhh_b9MnF94CoQMBMgxbzeW7L0.js

ru_FOU55zuRc28IKDawOVhh_b9MnF94CoQMBMgxbzeW7L0.js

871 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

873 ms

colorbox.js

colorbox.js

874 ms

colorbox_default_style.js

colorbox_default_style.js

876 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

879 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

870 ms

jquery.ui.tabs.min.js

jquery.ui.tabs.min.js

757 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

758 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

757 ms

jquery.blockui.js

jquery.blockui.js

758 ms

uc_ajax_cart.js

uc_ajax_cart.js

761 ms

jquery.cookie.js

jquery.cookie.js

864 ms

jump-menu.js

jump-menu.js

760 ms

base.js

base.js

759 ms

progress.js

progress.js

758 ms

ajax_view.js

ajax_view.js

760 ms

kibmak.js

kibmak.js

764 ms

collapsiblock.js

collapsiblock.js

862 ms

bg_all.jpg

bg_all.jpg

1241 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

227 ms

bg-stolle.jpg

bg-stolle.jpg

1653 ms

mobile_ref.png

mobile_ref.png

128 ms

menu.png

menu.png

129 ms

stolle_logo.png

stolle_logo.png

381 ms

stolle_logo.png

stolle_logo.png

443 ms

front.jpg

front.jpg

628 ms

footerlogo.png

footerlogo.png

256 ms

vk.png

vk.png

381 ms

facebook.png

facebook.png

506 ms

twitter.png

twitter.png

507 ms

gplus.png

gplus.png

568 ms

watch.js

watch.js

168 ms

analytics.js

analytics.js

22 ms

collect

collect

12 ms

watch.js

watch.js

474 ms

advert.gif

advert.gif

90 ms

1

1

92 ms

Accessibility Review

stolle.ru accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

High

Page has valid source maps

SEO Factors

stolle.ru SEO score

83

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 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 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

stolle.ru

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