Tools & Wizards About Us

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

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

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

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: