4.3 sec in total
435 ms
1.8 sec
2.1 sec
Welcome to prelaz-free.bloger.hr homepage info - get ready to check Prelaz Free Bloger best content for Macedonia right away, or after learning these important things about prelaz-free.bloger.hr
Index.hr - Nezavisni hrvatski news i lifestyle portal - Pročitajte najnovije vijesti, sportske novosti, i vijesti iz svijeta zabave
Visit prelaz-free.bloger.hrWe analyzed Prelaz-free.bloger.hr page load time and found that the first response time was 435 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
prelaz-free.bloger.hr performance score
435 ms
187 ms
198 ms
199 ms
200 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Prelaz-free.bloger.hr, 13% (9 requests) were made to Widgeo.net and 7% (5 requests) were made to Scontent-a-fra.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (998 ms) relates to the external source Scontent-b-fra.xx.fbcdn.net.
Page size can be reduced by 347.0 kB (63%)
550.1 kB
203.1 kB
In fact, the total size of Prelaz-free.bloger.hr main page is 550.1 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 465.5 kB which makes up the majority of the site volume.
Potential reduce by 41.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 6.4 kB, which is 12% 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 41.2 kB or 78% of the original size.
Potential reduce by 1.4 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. Prelaz Free Bloger images are well optimized though.
Potential reduce by 292.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 292.5 kB or 63% of the original size.
Potential reduce by 11.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. Prelaz-free.bloger.hr needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 83% of the original size.
Number of requests can be reduced by 38 (76%)
50
12
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prelaz Free Bloger. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
default.aspx
435 ms
sifrscreen.css
187 ms
layout_4.css
198 ms
theme.css
199 ms
override.css
200 ms
overridesimple.css
201 ms
sifr.js
278 ms
simpleajax.js
287 ms
ajaxroutine.js
295 ms
ufo.js
296 ms
swfobject.js
299 ms
AC_OETags.js
301 ms
message.php
202 ms
geocompteur.php
235 ms
theme.css.js
239 ms
xgemius.js
239 ms
emg-with-jquery.js
28 ms
watch
448 ms
247784_580316505407202_7625190799487274519_n.jpg
556 ms
10538454_577637309008455_2910497621113558012_n.jpg
290 ms
10704077_574311712674348_545010806887541844_n.jpg
274 ms
10502281_721709537905825_3251253955235260924_n.jpg
285 ms
10553402_550556321716554_8258054884941178344_n.jpg
566 ms
10509527_699654086778037_3921249615041189633_n.jpg
431 ms
10403402_694880447255401_8004339059932158605_n.jpg
423 ms
1969399_309295405908597_6246453945403338586_n.jpg
471 ms
1506579_728326963888800_5140141120848277113_n.jpg
285 ms
10561557_724405757605762_1001880974796263200_n.jpg
452 ms
logopm.png
124 ms
10487389_548463761925810_5025425798598184924_n.jpg
996 ms
10500394_516411091792596_773244851464713824_n.jpg
998 ms
10527353_711915642188107_6519267268216960195_n.jpg
854 ms
10501846_516346511799054_5767193429021511181_n.jpg
565 ms
upbody.jpg
149 ms
close.gif
148 ms
komentar.gif
148 ms
btn.gif
145 ms
10629812_752630271462958_3594210368802973790_n.jpg
644 ms
10402991_673601039402856_8773490121537105170_n.jpg
879 ms
10574529_548464278592425_2138908995999374204_n.jpg
946 ms
10468071_655246517904975_3203276650120011885_n.jpg
873 ms
heder1x2.png
118 ms
nidjoch2.jpg
434 ms
override.css
272 ms
standard.js
147 ms
tcm_b.js
333 ms
tcm_opener.js
388 ms
copt.js
246 ms
analytics.js
111 ms
hitparade.php
240 ms
geocompteur_html.php
284 ms
hitparade.php
313 ms
ga.js
62 ms
collect
101 ms
collect
105 ms
48df891e.png
301 ms
door.js
420 ms
__utm.gif
85 ms
ajs.php
211 ms
css
26 ms
geo_css.php
196 ms
jquery.min.js
24 ms
geowidget_js.js
10 ms
lg.php
103 ms
rexdot.gif
117 ms
hit.xiti
205 ms
flag_united%20states.png
16 ms
geoall4.png
168 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
9 ms
hit.gif
351 ms
hit.xiti
213 ms
script.v35.js
252 ms
prelaz-free.bloger.hr SEO score
HR
HR
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prelaz-free.bloger.hr can be misinterpreted by Google and other search engines. Our service has detected that Croatian is used on the page, and it matches the claimed language. Our system also found out that Prelaz-free.bloger.hr main page’s claimed encoding is iso-8859-2. 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.
prelaz-free.bloger.hr
Open Graph description is not detected on the main page of Prelaz Free Bloger. 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: