Tools & Wizards About Us
dlznik.sk screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dlznik.sk

Dlžník.sk | Zoznam dlžníkov, Zoznam neplatičov, Pohľadávky

Page Load Speed

6.3 sec in total

First Response

323 ms

Resources Loaded

5.8 sec

Page Rendered

180 ms

dlznik.sk screenshot

About Website

Click here to check amazing Dlznik content. Otherwise, check out these important facts you probably never knew about dlznik.sk

Najúplnejší zoznam dlžníkov a neplatičov v SR. Pohľadávky, vyhlásené konkurzy a reštrukturalizácie. Sociálna sieť slovenských firiem – profily subjektov a vzťahy medzi firmami.

Visit dlznik.sk

Key Findings

We analyzed Dlznik.sk page load time and found that the first response time was 323 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

dlznik.sk performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

dlznik.zoznam.sk

323 ms

dlznik.zoznam.sk

873 ms

loader.js

248 ms

didomi.min.js

552 ms

base.css

112 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dlznik.sk, 9% (10 requests) were made to Pagead2.googlesyndication.com and 8% (9 requests) were made to Static.criteo.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Gask.hit.gemius.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.3 kB (19%)

Content Size

943.6 kB

After Optimization

764.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dlznik.sk main page is 943.6 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. 65% of websites need less resources to load. Javascripts take 699.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 55.9 kB

  • Original 69.9 kB
  • After minification 64.8 kB
  • After compression 14.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 55.9 kB or 80% of the original size.

Image Optimization

-20%

Potential reduce by 32.1 kB

  • Original 163.6 kB
  • After minification 131.4 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, Dlznik needs image optimization as it can save up to 32.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 87.5 kB

  • Original 699.7 kB
  • After minification 699.7 kB
  • After compression 612.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 87.5 kB or 13% of the original size.

CSS Optimization

-36%

Potential reduce by 3.8 kB

  • Original 10.4 kB
  • After minification 10.4 kB
  • After compression 6.7 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. Dlznik.sk needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (61%)

Requests Now

108

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dlznik.zoznam.sk

dlznik.zoznam.sk

323 ms

dlznik.zoznam.sk

dlznik.zoznam.sk

873 ms

loader.js

loader.js

248 ms

didomi.min.js

didomi.min.js

552 ms

base.css

base.css

112 ms

jquery.js

jquery.js

451 ms

jquery.jqplot.min.js

jquery.jqplot.min.js

892 ms

jqplot.barRenderer.min.js

jqplot.barRenderer.min.js

571 ms

jqplot.categoryAxisRenderer.min.js

jqplot.categoryAxisRenderer.min.js

458 ms

swfobject.js

swfobject.js

572 ms

base.js

base.js

458 ms

js

js

68 ms

ddrivetooltip.js

ddrivetooltip.js

456 ms

get.fcgi

get.fcgi

679 ms

adsbygoogle.js

adsbygoogle.js

123 ms

get.fcgi

get.fcgi

850 ms

hmapxy.js

hmapxy.js

608 ms

get.fcgi

get.fcgi

697 ms

sdk.37c02f794fb90d769910ffc2dab998e108db598b.js

sdk.37c02f794fb90d769910ffc2dab998e108db598b.js

6 ms

logo.png

logo.png

110 ms

logo_zoznam.gif

logo_zoznam.gif

115 ms

sf-btn-big.png

sf-btn-big.png

215 ms

xgemius.js

xgemius.js

1197 ms

top_info_delim_bg.gif

top_info_delim_bg.gif

226 ms

top_links_top_bg.gif

top_links_top_bg.gif

224 ms

box_normal_bg.gif

box_normal_bg.gif

109 ms

box_normal_top.gif

box_normal_top.gif

203 ms

search_bg.gif

search_bg.gif

328 ms

search_submit_btn_bg.gif

search_submit_btn_bg.gif

321 ms

box_normal_bottom.gif

box_normal_bottom.gif

310 ms

add_deptor_bg.gif

add_deptor_bg.gif

417 ms

box_normal_bg.gif

box_normal_bg.gif

337 ms

box_normal_top.gif

box_normal_top.gif

337 ms

box_normal_bottom.gif

box_normal_bottom.gif

416 ms

unemplyment_bg.gif

unemplyment_bg.gif

1183 ms

unemployment_div.gif

unemployment_div.gif

