Tools & Wizards About Us
vitalis.ba screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vitalis.ba

Vitalis - Dom za starije | Starački dom, Sanitetski prevoz

Page Load Speed

5.7 sec in total

First Response

548 ms

Resources Loaded

4.7 sec

Page Rendered

476 ms

vitalis.ba screenshot

About Website

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.ba

Key Findings

We analyzed Vitalis.ba page load time and found that the first response time was 548 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

vitalis.ba performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value22.5 s

0/100

10%

TBT (Total Blocking Time)

Value6,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value35.9 s

0/100

10%

Network Requests Diagram

vitalis.ba

548 ms

9kho4.css

194 ms

post-11.css

286 ms

9kho4.css

384 ms

post-14.css

292 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 56% of them (45 requests) were addressed to the original Vitalis.ba, 18% (14 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Vitalis.ba.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.1 kB (3%)

Content Size

2.9 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vitalis.ba main page is 2.9 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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 92.9 kB

  • Original 109.6 kB
  • After minification 105.1 kB
  • After compression 16.7 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 92.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

  • Original 2.6 MB
  • After minification 2.6 MB

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.

JavaScript Optimization

-2%

Potential reduce by 2.5 kB

  • Original 164.1 kB
  • After minification 164.1 kB
  • After compression 161.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 59.2 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. Vitalis.ba has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (66%)

Requests Now

74

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 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 37 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vitalis.ba

vitalis.ba

548 ms

9kho4.css

9kho4.css

194 ms

post-11.css

post-11.css

286 ms

9kho4.css

9kho4.css

384 ms

post-14.css

post-14.css

292 ms

post-57.css

post-57.css

290 ms

post-142.css

post-142.css

294 ms

post-1026.css

post-1026.css

287 ms

post-824.css

post-824.css

378 ms

css

css

110 ms

9khop.css

9khop.css

393 ms

9kho4.js

9kho4.js

481 ms

js.cookie.min.js

js.cookie.min.js

32 ms

js.cookie.min.mjs

js.cookie.min.mjs

35 ms

js

js

74 ms

js

js

120 ms

js

js

136 ms

9kho3.css

9kho3.css

397 ms

9kho3.css

9kho3.css

395 ms

wp-embed.min.js

wp-embed.min.js

468 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

472 ms

imagesloaded.min.js

imagesloaded.min.js

473 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

632 ms

webpack.runtime.min.js

webpack.runtime.min.js

633 ms

frontend-modules.min.js

frontend-modules.min.js

640 ms

frontend.min.js

frontend.min.js

641 ms

waypoints.min.js

waypoints.min.js

641 ms

core.min.js

core.min.js

642 ms

frontend.min.js

frontend.min.js

643 ms

elements-handlers.min.js

elements-handlers.min.js

640 ms

jquery.sticky.min.js

jquery.sticky.min.js

730 ms

fbevents.js

fbevents.js

164 ms

gtm.js

gtm.js

151 ms

ibAWcfltPZQ

ibAWcfltPZQ

401 ms

page.php

page.php

263 ms

dom-za-starije-vitalis-logo.png

dom-za-starije-vitalis-logo.png

208 ms

intro-bkg-2.jpg

intro-bkg-2.jpg

902 ms

sanitetski-prevoz-bkg2-min.png

sanitetski-prevoz-bkg2-min.png

1089 ms

upit-bkg.jpg

upit-bkg.jpg

402 ms

dom-gal-4.jpg

dom-gal-4.jpg

845 ms

dom-gal-5.jpg

dom-gal-5.jpg

846 ms

dom-gal-8.jpg

dom-gal-8.jpg

847 ms

dom-gal-7.jpg

dom-gal-7.jpg

847 ms

dom-gal-6.jpg

dom-gal-6.jpg

952 ms

osoblje-dom-vitalis.png

osoblje-dom-vitalis.png

1088 ms

galerija-img.jpg

galerija-img.jpg

901 ms

faq-img.jpg

faq-img.jpg

902 ms

img-1.jpg

img-1.jpg

968 ms

sanitetski-prevoz-dom-vitalis.png

sanitetski-prevoz-dom-vitalis.png

969 ms

img-3.jpg

img-3.jpg

954 ms

popup.jpg

popup.jpg

1088 ms

fa-solid-900.woff

fa-solid-900.woff

981 ms

fa-regular-400.woff

fa-regular-400.woff

1121 ms

eicons.woff

eicons.woff

1122 ms

fa-brands-400.woff

fa-brands-400.woff

1122 ms

font

font

64 ms

xOMdzFCV7Du.css

xOMdzFCV7Du.css

31 ms

XVfyC-hY3iC.js

XVfyC-hY3iC.js

37 ms

O1Rb7CQsNyZ.js

O1Rb7CQsNyZ.js

33 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

68 ms

hQIh1OAznJN.js

hQIh1OAznJN.js

68 ms

VIsRuUKJnSl.js

VIsRuUKJnSl.js

73 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

67 ms

WWCnZq92JDW.js

WWCnZq92JDW.js

72 ms

p55HfXW__mM.js

p55HfXW__mM.js

80 ms

knF92sc18tr.js

knF92sc18tr.js

79 ms

0oAcl5WIW_m.js

0oAcl5WIW_m.js

82 ms

NAwf-wBX08e.js

NAwf-wBX08e.js

81 ms

434030138_928274689303696_6021913620369533483_n.jpg

434030138_928274689303696_6021913620369533483_n.jpg

486 ms

g6z8PvzJiRa.js

g6z8PvzJiRa.js

36 ms

434419491_930441885753643_6211593299095106473_n.jpg

434419491_930441885753643_6211593299095106473_n.jpg

105 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

26 ms

www-player.css

www-player.css

33 ms

www-embed-player.js

www-embed-player.js

73 ms

base.js

base.js

104 ms

ad_status.js

ad_status.js

276 ms

lA2ntTx-2QuHkXZslM9sAF03Z9lhVUC55dA1orjIb5A.js

lA2ntTx-2QuHkXZslM9sAF03Z9lhVUC55dA1orjIb5A.js

198 ms

embed.js

embed.js

66 ms

id

id

48 ms

Create

Create

120 ms

Accessibility Review

vitalis.ba accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

vitalis.ba best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vitalis.ba SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    HR

  • Language Claimed

    EN

  • Encoding

    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 it does not match the claimed English language. 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.

Social Sharing Optimization

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: