3.5 sec in total
642 ms
2.6 sec
192 ms
Welcome to pria.ee homepage info - get ready to check PRIA best content for Estonia right away, or after learning these important things about pria.ee
Põllumajanduse Registrite ja Informatsiooni Amet (PRIA) on Eesti Vabariigi Põllumajandusministeeriumi valitsemisalas olev valitsusasutus, mis loodi 2000. aasta suvel. PRIA ülesandeks on riiklike toetu...
Visit pria.eeWe analyzed Pria.ee page load time and found that the first response time was 642 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.
pria.ee performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value9.9 s
0/100
25%
Value5.6 s
53/100
10%
Value620 ms
48/100
30%
Value0.033
100/100
15%
Value8.7 s
36/100
10%
642 ms
357 ms
697 ms
357 ms
703 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 Pria.ee, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pria.ee.
Page size can be reduced by 278.1 kB (43%)
639.5 kB
361.4 kB
In fact, the total size of Pria.ee main page is 639.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. 30% of websites need less resources to load. Images take 396.3 kB which makes up the majority of the site volume.
Potential reduce by 22.1 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.4 kB, which is 35% 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 22.1 kB or 82% of the original size.
Potential reduce by 89.5 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, PRIA needs image optimization as it can save up to 89.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 97.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 97.2 kB or 71% of the original size.
Potential reduce by 69.3 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. Pria.ee needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 87% of the original size.
Number of requests can be reduced by 22 (39%)
57
35
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PRIA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pria.ee
642 ms
lightbox.css
357 ms
index_new.css
697 ms
fontchange.css
357 ms
jquery.js
703 ms
jquery.cookie.js
356 ms
general.js
356 ms
swfobject.js
470 ms
ga.js
26 ms
print.php
458 ms
__utm.gif
34 ms
close.png
382 ms
loading.gif
267 ms
prev.png
284 ms
next.png
396 ms
bg.gif
115 ms
head_bg.png
986 ms
logo.png
381 ms
lang.png
407 ms
lang_bg_sel.png
494 ms
lang_bg.png
495 ms
tabs-active.png
511 ms
tabs-inactive.png
510 ms
print_logo.gif
512 ms
mmenu_sepa.gif
607 ms
txt_search.gif
607 ms
btn_search.gif
623 ms
btn_search_detail.png
624 ms
submenu_bg.gif
625 ms
box99b.gif
721 ms
box99b_sepa.gif
720 ms
important.png
736 ms
important-fade.png
739 ms
important-sep.png
738 ms
important-bullet.png
833 ms
box44.gif
835 ms
cat_sepa.gif
850 ms
box11.gif
851 ms
box11_content.gif
853 ms
box22_sepa.gif
947 ms
box66.gif
948 ms
box66_content.gif
963 ms
box22.gif
965 ms
box22_content.gif
966 ms
nl_txt.gif
1060 ms
btn_nl1.gif
1061 ms
btn_nl2.gif
967 ms
captcha.php
855 ms
85.jpg
803 ms
74.jpg
720 ms
86.png
911 ms
47.jpg
775 ms
mak_logo_50.png
790 ms
5.gif
796 ms
ekf_logo_50.png
720 ms
foot_logo.png
740 ms
ajax-loader.gif
783 ms
foot_bg.gif
805 ms
foot_sepa.gif
805 ms
pria.ee accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA progressbar elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
pria.ee 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
Page has valid source maps
pria.ee 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
Tap targets are not sized appropriately
ET
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pria.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian 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 Pria.ee 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.
pria.ee
Open Graph description is not detected on the main page of PRIA. 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: