8.8 sec in total
477 ms
8.1 sec
175 ms
Visit dacia.hu now to see the best up-to-date Dacia content for Hungary and also check out these interesting facts you probably never knew about dacia.hu
Új autók a Dacia kínálatában. Személyautó és furgon autók széles választéka igazán vonzó árakon. Nézzen be hozzánk!
Visit dacia.huWe analyzed Dacia.hu page load time and found that the first response time was 477 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dacia.hu performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value6.4 s
10/100
25%
Value4.7 s
70/100
10%
Value2,070 ms
7/100
30%
Value0.56
13/100
15%
Value10.1 s
26/100
10%
477 ms
185 ms
185 ms
414 ms
291 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 65% of them (39 requests) were addressed to the original Dacia.hu, 8% (5 requests) were made to Googletagmanager.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Dacia.hu.
Page size can be reduced by 353.6 kB (35%)
1.0 MB
670.8 kB
In fact, the total size of Dacia.hu main page is 1.0 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. Images take 630.7 kB which makes up the majority of the site volume.
Potential reduce by 293.3 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 293.3 kB or 88% of the original size.
Potential reduce by 28.3 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. Dacia images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 52% of the original size.
Number of requests can be reduced by 29 (56%)
52
23
The browser has sent 52 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 23 to 1 for JavaScripts and as a result speed up the page load time.
dacia.hu
477 ms
utag-dhu.js
185 ms
ekino-lite.css
185 ms
projet.css
414 ms
wf_dacia.css
291 ms
mootools.js
508 ms
jquery.min.js
34 ms
ekino.js
536 ms
projet.js
1516 ms
full_lite.js
770 ms
skinFormElements.js
387 ms
sitestat.js
480 ms
sitestat_call.js
528 ms
55.js
574 ms
cookieAnalytics.js
506 ms
webFormsApp.js
6959 ms
jquery.passwordStrength.js
524 ms
gtm.js
45 ms
chevrons.png
108 ms
header_nav_bg.png
109 ms
logo.png
110 ms
mainBg.png
108 ms
Facebook.png
109 ms
YouTube.png
217 ms
Twitter.png
216 ms
Duster_Urban_Banner_2015_NOV_980x388.jpg
635 ms
protection_bgHome.png
218 ms
sandero-banner_2015_aug_omnio_980x388.jpg
632 ms
Duster-Banner_2015_JUL_Omnio_980x388.jpg
620 ms
dokker-van-hu-09a.jpg
708 ms
banner-hp.jpg
770 ms
neotechdacia-regular-webfont.woff
795 ms
neotechdacia-light-webfont.woff
822 ms
neotechdacia-medium-webfont.woff
813 ms
ImageFromBookmark
213 ms
ImageFromBookmark
38 ms
aktualis.jpg
798 ms
fb-icon.jpg
862 ms
3EV.jpg
882 ms
push4-71x54-home.jpg
883 ms
logo-daciagroup.png
901 ms
carPickerBg.png
903 ms
gtm.js
45 ms
gtm.js
37 ms
gtm.js
35 ms
conversion_async.js
53 ms
deployment.js
56 ms
HU.js
282 ms
35 ms
41 ms
ga.js
455 ms
gtm.js
14 ms
__utm.gif
29 ms
collect
61 ms
__utm.gif
20 ms
MultiNoun.jsonp
127 ms
btTooltip.png
149 ms
cookie-consent-symbol.woff
28 ms
collect
10 ms
MultiNoun.jsonp
428 ms
dacia.hu 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
dacia.hu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
dacia.hu 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 doesn't use legible font sizes
Tap targets are not sized appropriately
HU
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dacia.hu can be misinterpreted by Google and other search engines. Our service has detected that Hungarian is used on the page, and it does not match the claimed French language. Our system also found out that Dacia.hu 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.
dacia.hu
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: