Tools & Wizards About Us
mehrli.uz screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mehrli.uz

Mehrli qo'llar - mehrli.uz

Page Load Speed

15.2 sec in total

First Response

730 ms

Resources Loaded

13.6 sec

Page Rendered

837 ms

mehrli.uz screenshot

About Website

Visit mehrli.uz now to see the best up-to-date Mehrli content and also check out these interesting facts you probably never knew about mehrli.uz

"Imkoniyat cheklangan yoshlar va bolalar markazi" nodavlat notijorat tashkiloti

Visit mehrli.uz

Key Findings

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

Performance Metrics

mehrli.uz performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value19.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

mehrli.uz

730 ms

mehrli.uz

6822 ms

css2

42 ms

all.min.css

47 ms

698 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Mehrli.uz, 77% (54 requests) were made to Static.mehrli.uz and 7% (5 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Mehrli.uz.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 162.4 kB

  • Original 192.5 kB
  • After minification 173.2 kB
  • After compression 30.0 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 162.4 kB or 84% of the original size.

Image Optimization

-20%

Potential reduce by 247.9 kB

  • Original 1.2 MB
  • After minification 969.1 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. Obviously, Mehrli needs image optimization as it can save up to 247.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 8.4 kB

  • Original 183.3 kB
  • After minification 183.3 kB
  • After compression 174.8 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

-0%

Potential reduce by 46 B

  • Original 14.5 kB
  • After minification 14.5 kB
  • After compression 14.5 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. Mehrli.uz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (30%)

Requests Now

61

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mehrli.uz

mehrli.uz

730 ms

mehrli.uz

mehrli.uz

6822 ms

css2

css2

42 ms

all.min.css

all.min.css

47 ms

698 ms

css

css

59 ms

app.min.css

app.min.css

1443 ms

custom.css

custom.css

1274 ms

jquery.js

jquery.js

1808 ms

yii.js

yii.js

1530 ms

jquery.pjax.js

jquery.pjax.js

2325 ms

app.min.js

app.min.js

2394 ms

map.js

map.js

2529 ms

script.js

script.js

2754 ms

checkout.js

checkout.js

1362 ms

widget.js

widget.js

176 ms

full-e45524872324c0fb9cf3b243b7b8b15ef5266531.js

full-e45524872324c0fb9cf3b243b7b8b15ef5266531.js

1166 ms

mehrli-logo.png

mehrli-logo.png

1856 ms

home-baby-1.png

home-baby-1.png

2315 ms

home-baby-2.png

home-baby-2.png

3273 ms

bagel.svg

bagel.svg

2075 ms

circles.svg

circles.svg

2105 ms

cross.svg

cross.svg

2300 ms

halfCircles.svg

halfCircles.svg

2326 ms

sun.svg

sun.svg

2356 ms

triangle.svg

triangle.svg

2551 ms

lines.svg

lines.svg

2550 ms

hand.png

hand.png

2578 ms

jar.png

jar.png

2608 ms

500_320_80_1235621886.png

500_320_80_1235621886.png

3979 ms

video-play-btn.png

video-play-btn.png

2784 ms

video-text.png

video-text.png

2803 ms

emoji-month.png

emoji-month.png

3081 ms

emoji-couple.png

emoji-couple.png

2859 ms

babies.png

babies.png

3524 ms

emoji-home.png

emoji-home.png

3307 ms

290_190_80_45723659.png

290_190_80_45723659.png

3643 ms

290_190_80_1972828645.png

290_190_80_1972828645.png

4114 ms

290_190_80_1244660615.jpg

290_190_80_1244660615.jpg

3521 ms

290_190_80_1744747749.jpg

290_190_80_1744747749.jpg

3560 ms

100_100_95_705626859.jpg

100_100_95_705626859.jpg

3770 ms

100_100_95_2922900436.png

100_100_95_2922900436.png

3758 ms

100_100_95_4018925530.png

100_100_95_4018925530.png

3811 ms

100_100_95_134553983.png

100_100_95_134553983.png

3895 ms

100_100_95_2578554050.png

100_100_95_2578554050.png

3992 ms

100_100_95_521241916.png

100_100_95_521241916.png

3460 ms

100_100_95_1453797221.png

100_100_95_1453797221.png

3285 ms

fa-solid-900.ttf

fa-solid-900.ttf

20 ms

fa-regular-400.ttf

fa-regular-400.ttf

49 ms

100_100_95_3815886754.png

100_100_95_3815886754.png

3330 ms

100_100_95_561454708.png

100_100_95_561454708.png

3768 ms

grab.cur

grab.cur

139 ms

grabbing.cur

grabbing.cur

184 ms

help.cur

help.cur

328 ms

zoom_in.cur

zoom_in.cur

418 ms

100_100_95_730939602.png

100_100_95_730939602.png

2611 ms

100_100_95_384919906.png

100_100_95_384919906.png

2588 ms

100_100_95_3725714962.png

100_100_95_3725714962.png

2498 ms

100_100_95_240630981.png

100_100_95_240630981.png

2515 ms

widget_app_base_1729588264776.js

widget_app_base_1729588264776.js

17 ms

100_100_95_2765206898.png

100_100_95_2765206898.png

2345 ms

100_100_95_2215222689.jpg

100_100_95_2215222689.jpg

2390 ms

100_100_95_1506086783.jpg

100_100_95_1506086783.jpg

2910 ms

100_100_95_1815165442.png

100_100_95_1815165442.png

2272 ms

100_100_95_3573004468.png

100_100_95_3573004468.png

2308 ms

100_100_95_2984835858.jpg

100_100_95_2984835858.jpg

2327 ms

100_100_95_1808205525.png

100_100_95_1808205525.png

2342 ms

100_100_95_3204362304.png

100_100_95_3204362304.png

2754 ms

100_100_95_1018074369.jpg

100_100_95_1018074369.jpg

2816 ms

100_100_95_471283652.png

100_100_95_471283652.png

2325 ms

Accessibility Review

mehrli.uz accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Links do not have a discernible name

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.

Best Practices

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

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

mehrli.uz SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    UZ

  • Language Claimed

    UZ

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mehrli.uz can be misinterpreted by Google and other search engines. Our service has detected that Uzbek is used on the page, and it matches the claimed language. Our system also found out that Mehrli.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

mehrli.uz

Open Graph data is detected on the main page of Mehrli. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: