5.7 sec in total
800 ms
4.8 sec
165 ms
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
Качественный хостинг от UZSCINET. Профессиональная техническая поддержка
Visit fan.uzWe analyzed Fan.uz page load time and found that the first response time was 800 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fan.uz performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value8.6 s
1/100
25%
Value10.9 s
6/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
800 ms
2766 ms
399 ms
399 ms
400 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fan.uz, 97% (30 requests) were made to Scinet.uz. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Scinet.uz.
Page size can be reduced by 38.0 kB (52%)
73.7 kB
35.6 kB
In fact, the total size of Fan.uz main page is 73.7 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. Only 5% of websites need less resources to load. Images take 27.5 kB which makes up the majority of the site volume.
Potential reduce by 17.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 2.7 kB, which is 12% 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 17.7 kB or 77% of the original size.
Potential reduce by 1.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. Fan images are well optimized though.
Potential reduce by 207 B
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 207 B or 47% of the original size.
Potential reduce by 19.0 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 needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 84% of the original size.
Number of requests can be reduced by 19 (66%)
29
10
The browser has sent 29 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 6 to 1 for CSS and as a result speed up the page load time.
fan.uz
800 ms
2766 ms
style.css
399 ms
style.css
399 ms
style.css
400 ms
style.css
400 ms
styles.css
404 ms
template_styles.css
812 ms
script.js
600 ms
woman.jpg
984 ms
home.gif
597 ms
search.gif
597 ms
map.gif
603 ms
printer.gif
797 ms
woman_breast.jpg
798 ms
woman_arms.jpg
802 ms
left-column-head.gif
805 ms
left-column-bottom.gif
996 ms
instmech.jpg
997 ms
shadow.gif
1006 ms
word.jpg
818 ms
favicon_wordpressss.jpg
824 ms
header_bg.gif
357 ms
line.gif
372 ms
logo.gif
373 ms
header_menu_corner.gif
387 ms
header_menu_bg.gif
387 ms
separator.gif
393 ms
left_menu_bg.gif
553 ms
content_block_left.gif
570 ms
content_block_bg.gif
571 ms
fan.uz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Document doesn't have a <title> element
Links do not have a discernible name
fan.uz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fan.uz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
UZ
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
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: