4.4 sec in total
508 ms
3.6 sec
265 ms
Visit usc.pl now to see the best up-to-date Usc content for Poland and also check out these interesting facts you probably never knew about usc.pl
Planujesz ślub i wesele? Urodziło Ci się dziecko? Nie jesteś pewien gdzie i jak załatwić formalności? Zajrzyj na www.usc.pl - Już łatwiej być nie może!
Visit usc.plWe analyzed Usc.pl page load time and found that the first response time was 508 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
usc.pl performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.9 s
52/100
25%
Value5.2 s
60/100
10%
Value70 ms
99/100
30%
Value0.001
100/100
15%
Value3.9 s
88/100
10%
508 ms
95 ms
113 ms
336 ms
448 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 49% of them (53 requests) were addressed to the original Usc.pl, 13% (14 requests) were made to Apis.google.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Usc.pl.
Page size can be reduced by 212.4 kB (27%)
786.7 kB
574.3 kB
In fact, the total size of Usc.pl main page is 786.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. 65% of websites need less resources to load. Images take 507.9 kB which makes up the majority of the site volume.
Potential reduce by 63.8 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 9.8 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 63.8 kB or 81% of the original size.
Potential reduce by 16.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. Usc images are well optimized though.
Potential reduce by 81.0 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 81.0 kB or 56% of the original size.
Potential reduce by 51.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. Usc.pl needs all CSS files to be minified and compressed as it can save up to 51.5 kB or 93% of the original size.
Number of requests can be reduced by 48 (46%)
104
56
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Usc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.usc.pl
508 ms
plusone.js
95 ms
arkusz.css
113 ms
style.css
336 ms
jquery.js
448 ms
jquery.bt.min.js
226 ms
stwdscript-1.1-free.js
352 ms
simpletreemenu.js
351 ms
simpletree.css
353 ms
xgemius.js
233 ms
brand
32 ms
all.js
52 ms
brand
76 ms
cb=gapi.loaded_0
17 ms
fpdata.js
139 ms
dc.js
36 ms
gplus-16.png
133 ms
tweeter.png
342 ms
toppasek.png
134 ms
lang_pl.png
134 ms
lang_en.png
166 ms
lang_de.png
134 ms
lang_ru.png
166 ms
lang_ua.png
167 ms
rss.png
226 ms
595a.jpg
224 ms
594a.jpg
395 ms
593a.jpg
412 ms
591a.jpg
412 ms
590a.jpg
411 ms
dodaj_firme.png
396 ms
wyszukiwarka.png
395 ms
big_01110010066000.jpg
556 ms
arrow_right.png
495 ms
wnioski_usc.png
496 ms
rtf.png
529 ms
pdf.png
534 ms
wnioski_waga.png
530 ms
wnioski_pisma.png
625 ms
595.jpg
624 ms
593.jpg
647 ms
577.jpg
646 ms
594.jpg
655 ms
logo_ig.jpg
672 ms
logo_technika.jpg
712 ms
logo_efrr.jpg
725 ms
combine.png
2025 ms
google_custom_search_watermark.gif
94 ms
contentbg.png
751 ms
wd_belka.png
750 ms
wa_ng.png
1424 ms
aktualnosci_belka.png
808 ms
wizytowki_belka.png
811 ms
artykuly_belka.png
855 ms
wnioski_belka.png
858 ms
widgets.js
67 ms
__utm.gif
45 ms
cb=gapi.loaded_1
44 ms
cb=gapi.loaded_2
64 ms
fastbutton
142 ms
badge
164 ms
238 ms
xd_arbiter.php
75 ms
xd_arbiter.php
107 ms
lsget.html
302 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
59 ms
forum_belka.png
809 ms
dziecko_belka.png
820 ms
malzenstwo_belka.png
864 ms
postmessageRelay
58 ms
zgon_belka.png
840 ms
inne_belka.png
887 ms
tagi_belka.png
905 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
15 ms
api.js
46 ms
core:rpc:shindig.random:shindig.sha1.js
115 ms
2536007149-postmessagerelay.js
12 ms
newsletter_belka.png
895 ms
fbpodklad.png
897 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
27 ms
likebox.php
256 ms
rs=AGLTcCOldiz7BxP14VvzYLiKh1pcAfK41A
27 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
27 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
82 ms
photo.jpg
142 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
180 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
198 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
236 ms
jot
173 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
32 ms
rs=AGLTcCPSFgQkd_9SlrQhvNKhZVah0ITF-Q
23 ms
xYm_UD1pmAz.css
46 ms
TGpOWuX6Pv8.css
50 ms
_rx8naC75Dy.js
67 ms
x5F9OMjKyLw.js
86 ms
ICDbTSzjQEg.js
85 ms
TTCre3391I0.js
84 ms
rexdot.js
124 ms
419419_336403506412165_887987107_n.jpg
48 ms
423755_336414933077689_259913252_n.jpg
29 ms
12438961_159044691130278_6363427639681482999_n.jpg
28 ms
1379841_10150004552801901_469209496895221757_n.jpg
26 ms
12310617_10205488421026217_3912184282691425093_n.jpg
29 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
8 ms
I6-MnjEovm5.js
9 ms
vlXaquuXMrr.js
18 ms
print.css
114 ms
usc.pl 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
Links do not have a discernible name
usc.pl 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
usc.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Usc.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Usc.pl 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.
usc.pl
Open Graph description is not detected on the main page of Usc. 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: