Tools & Wizards About Us
elpa.rs screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

elpa.rs

ELPA d.o.o. - Dobrodošli

Page Load Speed

2.8 sec in total

First Response

311 ms

Resources Loaded

2.3 sec

Page Rendered

183 ms

elpa.rs screenshot

About Website

Visit elpa.rs now to see the best up-to-date ELPA content for Serbia and also check out these interesting facts you probably never knew about elpa.rs

elpa

Visit elpa.rs

Key Findings

We analyzed Elpa.rs page load time and found that the first response time was 311 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

elpa.rs performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value22.9 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

elpa.rs

311 ms

www.elpa.rs

669 ms

css

64 ms

unsemantic.css

103 ms

responsive.css

193 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 91% of them (29 requests) were addressed to the original Elpa.rs, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (837 ms) belongs to the original domain Elpa.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.8 kB (25%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elpa.rs main page is 1.6 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 13.7 kB

  • Original 17.5 kB
  • After minification 16.4 kB
  • After compression 3.9 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 13.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 34.2 kB

  • Original 1.1 MB
  • After minification 1.1 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. ELPA images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 189.4 kB

  • Original 243.3 kB
  • After minification 177.4 kB
  • After compression 53.9 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 189.4 kB or 78% of the original size.

CSS Optimization

-84%

Potential reduce by 158.5 kB

  • Original 189.2 kB
  • After minification 158.0 kB
  • After compression 30.6 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. Elpa.rs needs all CSS files to be minified and compressed as it can save up to 158.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (48%)

Requests Now

27

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELPA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

elpa.rs

elpa.rs

311 ms

www.elpa.rs

www.elpa.rs

669 ms

css

css

64 ms

unsemantic.css

unsemantic.css

103 ms

responsive.css

responsive.css

193 ms

font-awesome.min.css

font-awesome.min.css

202 ms

juicy.css

juicy.css

198 ms

style.css

style.css

207 ms

red.css

red.css

206 ms

base.css

base.css

208 ms

layout.css

layout.css

287 ms

index.css

index.css

293 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

400 ms

bootstrap.custom.min.css

bootstrap.custom.min.css

305 ms

functions.min.js

functions.min.js

296 ms

bg-page-2.jpg

bg-page-2.jpg

705 ms

logo.png

logo.png

269 ms

Baner1.jpg

Baner1.jpg

304 ms

navbg.png

navbg.png

120 ms

slider-5-verzija-4.jpg

slider-5-verzija-4.jpg

592 ms

3%20mala%20slika.jpg

3%20mala%20slika.jpg

437 ms

1%20mala%20slika.jpg

1%20mala%20slika.jpg

535 ms

slika-4.jpg

slika-4.jpg

772 ms

1%20velika%20slika.jpg

1%20velika%20slika.jpg

701 ms

111.jpg

111.jpg

646 ms

2.jpg

2.jpg

642 ms

3.jpg

3.jpg

699 ms

jquery.juicy.js

jquery.juicy.js

730 ms

1bHRUMxmJHoup12DnI9XmQ.woff

1bHRUMxmJHoup12DnI9XmQ.woff

18 ms

I1Pn3gihk5vyP0Yw5GqKsQ.woff

I1Pn3gihk5vyP0Yw5GqKsQ.woff

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

837 ms

shoppie.scripts.js

shoppie.scripts.js

106 ms

Accessibility Review

elpa.rs accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

elpa.rs best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

elpa.rs SEO score

72

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

elpa.rs

Open Graph data is detected on the main page of ELPA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: