Tools & Wizards About Us
piu.rs screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

piu.rs

Jedinica za upravljanje projektom / Project Implementation Unit

Page Load Speed

4 sec in total

First Response

500 ms

Resources Loaded

2.1 sec

Page Rendered

1.4 sec

piu.rs screenshot

About Website

Welcome to piu.rs homepage info - get ready to check Piu best content for Serbia right away, or after learning these important things about piu.rs

Pružаnje uslugа konsаltingа, menаdžmentа i nаdzorа u vezi sа uprаvljаnjem projektom; pripremа, evаluаcijа i objаvljivаnje tenderа; koordinаcijа аktivnosti i pružаnje аdministrаtivnih uslugа projektnim...

Visit piu.rs

Key Findings

We analyzed Piu.rs page load time and found that the first response time was 500 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

piu.rs performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

piu.rs

500 ms

piu.rs

488 ms

page-homepage.css

99 ms

style.min.css

198 ms

page-homepage.js

292 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Piu.rs and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Piu.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.8 kB (6%)

Content Size

4.2 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piu.rs main page is 4.2 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. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 45.0 kB

  • Original 53.2 kB
  • After minification 40.1 kB
  • After compression 8.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 13.1 kB, which is 25% 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 45.0 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 203.4 kB

  • Original 4.1 MB
  • After minification 3.9 MB

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. Piu images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 1.4 kB

  • Original 19.5 kB
  • After minification 19.5 kB
  • After compression 18.2 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. Piu.rs has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Piu. According to our analytics all requests are already optimized.

Network Requests Diagram

piu.rs

piu.rs

500 ms

piu.rs

piu.rs

488 ms

page-homepage.css

page-homepage.css

99 ms

style.min.css

style.min.css

198 ms

page-homepage.js

page-homepage.js

292 ms

logo_big-2.png

logo_big-2.png

293 ms

588-full-2.jpg

588-full-2.jpg

692 ms

587-full-6.jpg

587-full-6.jpg

597 ms

586-full-5.jpg

586-full-5.jpg

497 ms

shutterstock_1902078616%D0%B3%D1%84%D0%B3%D1%84-1.jpg

shutterstock_1902078616%D0%B3%D1%84%D0%B3%D1%84-1.jpg

887 ms

p2_2.jpg

p2_2.jpg

1075 ms

p3_2.png

p3_2.png

878 ms

Rectangle-2.jpg

Rectangle-2.jpg

890 ms

hero__img-pattern.png

hero__img-pattern.png

695 ms

Group-7152.png

Group-7152.png

788 ms

Group-7151.png

Group-7151.png

793 ms

Group-7150.png

Group-7150.png

887 ms

Rectangle-215.jpg

Rectangle-215.jpg

892 ms

Group-7207.png

Group-7207.png

975 ms

Rectangle-216.jpg

Rectangle-216.jpg

984 ms

Group-7184.png

Group-7184.png

983 ms

Rectangle-217.jpg

Rectangle-217.jpg

987 ms

Group-7185.png

Group-7185.png

989 ms

Rectangle-218.jpg

Rectangle-218.jpg

1072 ms

Group-7186.png

Group-7186.png

1080 ms

logo_small.png

logo_small.png

1081 ms

republic_logo.png

republic_logo.png

1084 ms

Accessibility Review

piu.rs accessibility score

40

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

piu.rs best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

piu.rs SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    SR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piu.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it matches the claimed language. Our system also found out that Piu.rs 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.

Social Sharing Optimization

piu.rs

Open Graph description is not detected on the main page of Piu. 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: