3.3 sec in total
477 ms
2.6 sec
257 ms
Welcome to krus.gov.pl homepage info - get ready to check Krus best content for Poland right away, or after learning these important things about krus.gov.pl
KRUS prowadzi ubezpieczenia emerytalno-rentowe, wypadkowe, chorobowe i macierzyńskie dla rolników.
Visit krus.gov.plWe analyzed Krus.gov.pl page load time and found that the first response time was 477 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
krus.gov.pl performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value10.1 s
0/100
25%
Value9.6 s
11/100
10%
Value120 ms
97/100
30%
Value0.37
29/100
15%
Value10.4 s
24/100
10%
477 ms
524 ms
115 ms
226 ms
229 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Krus.gov.pl, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Krus.gov.pl.
Page size can be reduced by 253.4 kB (52%)
484.5 kB
231.1 kB
In fact, the total size of Krus.gov.pl main page is 484.5 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. 20% of websites need less resources to load. Javascripts take 252.2 kB which makes up the majority of the site volume.
Potential reduce by 24.2 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 5.4 kB, which is 17% 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 24.2 kB or 78% 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. Obviously, Krus needs image optimization as it can save up to 16.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 165.2 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 165.2 kB or 66% of the original size.
Potential reduce by 47.8 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. Krus.gov.pl needs all CSS files to be minified and compressed as it can save up to 47.8 kB or 80% of the original size.
Number of requests can be reduced by 20 (35%)
57
37
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
krus.gov.pl
477 ms
www.krus.gov.pl
524 ms
stylesheet_819be57eb7.css
115 ms
screen.css
226 ms
krus_rwd.css
229 ms
nivo-slider.css
227 ms
cookies_css.css
232 ms
skin.css
235 ms
pushy.css
237 ms
jcarousel.responsive.css
335 ms
shadowbox.css
345 ms
jquery-1.7.2.min.js
572 ms
jquery.nivo.slider.pack.3.js
356 ms
cookie.js
359 ms
jquery.jcarousel.min_.js
469 ms
shadowbox.js
673 ms
krus.js
456 ms
contrast.js
467 ms
scroll.js
469 ms
pushy.js
568 ms
javascript_9a38f34785.js
580 ms
libraries.css
364 ms
krus.css
477 ms
logo_krus.png
121 ms
btn_arrow.png
113 ms
logo_bip.gif
117 ms
btn_search.png
119 ms
bg_h_menu_c.png
118 ms
bg_left_menu.jpg
116 ms
bg_sprite_ico.png
224 ms
bg_point.gif
230 ms
bg_slideshow.gif
228 ms
BGR_baner_logo_180_2016.jpg
351 ms
baner_ISSA_kolokwium_2016_w.jpg
350 ms
badania_logo_baner_2015_750.jpg
240 ms
baner_ekrus_2016.png
334 ms
bg_date.gif
338 ms
line.gif
342 ms
RTEmagicC_wydarzenia_prewencyjne.gif.gif
353 ms
btn_more_orange.gif
446 ms
dziennik-ikona_03.jpg
450 ms
Issa_globus.jpg
454 ms
btn_more.gif
463 ms
BGR_logo_2016_70.jpg
467 ms
kpdd_2015_konik_80.jpg
467 ms
szanuj_zycie_70.jpg
556 ms
plakat_upadek_miniatura_70.jpg
672 ms
chron_dziecko_okladka_70.jpg
568 ms
konkurs_badania_przesiewowe.gif
576 ms
logo_UE_70.jpg
582 ms
bg_niezbednik.jpg
579 ms
bg_polecane_certyfikaty.jpg
667 ms
zintegrowany_system_zarzadzania.gif
681 ms
jakosc_w_administracji.gif
688 ms
analytics.js
24 ms
collect
12 ms
loading.gif
115 ms
arrows.png
114 ms
bullets.png
116 ms
krus.gov.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
Image elements do not have [alt] attributes
Links do not have a discernible name
krus.gov.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
Browser errors were logged to the console
krus.gov.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krus.gov.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 Krus.gov.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.
krus.gov.pl
Open Graph description is not detected on the main page of Krus. 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: