10 sec in total
3.3 sec
6.4 sec
268 ms
Visit vitalis.ba now to see the best up-to-date Vitalis content for Bosnia and Herzegovina and also check out these interesting facts you probably never knew about vitalis.ba
Dom za starije Vitalis nudi usluge smještaj starijih osoba, kućna njega i sanitetski prevoz. Starački dom koji sa iskustvom za potpunu skrb.
Visit vitalis.baWe analyzed Vitalis.ba page load time and found that the first response time was 3.3 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
vitalis.ba performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value13.0 s
0/100
25%
Value8.6 s
17/100
10%
Value750 ms
39/100
30%
Value0.004
100/100
15%
Value13.5 s
11/100
10%
3341 ms
94 ms
196 ms
219 ms
24 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 66% of them (56 requests) were addressed to the original Vitalis.ba, 7% (6 requests) were made to I0.wp.com and 5% (4 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Vitalis.ba.
Page size can be reduced by 1.9 MB (62%)
3.1 MB
1.2 MB
In fact, the total size of Vitalis.ba main page is 3.1 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. CSS take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 44.1 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 44.1 kB or 78% of the original size.
Potential reduce by 6.6 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. Vitalis images are well optimized though.
Potential reduce by 489.7 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 489.7 kB or 65% of the original size.
Potential reduce by 1.4 MB
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. Vitalis.ba needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 90% of the original size.
Number of requests can be reduced by 52 (67%)
78
26
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vitalis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
vitalis.ba
3341 ms
ie10-viewport-bug-workaround.js
94 ms
language-selector.css
196 ms
layerslider.css
219 ms
css
24 ms
styles.css
224 ms
form.min.css
290 ms
settings.css
225 ms
navigation.css
220 ms
cms-navigation-base.css
300 ms
cms-navigation.css
315 ms
bootstrap.min.css
498 ms
font-awesome.min.css
250 ms
animate.min.css
299 ms
flexslider.css
310 ms
jquery.fancybox.css
322 ms
jquery.fancybox-thumbs.css
382 ms
alterna-styles.css
487 ms
style.css
405 ms
css
28 ms
js_composer.css
693 ms
style.min.css
437 ms
animate.min.css
427 ms
interactive-styles.min.css
478 ms
Defaults.css
515 ms
jetpack.css
541 ms
jquery.js
766 ms
jquery-migrate.min.js
580 ms
greensock.js
670 ms
layerslider.kreaturamedia.jquery.js
764 ms
layerslider.transitions.js
634 ms
jquery.themepunch.tools.min.js
845 ms
jquery.themepunch.revolution.min.js
811 ms
picturefill.min.js
861 ms
css
26 ms
photon.js
861 ms
jquery.form.min.js
861 ms
scripts.js
861 ms
devicepx-jetpack.js
5 ms
gprofiles.js
62 ms
wpgroho.js
862 ms
bootstrap.min.js
332 ms
isotope.pkgd.min.js
893 ms
jquery.mousewheel-3.0.6.pack.js
894 ms
e-201611.js
4 ms
jquery.fancybox.pack.js
893 ms
jquery.fancybox-thumbs.js
813 ms
jquery.flexslider-min.js
783 ms
csstransforms3d.js
779 ms
jquery.theme.js
779 ms
sitepress.js
775 ms
js_composer_front.js
855 ms
wp-emoji-release.min.js
703 ms
analytics.js
25 ms
HOME-1.jpg
1230 ms
Text-za-sliku-1.png
734 ms
Text-za-sliku-4.png
1101 ms
de.png
184 ms
bs.png
183 ms
Vitalis-logo2.png
286 ms
zutapodlogal.jpg
286 ms
Text-za-sliku-7.png
741 ms
HOME-2.jpg
1274 ms
Text-za-sliku-2.png
823 ms
HOME-3.jpg
2167 ms
HOME-4.jpg
820 ms
SMJESTAJ-mala.jpg
774 ms
KUCNA-NJEGA-mala.jpg
1707 ms
sanitet.png
2095 ms
Vitalis-slogan.png
1208 ms
collect
17 ms
testimonials_arraw.png
189 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
20 ms
fontawesome-webfont.woff
18 ms
Defaults.woff
342 ms
collect
173 ms
revolution.extension.slideanims.min.js
105 ms
revolution.extension.layeranimation.min.js
112 ms
revolution.extension.navigation.min.js
108 ms
hovercard.css
46 ms
services.css
55 ms
icon_chevron_top.png
167 ms
g.gif
4 ms
loader.gif
95 ms
revicons.woff
104 ms
vitalis.ba 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.
vitalis.ba 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
vitalis.ba SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitalis.ba can be misinterpreted by Google and other search engines. Our service has detected that Croatian 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 Vitalis.ba 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.
vitalis.ba
Open Graph data is detected on the main page of Vitalis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: