Tools & Wizards About Us
autodna.pl screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

autodna.pl

Sprawdź VIN | Miliardy rekordów o pojazdach używanych | autoDNA

Page Load Speed

3.7 sec in total

First Response

366 ms

Resources Loaded

3.1 sec

Page Rendered

255 ms

autodna.pl screenshot

About Website

Click here to check amazing AutoDNA content for Poland. Otherwise, check out these important facts you probably never knew about autodna.pl

Sprawdź VIN za darmo. Poznaj historię pojazdu, przebiegi, przeglądy samochodu, uszkodzenia, kradzieże, archiwalne zdjęcia.

Visit autodna.pl

Key Findings

We analyzed Autodna.pl page load time and found that the first response time was 366 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

autodna.pl performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value1.209

1/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

autodna.pl

366 ms

www.autodna.pl

454 ms

reset.css

118 ms

adu-main.css

457 ms

jquery.lightbox-0.5.css

234 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 75% of them (81 requests) were addressed to the original Autodna.pl, 8% (9 requests) were made to Facebook.com and 6% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Autodna.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.6 kB (20%)

Content Size

209.7 kB

After Optimization

167.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Autodna.pl main page is 209.7 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. 45% of websites need less resources to load. Images take 132.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 37.9 kB

  • Original 48.7 kB
  • After minification 34.3 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 29% 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 37.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 132.2 kB
  • After minification 132.2 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. AutoDNA images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 4.7 kB

  • Original 28.9 kB
  • After minification 28.9 kB
  • After compression 24.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 4.7 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (33%)

Requests Now

95

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

autodna.pl

autodna.pl

366 ms

www.autodna.pl

www.autodna.pl

454 ms

reset.css

reset.css

118 ms

adu-main.css

adu-main.css

457 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

234 ms

adu-force-pl.css

adu-force-pl.css

232 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

481 ms

jquery.cycle.all.2.73.min.js

jquery.cycle.all.2.73.min.js

348 ms

jquery.lightbox-0.5-pl.js

jquery.lightbox-0.5-pl.js

239 ms

autodna_ext.js

autodna_ext.js

349 ms

autodna.js

autodna.js

479 ms

menu.js

menu.js

356 ms

kt_valid.js

kt_valid.js

478 ms

kt_slidebar.css

kt_slidebar.css

476 ms

kt_slidebar.js

kt_slidebar.js

476 ms

cookie.js

cookie.js

563 ms

fonts_multi.css

fonts_multi.css

350 ms

floatbar.css

floatbar.css

126 ms

analytics.js

analytics.js

63 ms

fbevents.js

fbevents.js

149 ms

header_bg.png

header_bg.png

136 ms

home-pl.png

home-pl.png

137 ms

sprawdzenie-vin-autodna.png

sprawdzenie-vin-autodna.png

137 ms

pl.png

pl.png

136 ms

icons_main.png

icons_main.png

135 ms

ico[mobile].png

ico[mobile].png

135 ms

menu_bg.png

menu_bg.png

264 ms

menu_home2.png

menu_home2.png

264 ms

header_ext_opt.jpg

header_ext_opt.jpg

369 ms

slide_img10_v6_blank.png

slide_img10_v6_blank.png

732 ms

slide_img8_blank.png

slide_img8_blank.png

833 ms

slide_img9_blank.png

slide_img9_blank.png

375 ms

slide_img7_v2_blank.png

slide_img7_v2_blank.png

496 ms

slide_img11_v3_blank.png

slide_img11_v3_blank.png

498 ms

slide_img12_blank.png

slide_img12_blank.png

486 ms

input_vin.png

input_vin.png

491 ms

button_blue.png

button_blue.png

601 ms

index_banner-blank.jpg

index_banner-blank.jpg

614 ms

tab-right-iv.png

tab-right-iv.png

612 ms

tab-m-right-iv.png

tab-m-right-iv.png

616 ms

tab-unactive-right-iv.png

tab-unactive-right-iv.png

715 ms

tab-unactive-m-right-iv.png

tab-unactive-m-right-iv.png

728 ms

box_top.png

box_top.png

730 ms

box_mid.png

box_mid.png

733 ms

h1.gif

h1.gif

830 ms

li_check.png

li_check.png

843 ms

slide_img2.jpg

slide_img2.jpg

858 ms

slide_img5.jpg

slide_img5.jpg

966 ms

box_bott.png

box_bott.png

846 ms

slidebar_left.png

slidebar_left.png

943 ms

sb_vwe.png

sb_vwe.png

946 ms

sb_forumsamochodowe.png

sb_forumsamochodowe.png

959 ms

sb_autodoradca.png

sb_autodoradca.png

962 ms

sb_motostat.png

sb_motostat.png

974 ms

sb_bezwypadkowe.png

sb_bezwypadkowe.png

1057 ms

platform.js

platform.js

107 ms

sb_pim.png

sb_pim.png

1018 ms

like.php

like.php

147 ms

collect

collect

82 ms

collect

collect

96 ms

Lato-Regular-LE5.2.ttf

Lato-Regular-LE5.2.ttf

1068 ms

Lato-Light-LE5.2.ttf

Lato-Light-LE5.2.ttf

992 ms

Lato-Bold-LE5.2.ttf

Lato-Bold-LE5.2.ttf

992 ms

Lato-Black-LE5.2.ttf

Lato-Black-LE5.2.ttf

988 ms

Lato-BoldItalic-LE5.2.ttf

Lato-BoldItalic-LE5.2.ttf

1209 ms

Lato-BlackItalic-LE5.2.ttf

Lato-BlackItalic-LE5.2.ttf

1063 ms

90 ms

113 ms

113 ms

113 ms

113 ms

113 ms

113 ms

124 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

62 ms

fastbutton

fastbutton

148 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

502 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

566 ms

ga-audiences

ga-audiences

80 ms

postmessageRelay

postmessageRelay

63 ms

Lato-Italic-LE5.2.ttf

Lato-Italic-LE5.2.ttf

1001 ms

Lato-LightItalic-LE5.2.ttf

Lato-LightItalic-LE5.2.ttf

993 ms

api.js

api.js

52 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

81 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

68 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

76 ms

pl.json

pl.json

872 ms

popup.html

popup.html

962 ms

mfgchk.html

mfgchk.html

871 ms

sb_mobilekspert.png

sb_mobilekspert.png

868 ms

sb_vosa.png

sb_vosa.png

878 ms

sb_carfax.png

sb_carfax.png

880 ms

sb_autocheck.png

sb_autocheck.png

853 ms

sb_autocentrum.png

sb_autocentrum.png

841 ms

sb_motogratka.png

sb_motogratka.png

856 ms

slidebar_right.png

slidebar_right.png

864 ms

footer_core2.jpg

footer_core2.jpg

776 ms

ico_fb20.png

ico_fb20.png

765 ms

ico_google20.png

ico_google20.png

835 ms

footer_logo.png

footer_logo.png

838 ms

slideshow_pagination2.png

slideshow_pagination2.png

851 ms

header_repeat_bg.jpg

header_repeat_bg.jpg

765 ms

cookies-close.png

cookies-close.png

775 ms

warto_kupic-pl.jpg

warto_kupic-pl.jpg

274 ms

1px_white.png

1px_white.png

338 ms

Accessibility Review

autodna.pl accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA progressbar elements do not have accessible names.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

autodna.pl best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

autodna.pl SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

autodna.pl

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