Tools & Wizards About Us
fan.uz screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fan.uz

Page Load Speed

3 sec in total

First Response

609 ms

Resources Loaded

2.4 sec

Page Rendered

60 ms

fan.uz screenshot

About Website

Welcome to fan.uz homepage info - get ready to check Fan best content for Russia right away, or after learning these important things about fan.uz

Visit fan.uz

Key Findings

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

Performance Metrics

fan.uz performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

fan.uz

609 ms

fan.uz

590 ms

style.css

288 ms

all.css

34 ms

normalize.min.css

30 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 63% of them (22 requests) were addressed to the original Fan.uz, 17% (6 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (703 ms) belongs to the original domain Fan.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.9 kB (14%)

Content Size

83.4 kB

After Optimization

71.5 kB

  • HTML
  • CSS

In fact, the total size of Fan.uz main page is 83.4 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. 25% of websites need less resources to load. CSS take 76.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 5.3 kB

  • Original 6.7 kB
  • After minification 4.0 kB
  • After compression 1.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 2.7 kB, which is 40% 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 5.3 kB or 80% of the original size.

CSS Optimization

-9%

Potential reduce by 6.6 kB

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

Requests Breakdown

Number of requests can be reduced by 22 (92%)

Requests Now

24

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fan. 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 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fan.uz

fan.uz

609 ms

fan.uz

fan.uz

590 ms

style.css

style.css

288 ms

all.css

all.css

34 ms

normalize.min.css

normalize.min.css

30 ms

modernizr.custom.js

modernizr.custom.js

419 ms

jquery.min.js

jquery.min.js

564 ms

jquery.easings.min.js

jquery.easings.min.js

420 ms

bootstrap.min.js

bootstrap.min.js

430 ms

velocity.min.js

velocity.min.js

432 ms

notifyMe.js

notifyMe.js

432 ms

vegas.js

vegas.js

559 ms

photoswipe.js

photoswipe.js

703 ms

photoswipe-ui-default.js

photoswipe-ui-default.js

573 ms

main.js

main.js

574 ms

font-awesome.min.css

font-awesome.min.css

288 ms

ionicons.min.css

ionicons.min.css

412 ms

bootstrap.min.css

bootstrap.min.css

418 ms

animate.css

animate.css

430 ms

photoswipe.css

photoswipe.css

431 ms

default-skin.css

default-skin.css

432 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

551 ms

vegas.css

vegas.css

555 ms

css

css

19 ms

css

css

35 ms

css

css

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

32 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

36 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

287 ms

fa-solid-900.woff

fa-solid-900.woff

24 ms

fa-regular-400.woff

fa-regular-400.woff

42 ms

Accessibility Review

fan.uz accessibility score

80

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.

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

High

Links do not have a discernible name

Best Practices

fan.uz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fan.uz SEO score

83

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

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

    UZ

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fan.uz

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