Tools & Wizards About Us
dacia.ba screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dacia.ba

Dacia BiH | Naslovna

Page Load Speed

4.2 sec in total

First Response

473 ms

Resources Loaded

3.5 sec

Page Rendered

188 ms

dacia.ba screenshot

About Website

Visit dacia.ba now to see the best up-to-date Dacia content for Bosnia and Herzegovina and also check out these interesting facts you probably never knew about dacia.ba

Otkrijte marku Dacia. Istražite našu ponudu novih i rabljenih vozila, dodatnu opremu i posebne ponude.

Visit dacia.ba

Key Findings

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

Performance Metrics

dacia.ba performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value1.521

0/100

15%

TTI (Time to Interactive)

Value31.7 s

0/100

10%

Network Requests Diagram

dacia.ba

473 ms

dacia.ba

765 ms

main-latin.css

875 ms

polyfills.js

506 ms

menu-provider.js

1131 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Dacia.ba, 5% (2 requests) were made to Ssl.google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dacia.ba.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (57%)

Content Size

5.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dacia.ba main page is 5.8 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. 45% of websites need less resources to load. Javascripts take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 64.7 kB

  • Original 75.0 kB
  • After minification 60.5 kB
  • After compression 10.4 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 14.6 kB, which is 19% 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 64.7 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 21.6 kB

  • Original 1.5 MB
  • After minification 1.5 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. Dacia images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 2.7 MB

  • Original 3.6 MB
  • After minification 3.6 MB
  • After compression 941.2 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 2.7 MB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 481.9 kB

  • Original 552.2 kB
  • After minification 551.4 kB
  • After compression 70.3 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. Dacia.ba needs all CSS files to be minified and compressed as it can save up to 481.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (19%)

Requests Now

32

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dacia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

dacia.ba

dacia.ba

473 ms

dacia.ba

dacia.ba

765 ms

main-latin.css

main-latin.css

875 ms

polyfills.js

polyfills.js

506 ms

menu-provider.js

menu-provider.js

1131 ms

runtime.min.js

runtime.min.js

137 ms

vendor.min.js

vendor.min.js

1260 ms

react.js

react.js

1433 ms

js

js

56 ms

ga.js

ga.js

36 ms

dacia-duster-hjd-ph2-hero-zone-001_ig_w580_h326.jpg

dacia-duster-hjd-ph2-hero-zone-001_ig_w580_h326.jpg

131 ms

dacia-duster-p1310-hero-zone_ig_w580_h326.jpg

dacia-duster-p1310-hero-zone_ig_w580_h326.jpg

383 ms

dacia-spring-bbg24-homepage-banner-001_ig_w580_h326.jpg

dacia-spring-bbg24-homepage-banner-001_ig_w580_h326.jpg

131 ms

dacia-jogger-rji-ph1-beautyshot-001_ig_w580_h326.jpg

dacia-jogger-rji-ph1-beautyshot-001_ig_w580_h326.jpg

383 ms

dacia-sandero-stepway-bji-ph1-beautyshot-001_ig_w580_h326.jpg

dacia-sandero-stepway-bji-ph1-beautyshot-001_ig_w580_h326.jpg

260 ms

Dacia-spring-bbg-ph1-BigRange_ig_w320_h200.jpg

Dacia-spring-bbg-ph1-BigRange_ig_w320_h200.jpg

261 ms

dacia-sandero-stepway-bji-ph1-BigRange_ig_w320_h200.jpg

dacia-sandero-stepway-bji-ph1-BigRange_ig_w320_h200.jpg

389 ms

dacia-logan-lji-ph1-BigRange_ig_w320_h200.jpg

dacia-logan-lji-ph1-BigRange_ig_w320_h200.jpg

389 ms

dacia-duster-hjd-ph2-BigRange_ig_w320_h200.jpg

dacia-duster-hjd-ph2-BigRange_ig_w320_h200.jpg

481 ms

Dacia-Jogger-rji-ph1-BigRange_ig_w320_h200.jpg

Dacia-Jogger-rji-ph1-BigRange_ig_w320_h200.jpg

506 ms

Dacia-Jogger-HEV-DSI-BigRange_ig_w320_h200.jpg

Dacia-Jogger-HEV-DSI-BigRange_ig_w320_h200.jpg

507 ms

Big-Range-Image-2_ig_w320_h200.jpg

Big-Range-Image-2_ig_w320_h200.jpg

524 ms

dacia-spring-bbg24-big-range_ig_w320_h200.jpg

dacia-spring-bbg24-big-range_ig_w320_h200.jpg

522 ms

dacia-duster-p1310-big-range_ig_w320_h200.jpg

dacia-duster-p1310-big-range_ig_w320_h200.jpg

613 ms

template-image-dacia_2560x500_DESKTOP.jpg

template-image-dacia_2560x500_DESKTOP.jpg

1010 ms

dacia-salon-01_ig_w400_h225.JPG

dacia-salon-01_ig_w400_h225.JPG

636 ms

Media-nav-12_ig_w400_h225.jpg

Media-nav-12_ig_w400_h225.jpg

653 ms

dacia-duster-hjd-ph2-001_ig_w400_h225.jpg

dacia-duster-hjd-ph2-001_ig_w400_h225.jpg

654 ms

Read-Regular_V3000.woff

Read-Regular_V3000.woff

755 ms

Read-Bold_V3000.woff

Read-Bold_V3000.woff

722 ms

emoji.woff

emoji.woff

1364 ms

DaciaBlock-Bold.ttf

DaciaBlock-Bold.ttf

883 ms

PictosComplete-Regular.woff

PictosComplete-Regular.woff

763 ms

__utm.gif

__utm.gif

12 ms

dacia-duster-hjd-ph2-hero-zone-001_ig_w900_h506.jpg

dacia-duster-hjd-ph2-hero-zone-001_ig_w900_h506.jpg

829 ms

dacia-duster-p1310-hero-zone_ig_w900_h506.jpg

dacia-duster-p1310-hero-zone_ig_w900_h506.jpg

867 ms

dacia-spring-bbg24-homepage-banner-001_ig_w900_h506.jpg

dacia-spring-bbg24-homepage-banner-001_ig_w900_h506.jpg

864 ms

dacia-jogger-rji-ph1-beautyshot-001_ig_w900_h506.jpg

dacia-jogger-rji-ph1-beautyshot-001_ig_w900_h506.jpg

961 ms

dacia-sandero-stepway-bji-ph1-beautyshot-001_ig_w900_h506.jpg

dacia-sandero-stepway-bji-ph1-beautyshot-001_ig_w900_h506.jpg

989 ms

Accessibility Review

dacia.ba accessibility score

76

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dacia.ba best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

dacia.ba SEO score

92

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

Language and Encoding

  • Language Detected

    BS

  • Language Claimed

    BS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dacia.ba can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Dacia.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

dacia.ba

Open Graph description is not detected on the main page of Dacia. 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: