5.5 sec in total
721 ms
4.5 sec
211 ms
Welcome to uloz.to homepage info - get ready to check Uloz best content for Czech Republic right away, or after learning these important things about uloz.to
Visit uloz.toWe analyzed Uloz.to page load time and found that the first response time was 721 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
uloz.to performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.6 s
0/100
25%
Value9.0 s
14/100
10%
Value5,190 ms
0/100
30%
Value1
2/100
15%
Value14.3 s
9/100
10%
721 ms
1879 ms
1400 ms
2182 ms
1141 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Uloz.to, 35% (17 requests) were made to Static.uloz.to and 13% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Static.uloz.to.
Page size can be reduced by 1.0 MB (46%)
2.3 MB
1.2 MB
In fact, the total size of Uloz.to main page is 2.3 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. 25% of websites need less resources to load. Javascripts take 988.9 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.0 kB or 66% of the original size.
Potential reduce by 34.7 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. Uloz images are well optimized though.
Potential reduce by 699.5 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 699.5 kB or 71% of the original size.
Potential reduce by 294.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. Uloz.to needs all CSS files to be minified and compressed as it can save up to 294.0 kB or 83% of the original size.
Number of requests can be reduced by 23 (58%)
40
17
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uloz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
uloz.to
721 ms
ulozto.css
1879 ms
jquery-ui-1.8.16.custom.css
1400 ms
ulozto.min.js
2182 ms
main.min.js
1141 ms
code
823 ms
bb_one2n.js
932 ms
css
27 ms
j.php
32 ms
cz.png
121 ms
sk.png
138 ms
en.png
137 ms
pl.png
135 ms
gtm.js
57 ms
bbnaut-lib-1.7.5.min.js
458 ms
thumbnail.js
224 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
55 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
56 ms
v.gif
24 ms
analytics.js
37 ms
watch.js
3 ms
fbevents.js
44 ms
linkid.js
12 ms
ecommerce.js
26 ms
123 ms
collect
90 ms
collect
22 ms
collect
11 ms
collect
25 ms
collect
95 ms
collect
113 ms
ga-audiences
64 ms
ga-audiences
46 ms
ga-audiences
40 ms
421 ms
ulozto-logo.svg
162 ms
xxuJ1mG.640x360.6.jpg
1069 ms
xZL7ZbPh.640x360.6.jpg
1081 ms
xPZjB8Cz.640x360.5.jpg
1059 ms
xDXVRFi7.640x360.6.jpg
1067 ms
home-icons.png
152 ms
hp-live-logo.png
152 ms
fontawesome-webfont.woff
480 ms
co
226 ms
bandzone.png
123 ms
icons.png
370 ms
31sec-logo.png
127 ms
logo-titulin.png
123 ms
uloz.to accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
uloz.to best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
uloz.to SEO score
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
Tap targets are not sized appropriately
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uloz.to can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Uloz.to 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.
uloz.to
Open Graph description is not detected on the main page of Uloz. 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: