Tools & Wizards About Us
sbarro.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sbarro.ru

Бесплатная доставка пиццы на дом и офис Москва - доставка пиццы недорого - Сбарро!

Page Load Speed

4.6 sec in total

First Response

351 ms

Resources Loaded

3.9 sec

Page Rendered

281 ms

sbarro.ru screenshot

About Website

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

Заказ бесплатной доставки итальянской пиццы в Москве. В пиццу можно добавить любой ингредиент по вашему вкусу и собрать пиццу по собственному рецепту. Доставка пиццы на дом или в офис.

Visit sbarro.ru

Key Findings

We analyzed Sbarro.ru page load time and found that the first response time was 351 ms and then it took 4.2 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

sbarro.ru performance score

0

Network Requests Diagram

sbarro.ru

351 ms

www.sbarro.ru

820 ms

newstyle.css

137 ms

nivo-slider.css

271 ms

font-awesome.css

275 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 71% of them (51 requests) were addressed to the original Sbarro.ru, 6% (4 requests) were made to Px.adhigh.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Sbarro.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 693.3 kB (26%)

Content Size

2.6 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 20.0 kB

  • Original 28.1 kB
  • After minification 25.8 kB
  • After compression 8.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. 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 20.0 kB or 71% of the original size.

Image Optimization

-9%

Potential reduce by 165.8 kB

  • Original 1.9 MB
  • After minification 1.7 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. Sbarro images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 420.4 kB

  • Original 596.1 kB
  • After minification 550.3 kB
  • After compression 175.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 420.4 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 87.2 kB

  • Original 108.1 kB
  • After minification 99.3 kB
  • After compression 20.9 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. Sbarro.ru needs all CSS files to be minified and compressed as it can save up to 87.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (59%)

Requests Now

63

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sbarro.ru

sbarro.ru

351 ms

www.sbarro.ru

www.sbarro.ru

820 ms

newstyle.css

newstyle.css

137 ms

nivo-slider.css

nivo-slider.css

271 ms

font-awesome.css

font-awesome.css

275 ms

chosen.css

chosen.css

274 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

271 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

278 ms

jquery.custom-input-file.css

jquery.custom-input-file.css

278 ms

core.css

core.css

405 ms

style.css

style.css

403 ms

style.css

style.css

405 ms

core.js

core.js

558 ms

core_ajax.js

core_ajax.js

419 ms

session.js

session.js

419 ms

jquery.min.js

jquery.min.js

824 ms

chosen.jquery.js

chosen.jquery.js

552 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

564 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

578 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

1017 ms

customInput.jquery.js

customInput.jquery.js

687 ms

jquery.form.js

jquery.form.js

697 ms

script.js

script.js

693 ms

js.js

js.js

718 ms

jquery.custom-input-file.js

jquery.custom-input-file.js

845 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

845 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

845 ms

conversion.js

conversion.js

28 ms

HeliosCond.woff

HeliosCond.woff

137 ms

analytics.js

analytics.js

14 ms

p.js

p.js

33 ms

rtrg

rtrg

267 ms

fbds.js

fbds.js

11 ms

logonew.png

logonew.png

135 ms

logoold.png

logoold.png

277 ms

captcha.php

captcha.php

390 ms

badf458f6788bcec659f7ba16fded9fa.jpg

badf458f6788bcec659f7ba16fded9fa.jpg

996 ms

2313a62a12c0d4d809b895cdef6fcd98.png

2313a62a12c0d4d809b895cdef6fcd98.png

1425 ms

416a97ee03108d6518caeaaac4245ca1.jpg

416a97ee03108d6518caeaaac4245ca1.jpg

1132 ms

sbarro_nomer_1.jpg

sbarro_nomer_1.jpg

527 ms

map2.jpg

map2.jpg

686 ms

dostavka2.jpg

dostavka2.jpg

983 ms

job.jpg

job.jpg

790 ms

fontawesome-webfont.woff@v=3.2.1

fontawesome-webfont.woff@v=3.2.1

991 ms

154 ms

collect

collect

56 ms

fancybox_overlay.png

fancybox_overlay.png

896 ms

like.png

like.png

1022 ms

avto.png

avto.png

1088 ms

point.png

point.png

1096 ms

3sekreta.png

3sekreta.png

1649 ms

bgfooter.png

bgfooter.png

1153 ms

redline.png

redline.png

1225 ms

vk.png

vk.png

1225 ms

fb.png

fb.png

1228 ms

ok.png

ok.png

1285 ms

inst.png

inst.png

1362 ms

watch.js

watch.js

34 ms

62 ms

chosen-sprite.png

chosen-sprite.png

1318 ms

tracking.js

tracking.js

5 ms

sync.html

sync.html

10 ms

rtset

rtset

65 ms

pixel

pixel

64 ms

85 ms

tpid=LBejsMSahNU

tpid=LBejsMSahNU

35 ms

xuid

xuid

31 ms

pixel

pixel

19 ms

goog

goog

7 ms

tap.php

tap.php

8 ms

sync

sync

68 ms

26 ms

SEO Factors

sbarro.ru SEO score

0

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

sbarro.ru

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