6.8 sec in total
1.7 sec
4.8 sec
340 ms
Visit vitus.hr now to see the best up-to-date Vitus content for Croatia and also check out these interesting facts you probably never knew about vitus.hr
Vitus d.o.o. je licencirana agencija za posredovanje u prometu nekretninama i projektiranje, sa bogatim desetogodišnjim iskustvom na polju nekretnina.
Visit vitus.hrWe analyzed Vitus.hr page load time and found that the first response time was 1.7 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster. This domain responded with an error, which can significantly jeopardize Vitus.hr rating and web reputation
vitus.hr performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value7.2 s
5/100
25%
Value9.4 s
12/100
10%
Value1,140 ms
22/100
30%
Value0.024
100/100
15%
Value7.1 s
52/100
10%
1674 ms
221 ms
224 ms
571 ms
782 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 90% of them (102 requests) were addressed to the original Vitus.hr, 4% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Vitus.hr.
Page size can be reduced by 1.2 MB (37%)
3.2 MB
2.0 MB
In fact, the total size of Vitus.hr main page is 3.2 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 109.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 109.2 kB or 87% of the original size.
Potential reduce by 16.7 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. Vitus images are well optimized though.
Potential reduce by 623.6 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 623.6 kB or 72% of the original size.
Potential reduce by 425.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. Vitus.hr needs all CSS files to be minified and compressed as it can save up to 425.6 kB or 85% of the original size.
Number of requests can be reduced by 63 (62%)
101
38
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vitus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
vitus.hr
1674 ms
jcemediabox.css
221 ms
style.css
224 ms
bootstrap.css
571 ms
master-a8f42f6ec2b9cde24b89482b22f8d10a.css
782 ms
master-gecko.css
234 ms
demo-a8f42f6ec2b9cde24b89482b22f8d10a.css
545 ms
mediaqueries.css
445 ms
grid-flexbox-responsive.css
350 ms
menu-dropdown-direction.css
460 ms
css
28 ms
vitus-custom.css
463 ms
maximenuck.php
688 ms
beez3-position1.css
575 ms
main.css
583 ms
jquery.ui.lightness.css
756 ms
jquery.safari-checkbox.css
672 ms
jquery.checkbox.css
689 ms
slider.css
694 ms
style2.0.css
791 ms
maximenuck.php
824 ms
template.css
804 ms
mootools-core.js
1055 ms
core.js
763 ms
jquery.min.js
894 ms
jquery.ui.js
1130 ms
jquery.migrate.js
818 ms
noconflict.js
834 ms
handlebars.js
978 ms
spin.min.js
935 ms
main.js
945 ms
jquery-noconflict.js
1006 ms
jquery-migrate.min.js
1051 ms
caption.js
1083 ms
jcemediabox.js
1196 ms
bootstrap.min.js
1116 ms
browser-engines.js
1169 ms
js
27 ms
rpl_style.css
1064 ms
rpl_style_orange.css
1281 ms
rokmediaqueries.js
1110 ms
jquery.ui.core.min.js
1010 ms
maximenuck.js
1048 ms
rplautocomplete.js
959 ms
jquery.checkbox.js
988 ms
jssor.slider.mini.js
920 ms
jquery.mousewheel.min.js
938 ms
jquery.simplemodal.js
936 ms
default.js
937 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
11 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
14 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
12 ms
EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff
11 ms
analytics.js
37 ms
header-bg.jpg
323 ms
logo.png
322 ms
hr.gif
321 ms
sl.gif
319 ms
en.gif
320 ms
de.gif
318 ms
it.gif
330 ms
hu.gif
330 ms
he.gif
329 ms
ru.gif
329 ms
none
644 ms
th480x360_img507_7a7sSV.jpg
436 ms
th100x75_img507_e6Nov6.jpg
438 ms
th100x75_img507_VHsYn3.jpg
432 ms
th100x75_img507_aV6BsY.jpg
433 ms
th100x75_img507_YX21sE.jpg
430 ms
th100x75_img507_jM5kPQ.jpg
539 ms
th100x75_img507_P96nk2.jpg
543 ms
th100x75_img507_bp4pkX.jpg
544 ms
th100x75_img507_61Sbd5.jpg
551 ms
more.png
553 ms
th575x350_img519_xg5bTE.jpg
646 ms
th575x350_img522_d3wGGQ.jpg
765 ms
th575x350_img1128_eYH8wM.jpg
655 ms
th575x350_img1129_FUlnOh.jpg
781 ms
th575x350_img1147_qxbWqZ.jpg
667 ms
th575x350_img1157_qWDJXR.jpg
864 ms
th575x350_img1359_sxZIvu.jpg
862 ms
th575x350_img1386_kWUSpQ.jpg
767 ms
th575x350_img1401_tBfFLM.jpg
900 ms
th575x350_img1417_T13QHL.jpg
875 ms
th575x350_img1421_RRDSfZ.jpg
880 ms
EUR.png
896 ms
index.php
1010 ms
OverlayBgr.png
959 ms
arrows.png
510 ms
collect
16 ms
loading.gif
924 ms
collect
246 ms
nexa-light-webfont.woff
685 ms
nexa-bold-webfont.woff
712 ms
fontawesome-webfont.woff
822 ms
popup.html
776 ms
tooltip.html
788 ms
ga-audiences
40 ms
default.css
138 ms
common.css
110 ms
jquery-1.4.min.js
233 ms
jquery.easing-1.3.js
177 ms
jquery.iosslider.js
301 ms
Baska_Krk.jpg
350 ms
selector-shadow.png
114 ms
Trg-Glagoljasa_Krk.jpg
226 ms
Glavotok_Croatia.jpg
547 ms
Krk_Croatia.jpg
449 ms
Drazica_Krk.jpg
466 ms
selector-prev.png
225 ms
selector-next.png
336 ms
vitus.hr 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
Links do not have a discernible name
vitus.hr 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
Page has valid source maps
vitus.hr SEO score
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
HR
HR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitus.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 Vitus.hr 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.
vitus.hr
Open Graph description is not detected on the main page of Vitus. 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: