2.8 sec in total
635 ms
2 sec
157 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 635 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
elcom.rs performance score
name
value
score
weighting
Value2.5 s
65/100
10%
Value3.7 s
58/100
25%
Value3.5 s
88/100
10%
Value320 ms
76/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
635 ms
665 ms
270 ms
396 ms
296 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 44% of them (24 requests) were addressed to the original Elcom.rs, 22% (12 requests) were made to Apis.google.com and 15% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (665 ms) belongs to the original domain Elcom.rs.
Page size can be reduced by 34.4 kB (16%)
214.4 kB
180.0 kB
In fact, the total size of Elcom.rs main page is 214.4 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. 65% of websites need less resources to load. Javascripts take 100.7 kB which makes up the majority of the site volume.
Potential reduce by 15.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. 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 15.2 kB or 71% of the original size.
Potential reduce by 4.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. ELCOM images are well optimized though.
Potential reduce by 6.1 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 9.1 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 9.1 kB or 83% of the original size.
Number of requests can be reduced by 31 (63%)
49
18
The browser has sent 49 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 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
elcom.rs
635 ms
prototype.js
665 ms
scriptaculous.js
270 ms
lightbox.js
396 ms
lightbox.css
296 ms
lins.css
264 ms
plusone.js
59 ms
jsapi
39 ms
effects.js
141 ms
builder.js
136 ms
ga.js
28 ms
cb=gapi.loaded_0
18 ms
logo.gif
205 ms
img_general.jpg
264 ms
sr.gif
205 ms
en.gif
207 ms
dots.gif
206 ms
rpfeil.gif
207 ms
DSC_0339s.JPG
504 ms
youtube.PNG
271 ms
fkloznica-120x60.jpg
486 ms
Displej_glasanje_s.JPG
486 ms
pos_s.gif
485 ms
kabina1.jpg
646 ms
radar_s.jpg
485 ms
dots2.gif
594 ms
49 ms
__utm.gif
28 ms
default+en.css
7 ms
minimalist.css
14 ms
default+en.I.js
10 ms
minimalist.css
19 ms
cb=gapi.loaded_1
67 ms
cb=gapi.loaded_2
71 ms
page
142 ms
async-ads.js
88 ms
google_custom_search_watermark.gif
80 ms
small-logo.png
46 ms
clear.gif
46 ms
loading.gif
406 ms
closelabel.gif
428 ms
postmessageRelay
50 ms
3193398744-postmessagerelay.js
41 ms
rpc:shindig_random.js
41 ms
rs=AGLTcCNwBglnRFJRg0mRD_l9WzbpnP29GQ
14 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
37 ms
rs=AGLTcCPwySJIDyCsiyt9g0BdSkQq3zwjug
87 ms
photo.jpg
233 ms
cb=gapi.loaded_0
135 ms
rs=AGLTcCPwySJIDyCsiyt9g0BdSkQq3zwjug
31 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
90 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
93 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
101 ms
rs=AGLTcCPwySJIDyCsiyt9g0BdSkQq3zwjug
13 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
UTF-8
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 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.
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: