Tools & Wizards About Us
passport.uzreport.uz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

passport.uzreport.uz

Новости Узбекистана сегодня – последние новости Ташкента | UzReport.news

Page Load Speed

5.1 sec in total

First Response

709 ms

Resources Loaded

4.2 sec

Page Rendered

203 ms

passport.uzreport.uz screenshot

About Website

Click here to check amazing Passport Uz Report content for Uzbekistan. Otherwise, check out these important facts you probably never knew about passport.uzreport.uz

Новости Узбекистана и Ташкента: последние новости сегодня, фото и видео, самые актуальные новости Узбекистана на UZREPORT TV и FUTBOL TV.

Visit passport.uzreport.uz

Key Findings

We analyzed Passport.uzreport.uz page load time and found that the first response time was 709 ms and then it took 4.4 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

passport.uzreport.uz performance score

0

Network Requests Diagram

passport.uzreport.uz

709 ms

style_osnov4.css

473 ms

share.js

260 ms

zp.js

666 ms

view.php

695 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Passport.uzreport.uz, 42% (10 requests) were made to Uzreport.uz and 13% (3 requests) were made to W.uptolike.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Uzreport.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.4 kB (52%)

Content Size

61.0 kB

After Optimization

29.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Passport.uzreport.uz main page is 61.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 27.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.8 kB

  • Original 20.4 kB
  • After minification 20.2 kB
  • After compression 5.6 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 14.8 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 202 B

  • Original 2.1 kB
  • After minification 1.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. Passport Uz Report images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 7.3 kB

  • Original 27.4 kB
  • After minification 25.3 kB
  • After compression 20.1 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 7.3 kB or 27% of the original size.

CSS Optimization

-83%

Potential reduce by 9.2 kB

  • Original 11.0 kB
  • After minification 9.5 kB
  • After compression 1.8 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. Passport.uzreport.uz needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

passport.uzreport.uz

passport.uzreport.uz

709 ms

style_osnov4.css

style_osnov4.css

473 ms

share.js

share.js

260 ms

zp.js

zp.js

666 ms

view.php

view.php

695 ms

countp.fgi

countp.fgi

136 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

238 ms

head_strelka.gif

head_strelka.gif

52 ms

line_proekt.gif

line_proekt.gif

837 ms

logo_r.gif

logo_r.gif

2024 ms

ico_face.gif

ico_face.gif

103 ms

ico_twit.gif

ico_twit.gif

874 ms

ico_rss.gif

ico_rss.gif

900 ms

ico_dom.gif

ico_dom.gif

1927 ms

line_tri.gif

line_tri.gif

148 ms

spam.cgi

spam.cgi

267 ms

view.php

view.php

638 ms

watch.js

watch.js

2 ms

count.fgi

count.fgi

99 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

20 ms

watch.js

watch.js

1 ms

impression.html

impression.html

329 ms

extra.js

extra.js

982 ms

SEO Factors

passport.uzreport.uz SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Passport.uzreport.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 Passport.uzreport.uz main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

passport.uzreport.uz

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: