Tools & Wizards About Us
bringo.uz screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

bringo.uz

экспресс доставка еды в Ташкенте круглосуточно - Bringo.uz

Page Load Speed

9.5 sec in total

First Response

2.2 sec

Resources Loaded

6.9 sec

Page Rendered

405 ms

bringo.uz screenshot

About Website

Welcome to bringo.uz homepage info - get ready to check Bringo best content for Uzbekistan right away, or after learning these important things about bringo.uz

экспресс доставка еды в Ташкенте круглосуточно - Bringo.uz

Visit bringo.uz

Key Findings

We analyzed Bringo.uz page load time and found that the first response time was 2.2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

bringo.uz performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value34.0 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value25,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value36.4 s

0/100

10%

Network Requests Diagram

bringo.uz

2175 ms

jquery.jgrowl.css

138 ms

jquery.js

859 ms

jquery.yiilistview.js

328 ms

jquery.jgrowl.js

348 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 88% of them (51 requests) were addressed to the original Bringo.uz, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Bringo.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 709.4 kB (42%)

Content Size

1.7 MB

After Optimization

981.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bringo.uz main page is 1.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. 40% of websites need less resources to load. Images take 903.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 43.7 kB

  • Original 51.4 kB
  • After minification 39.2 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 12.1 kB, which is 24% 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 43.7 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 67.3 kB

  • Original 903.2 kB
  • After minification 835.9 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. Bringo images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 501.8 kB

  • Original 619.7 kB
  • After minification 392.0 kB
  • After compression 117.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 501.8 kB or 81% of the original size.

CSS Optimization

-83%

Potential reduce by 96.5 kB

  • Original 116.7 kB
  • After minification 83.5 kB
  • After compression 20.1 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. Bringo.uz needs all CSS files to be minified and compressed as it can save up to 96.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (68%)

Requests Now

53

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bringo.uz

bringo.uz

2175 ms

jquery.jgrowl.css

jquery.jgrowl.css

138 ms

jquery.js

jquery.js

859 ms

jquery.yiilistview.js

jquery.yiilistview.js

328 ms

jquery.jgrowl.js

jquery.jgrowl.js

348 ms

css

css

75 ms

main.css

main.css

349 ms

hint.base.min.css

hint.base.min.css

348 ms

custom.css

custom.css

355 ms

style.css

style.css

494 ms

mobile.css

mobile.css

525 ms

magnific-popup.css

magnific-popup.css

528 ms

fotorama.css

fotorama.css

528 ms

fontello.css

fontello.css

539 ms

main.js

main.js

668 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

707 ms

common.js

common.js

708 ms

script.js

script.js

707 ms

bootstrap.js

bootstrap.js

734 ms

fotorama.js

fotorama.js

1075 ms

jquery.mockjax.js

jquery.mockjax.js

1721 ms

jquery.autocomplete.js

jquery.autocomplete.js

1725 ms

normalize.css

normalize.css

208 ms

snippets.css

snippets.css

212 ms

magnific-addons.css

magnific-addons.css

204 ms

logo_bringo_128.png

logo_bringo_128.png

173 ms

search_icon.png

search_icon.png

176 ms

food_icon.png

food_icon.png

171 ms

products_icon.png

products_icon.png

175 ms

enter_icon.png

enter_icon.png

173 ms

basket_icon.png

basket_icon.png

169 ms

menu_icon.png

menu_icon.png

322 ms

order_icon.png

order_icon.png

320 ms

delivery_icon.png

delivery_icon.png

321 ms

heart_icon.png

heart_icon.png

323 ms

right_arrow_icon.png

right_arrow_icon.png

328 ms

283_759606798.jpg

283_759606798.jpg

2925 ms

290_409960315.jpg

290_409960315.jpg

1067 ms

231_2208238124.jpg

231_2208238124.jpg

1013 ms

355_1759564193.jpg

355_1759564193.jpg

1612 ms

235_3393875568.jpg

235_3393875568.jpg

916 ms

down_arrow_orange_icon.png

down_arrow_orange_icon.png

519 ms

right_arrow_blue_icon.png

right_arrow_blue_icon.png

732 ms

307_4041620999.jpg

307_4041620999.jpg

2369 ms

252_952030012.jpg

252_952030012.jpg

1727 ms

251_761729528.jpg

251_761729528.jpg

1336 ms

334_1057535657.jpg

334_1057535657.jpg

1238 ms

336_1828577252.jpg

336_1828577252.jpg

1530 ms

down_arrow_blue_icon.png

down_arrow_blue_icon.png

1496 ms

social_f_icon.png

social_f_icon.png

1635 ms

social_t_icon.png

social_t_icon.png

1663 ms

social_i_icon.png

social_i_icon.png

1755 ms

watch.js

watch.js

37 ms

analytics.js

analytics.js

60 ms

Fl4y0QdOxyyTHEGMXX8kcaCWcynf_cDxXwCLxiixG1c.ttf

Fl4y0QdOxyyTHEGMXX8kcaCWcynf_cDxXwCLxiixG1c.ttf

68 ms

B85vmdvDILX92ray16e-1g.ttf

B85vmdvDILX92ray16e-1g.ttf

69 ms

collect

collect

46 ms

collect

collect

309 ms

Accessibility Review

bringo.uz accessibility score

76

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bringo.uz best practices score

75

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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

bringo.uz SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

bringo.uz

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