442 ms

trend_minus.gif

trend_minus.gif

1181 ms

news_div.gif

news_div.gif

1165 ms

homepage-logo-socpoist.jpg

homepage-logo-socpoist.jpg

1165 ms

homepage-logo-dovera.jpg

homepage-logo-dovera.jpg

1166 ms

homepage-logo-unionzp.jpg

homepage-logo-unionzp.jpg

1167 ms

input_small_bg.gif

input_small_bg.gif

1168 ms

login_btn_bg.gif

login_btn_bg.gif

1168 ms

banner_empty.gif

banner_empty.gif

1161 ms

tenders_div.gif

tenders_div.gif

1157 ms

bit_next.gif

bit_next.gif

1158 ms

badpayer_div.gif

badpayer_div.gif

1159 ms

bit_next.gif

bit_next.gif

1160 ms

bit_next.gif

bit_next.gif

1156 ms

restructuring_div.gif

restructuring_div.gif

1157 ms

border_footer_2.gif

border_footer_2.gif

1158 ms

js

js

34 ms

get.fcgi

get.fcgi

166 ms

adsbygoogle.js

adsbygoogle.js

95 ms

get.fcgi

get.fcgi

260 ms

hmapxy.js

hmapxy.js

164 ms

get.fcgi

get.fcgi

163 ms

zoznam.gif

zoznam.gif

636 ms

fpdata.js

fpdata.js

130 ms

lsget.html

lsget.html

468 ms

js

js

84 ms

analytics.js

analytics.js

78 ms

show_ads_impl.js

show_ads_impl.js

257 ms

collect

collect

18 ms

count.fcgi

count.fcgi

110 ms

collect

collect

26 ms

redot.gif

redot.gif

121 ms

zrt_lookup.html

zrt_lookup.html

58 ms

ads

ads

251 ms

top_links_bottom_bg.gif

top_links_bottom_bg.gif

254 ms

ads

ads

529 ms

rexdot.js

rexdot.js

87 ms

top_links_ico_bg.png

top_links_ico_bg.png

236 ms

afr.php

afr.php

203 ms

window_focus.js

window_focus.js

27 ms

qs_click_protection.js

qs_click_protection.js

30 ms

ufs_web_display.js

ufs_web_display.js

19 ms

activeview

activeview

73 ms

privacy_small.svg

privacy_small.svg

213 ms

lg.php

lg.php

211 ms

webfontloader.js

webfontloader.js

213 ms

animejs.js

animejs.js

206 ms

adchoices_en.svg

adchoices_en.svg

186 ms

close_button.svg

close_button.svg

198 ms

back_button2.svg

back_button2.svg

191 ms

criteo_logo_2021.svg

criteo_logo_2021.svg

188 ms

privacy.svg

privacy.svg

196 ms

reactive_library.js

reactive_library.js

195 ms

ads

ads

390 ms

ads

ads

140 ms

ads

ads

377 ms

lato-400.css

lato-400.css

14 ms

load_preloaded_resource.js

load_preloaded_resource.js

101 ms

abg_lite.js

abg_lite.js

222 ms

s

s

99 ms

c653839755d9d9a3a773c62a0253f53f.js

c653839755d9d9a3a773c62a0253f53f.js

292 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

214 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

213 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

294 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

294 ms

afr.php

afr.php

265 ms

activeview

activeview

187 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

65 ms

11558255824195728674

11558255824195728674

72 ms

css

css

61 ms

lg.php

lg.php

27 ms

ce3bf158ba5f4aee999371caffc9120e_image_ad_300x250.png

ce3bf158ba5f4aee999371caffc9120e_image_ad_300x250.png

27 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

23 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

31 ms

xjhP1ZZuKGHO2MkN5-NpKnD2PsyBoLvUaPEUlRzCpD8.js

xjhP1ZZuKGHO2MkN5-NpKnD2PsyBoLvUaPEUlRzCpD8.js

76 ms

sodar

sodar

282 ms

activeview

activeview

254 ms

sodar2.js

sodar2.js

13 ms

Accessibility Review

dlznik.sk accessibility score

58

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

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

dlznik.sk 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

Missing source maps for large first-party JavaScript

SEO Factors

dlznik.sk SEO score

92

Search Engine Optimization Advices

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    SK

  • Language Claimed

    SK

  • Encoding

    UTF-8

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

dlznik.sk

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