5.4 sec in total
1 sec
4.1 sec
340 ms
Visit plac.si now to see the best up-to-date Plac content and also check out these interesting facts you probably never knew about plac.si
Visit plac.si
We analyzed Plac.si page load time and found that the first response time was 1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
plac.si performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.6 s
1/100
25%
Value10.2 s
9/100
10%
Value9,170 ms
0/100
30%
Value0.089
92/100
15%
Value17.2 s
4/100
10%
1015 ms
332 ms
328 ms
333 ms
331 ms
Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Plac.si, 95% (166 requests) were made to Domene.si and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Plac.si.
Page size can be reduced by 229.6 kB (39%)
587.4 kB
357.9 kB
In fact, the total size of Plac.si main page is 587.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. 45% of websites need less resources to load. Images take 259.5 kB which makes up the majority of the site volume.
Potential reduce by 76.5 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 11.5 kB, which is 13% 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 76.5 kB or 90% of the original size.
Potential reduce by 873 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. Plac images are well optimized though.
Potential reduce by 114.4 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 114.4 kB or 58% of the original size.
Potential reduce by 37.8 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. Plac.si needs all CSS files to be minified and compressed as it can save up to 37.8 kB or 82% of the original size.
Number of requests can be reduced by 73 (43%)
171
98
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plac. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
plac.si
1015 ms
ddmenu.css
332 ms
scheme_common.css
328 ms
scheme_header.css
333 ms
scheme_news-slider.css
331 ms
coda-slider.css
334 ms
stylesheet.css
334 ms
language.css
406 ms
jquery.js
465 ms
jquery.easing.js
396 ms
jquery.coda-slider.js
398 ms
javascript.gp
175 ms
cookieControl-5.1.min.js
457 ms
ga.js
46 ms
bg_body.jpg
116 ms
logo.jpg
114 ms
header_home.jpg
115 ms
headline_default.jpg
148 ms
btn_go.png
117 ms
flag.gif
118 ms
bg_breadcrumb.gif
148 ms
paypal.png
148 ms
si.png
149 ms
eu.png
149 ms
generic.png
150 ms
pw.png
190 ms
in.png
193 ms
me.png
195 ms
al.png
196 ms
at.png
199 ms
ba.png
202 ms
be.png
254 ms
bg.png
257 ms
ca.png
259 ms
cat.png
262 ms
ch.png
265 ms
cy.png
266 ms
cz.png
464 ms
de.png
464 ms
dk.png
462 ms
ee.png
464 ms
es.png
467 ms
fr.png
464 ms
gr.png
467 ms
hr.png
469 ms
hu.png
469 ms
im.png
467 ms
is.png
471 ms
it.png
471 ms
li.png
455 ms
candarab.ttf
601 ms
lt.png
371 ms
lu.png
372 ms
lv.png
370 ms
mk.png
372 ms
ga.js
23 ms
mt.png
378 ms
nl.png
378 ms
no.png
384 ms
pl.png
382 ms
pt.png
383 ms
ro.png
440 ms
__utm.gif
13 ms
rs.png
401 ms
ru.png
402 ms
se.png
402 ms
sk.png
401 ms
ua.png
455 ms
uk.png
452 ms
ac.png
406 ms
ae.png
402 ms
af.png
402 ms
ag.png
455 ms
ai.png
454 ms
am.png
467 ms
widget_v2.134.js
19 ms
__$$__stringtable_lang_hr.js
47 ms
as.png
270 ms
br.png
271 ms
by.png
308 ms
bz.png
315 ms
cc.png
314 ms
cd.png
319 ms
cn.png
320 ms
co.png
323 ms
jp.png
373 ms
kr.png
375 ms
sa.png
374 ms
us.png
374 ms
uy.png
374 ms
za.png
379 ms
cx.png
422 ms
ec.png
432 ms
fm.png
418 ms
gd.png
398 ms
gg.png
398 ms
gl.png
400 ms
gs.png
443 ms
gy.png
453 ms
hk.png
396 ms
hm.png
397 ms
hn.png
391 ms
ht.png
399 ms
il.png
441 ms
io.png
395 ms
je.png
395 ms
kg.png
391 ms
ki.png
391 ms
la.png
398 ms
lc.png
385 ms
ly.png
394 ms
ma.png
380 ms
mg.png
383 ms
mn.png
381 ms
ms.png
390 ms
mu.png
392 ms
mx.png
395 ms
nu.png
396 ms
nz.png
394 ms
pe.png
391 ms
pm.png
398 ms
pr.png
385 ms
qa.png
394 ms
re.png
394 ms
sb.png
394 ms
sc.png
393 ms
sh.png
398 ms
so.png
394 ms
sr.png
394 ms
st.png
392 ms
sx.png
394 ms
tf.png
395 ms
tk.png
398 ms
tp.png
764 ms
tm.png
753 ms
to.png
751 ms
tv.png
752 ms
tw.png
753 ms
vc.png
745 ms
ve.png
704 ms
vg.png
694 ms
wf.png
693 ms
ws.png
692 ms
yt.png
692 ms
news_slider.gif
685 ms
news_slider_next.gif
643 ms
news_slider_prev.gif
632 ms
news_slider_tabs.gif
634 ms
more.gif
629 ms
icon_clientarea.gif
630 ms
icon_announcement.gif
622 ms
icon_knowledgebase.gif
582 ms
icon_tutorials.gif
571 ms
icon_downloads.gif
572 ms
icon_ticket.gif
570 ms
icon_community.gif
569 ms
icon_serverstatus.gif
561 ms
icon_networkissues.gif
521 ms
icon_domainchecker.gif
511 ms
icon_cart.gif
512 ms
icon_affiliates.gif
510 ms
contact_form.jpg
510 ms
btn_submit.gif
500 ms
bg_sidemenu.jpg
461 ms
sidemenu_separate.gif
450 ms
btn_small.gif
451 ms
table_tr.gif
449 ms
bg_sidemenu_foot.jpg
448 ms
bg_foot.jpg
439 ms
avatar_simple_visitor.png
211 ms
bg_testimonials.jpg
69 ms
footlink_separate.gif
66 ms
bullet_01.png
69 ms
ajax-loader.gif
485 ms
aL63HcygAAVYuCCsAAA==
4 ms
plac.si accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
plac.si 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
plac.si SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
SL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plac.si can be misinterpreted by Google and other search engines. Our service has detected that Slovenian 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 Plac.si 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.
plac.si
Open Graph description is not detected on the main page of Plac. 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: