Tools & Wizards About Us
autodata.nl screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

autodata.nl

Autodata | Taxeren, Voorraadbeheer en Websites voor de autobranche

Page Load Speed

2.7 sec in total

First Response

345 ms

Resources Loaded

2.2 sec

Page Rendered

201 ms

autodata.nl screenshot

About Website

Visit autodata.nl now to see the best up-to-date Autodata content for Netherlands and also check out these interesting facts you probably never knew about autodata.nl

Autodata biedt moderne applicaties en slimme oplossingen voor auto inkoop en verkoop.

Visit autodata.nl

Key Findings

We analyzed Autodata.nl page load time and found that the first response time was 345 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

autodata.nl performance score

0

Network Requests Diagram

autodata.nl

345 ms

92 ms

home

118 ms

_cms1446581136_xcms.css

609 ms

_cms1_autodatasite.css

621 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 68% of them (34 requests) were addressed to the original Autodata.nl, 10% (5 requests) were made to Loquendo.nl and 4% (2 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (804 ms) belongs to the original domain Autodata.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.3 kB (51%)

Content Size

669.9 kB

After Optimization

325.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Autodata.nl main page is 669.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 309.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 27.5 kB

  • Original 35.5 kB
  • After minification 33.0 kB
  • After compression 8.0 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 27.5 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 30.7 kB

  • Original 221.8 kB
  • After minification 191.1 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. Obviously, Autodata needs image optimization as it can save up to 30.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 201.4 kB

  • Original 309.8 kB
  • After minification 275.3 kB
  • After compression 108.4 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 201.4 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 84.8 kB

  • Original 102.9 kB
  • After minification 102.8 kB
  • After compression 18.1 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. Autodata.nl needs all CSS files to be minified and compressed as it can save up to 84.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (55%)

Requests Now

42

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

autodata.nl

autodata.nl

345 ms

92 ms

home

home

118 ms

_cms1446581136_xcms.css

_cms1446581136_xcms.css

609 ms

_cms1_autodatasite.css

_cms1_autodatasite.css

621 ms

responsive.css

responsive.css

614 ms

css

css

24 ms

_cms1403870051_xcms.combined.js

_cms1403870051_xcms.combined.js

615 ms

jquery.js

jquery.js

718 ms

autodata-nieuw.js

autodata-nieuw.js

618 ms

jquery.min.js

jquery.min.js

45 ms

jquery.prettyphoto.js

jquery.prettyphoto.js

703 ms

jquery.cycle.all.latest.js

jquery.cycle.all.latest.js

804 ms

autodata.js

autodata.js

708 ms

loquendo.css

loquendo.css

744 ms

conversion.js

conversion.js

17 ms

loquendo.js

loquendo.js

269 ms

j.php

j.php

61 ms

autodata_woordmerk.png

autodata_woordmerk.png

132 ms

english.png

english.png

133 ms

nederlands.png

nederlands.png

136 ms

bg_nav_grijs.png

bg_nav_grijs.png

132 ms

bg_nav_grijs2.png

bg_nav_grijs2.png

140 ms

cardesk_banner_schadeverleden_29022016.jpg

cardesk_banner_schadeverleden_29022016.jpg

503 ms

actiebt.png

actiebt.png

191 ms

autodata_beeldmerk_icon_inkoop_fc.png

autodata_beeldmerk_icon_inkoop_fc.png

191 ms

autodata_button_off.png

autodata_button_off.png

189 ms

autodata_beeldmerk_icon_voorraad_fc.png

autodata_beeldmerk_icon_voorraad_fc.png

191 ms

autodata_beeldmerk_icon_verkoop_fc.png

autodata_beeldmerk_icon_verkoop_fc.png

189 ms

autodata_beeldmerk_icon_algemeen_fc.png

autodata_beeldmerk_icon_algemeen_fc.png

286 ms

autodata_button_zwart_off.png

autodata_button_zwart_off.png

279 ms

arrow_up.png

arrow_up.png

282 ms

arrow_down.png

arrow_down.png

283 ms

autodata-bg-footer.png

autodata-bg-footer.png

369 ms

clicksautomotive-facebook-icon.png

clicksautomotive-facebook-icon.png

375 ms

clicksautomotive-twitter-icon.png

clicksautomotive-twitter-icon.png

378 ms

clicksautomotive-youtube-icon.png

clicksautomotive-youtube-icon.png

375 ms

91 ms

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

42 ms

Luunk03-uSz9LnB7oNEUuvesZW2xOQ-xsNqO47m55DA.ttf

Luunk03-uSz9LnB7oNEUuvesZW2xOQ-xsNqO47m55DA.ttf

44 ms

ga.js

ga.js

41 ms

chat.cgi

chat.cgi

94 ms

v.gif

v.gif

14 ms

vcount.cgi

vcount.cgi

342 ms

__utm.gif

__utm.gif

16 ms

36 ms

chat.cgi

chat.cgi

403 ms

mobiel.css

mobiel.css

94 ms

chat.cgi

chat.cgi

91 ms

chat.cgi

chat.cgi

103 ms

SEO Factors

autodata.nl SEO score

0

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autodata.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Autodata.nl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

autodata.nl

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