3.1 sec in total
461 ms
2.5 sec
97 ms
Click here to check amazing ELCOM content. Otherwise, check out these important facts you probably never knew about elcom.rs
elcom.rs - Kosta Manojlovic
Visit elcom.rsWe analyzed Elcom.rs page load time and found that the first response time was 461 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
elcom.rs performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value3.5 s
64/100
25%
Value3.4 s
90/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value4.7 s
80/100
10%
461 ms
474 ms
368 ms
511 ms
461 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Elcom.rs, 47% (18 requests) were made to Cdn.elcom.rs and 18% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (970 ms) relates to the external source Developers.google.com.
Page size can be reduced by 50.7 kB (12%)
425.6 kB
374.9 kB
In fact, the total size of Elcom.rs main page is 425.6 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. Javascripts take 315.6 kB which makes up the majority of the site volume.
Potential reduce by 13.0 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.0 kB or 70% of the original size.
Potential reduce by 113 B
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. ELCOM images are well optimized though.
Potential reduce by 1.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.
Potential reduce by 36.0 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. Elcom.rs needs all CSS files to be minified and compressed as it can save up to 36.0 kB or 84% of the original size.
Number of requests can be reduced by 19 (56%)
34
15
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELCOM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
elcom.rs
461 ms
elcom.rs
474 ms
lightbox.css
368 ms
lightbox.js
511 ms
lins.css
461 ms
plusone.js
20 ms
analytics.js
511 ms
sr.gif
526 ms
en.gif
507 ms
dots.png
665 ms
cb=gapi.loaded_0
6 ms
cse.js
80 ms
logo.gif
168 ms
img_general.jpg
98 ms
rpfeil.gif
192 ms
DSC_0339s.jpg
191 ms
youtube.png
190 ms
fkloznica-120x60.jpg
237 ms
Displej_glasanje_s.jpg
255 ms
pos_s.gif
297 ms
kabina1.jpg
367 ms
radar_s.jpg
255 ms
dots2.png
310 ms
cb=gapi.loaded_1
24 ms
cb=gapi.loaded_2
26 ms
page
34 ms
collect
42 ms
postmessageRelay
99 ms
cse_element__en.js
31 ms
default+en.css
83 ms
default.css
86 ms
async-ads.js
29 ms
branding.png
27 ms
clear.png
25 ms
developers.google.com
970 ms
3604799710-postmessagerelay.js
46 ms
rpc:shindig_random.js
33 ms
cb=gapi.loaded_0
4 ms
elcom.rs 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
elcom.rs best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
elcom.rs SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
SR
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elcom.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian 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 Elcom.rs main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
elcom.rs
Open Graph description is not detected on the main page of ELCOM. 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: