Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

Page Load Speed

2.1 sec in total

First Response

156 ms

Resources Loaded

1.3 sec

Page Rendered

706 ms

uz3.ru screenshot

About Website

Click here to check amazing Uz 3 content. Otherwise, check out these important facts you probably never knew about uz3.ru

Your description

Visit uz3.ru

Key Findings

We analyzed Uz3.ru page load time and found that the first response time was 156 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

uz3.ru performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

leadmagnet.ru

156 ms

css

25 ms

css

36 ms

bootstrap.min.css

91 ms

rs-settings.css

88 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Uz3.ru, 28% (32 requests) were made to Maps.google.com and 10% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (363 ms) relates to the external source Leadmagnet.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (30%)

Content Size

3.4 MB

After Optimization

2.4 MB

In fact, the total size of Uz3.ru main page is 3.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.8 kB

  • Original 65.2 kB
  • After minification 56.7 kB
  • After compression 9.4 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 8.5 kB, which is 13% 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 55.8 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 191.7 kB

  • Original 2.2 MB
  • After minification 2.0 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. Uz 3 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 568.2 kB

  • Original 885.5 kB
  • After minification 834.9 kB
  • After compression 317.3 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 568.2 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 202.1 kB

  • Original 235.6 kB
  • After minification 220.2 kB
  • After compression 33.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. Uz3.ru needs all CSS files to be minified and compressed as it can save up to 202.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (27%)

Requests Now

102

After Optimization

74

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

Accessibility Review

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

Document doesn't have a <title> element

Best Practices

uz3.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

uz3.ru SEO score

50

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uz3.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Uz3.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

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