Tools & Wizards About Us
dhlgf.pl screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

dhlgf.pl

Tani kurier i przesyłki kurierskie | AlleKurier.pl

Page Load Speed

2.2 sec in total

First Response

65 ms

Resources Loaded

1.8 sec

Page Rendered

272 ms

dhlgf.pl screenshot

About Website

Visit dhlgf.pl now to see the best up-to-date Dhlgf content and also check out these interesting facts you probably never knew about dhlgf.pl

Tanie przesyłki kurierskie bez umowy i 70% taniej - Sprawdź nas! Tani kurier DPD, DHL, UPS, InPost, Geis, FedEx i GLS dostępny dla każdego na AlleKurier.pl.

Visit dhlgf.pl

Key Findings

We analyzed Dhlgf.pl page load time and found that the first response time was 65 ms and then it took 2.1 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

dhlgf.pl performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

allekurier.pl

65 ms

js

68 ms

ga_exp.js

20 ms

index.css

34 ms

ChatPlugin.js

403 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dhlgf.pl, 33% (15 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (901 ms) relates to the external source Opineo.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.8 kB (12%)

Content Size

634.7 kB

After Optimization

561.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dhlgf.pl main page is 634.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. 55% of websites need less resources to load. CSS take 354.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 69.3 kB

  • Original 99.5 kB
  • After minification 98.6 kB
  • After compression 30.2 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 69.3 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 104.3 kB
  • After minification 104.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. Dhlgf images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 4.5 kB

  • Original 76.3 kB
  • After minification 76.3 kB
  • After compression 71.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 354.7 kB
  • After minification 354.7 kB
  • After compression 354.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. Dhlgf.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

allekurier.pl

allekurier.pl

65 ms

js

js

68 ms

ga_exp.js

ga_exp.js

20 ms

index.css

index.css

34 ms

ChatPlugin.js

ChatPlugin.js

403 ms

fbevents.js

fbevents.js

16 ms

all.css

all.css

53 ms

css

css

37 ms

css

css

55 ms

loader.svg

loader.svg

147 ms

lovespread.php

lovespread.php

901 ms

analytics.js

analytics.js

48 ms

notify-info.png

notify-info.png

161 ms

bg-gradient.png

bg-gradient.png

180 ms

paleta-max700-opis.png

paleta-max700-opis.png

181 ms

envelope-bg-opis.png

envelope-bg-opis.png

165 ms

form-parcel-icon.png

form-parcel-icon.png

184 ms

form-cargo-icon.png

form-cargo-icon.png

139 ms

form-envelope-icon.png

form-envelope-icon.png

160 ms

arrow.png

arrow.png

181 ms

spritesheet-homev3.png

spritesheet-homev3.png

299 ms

baner-1.png

baner-1.png

193 ms

baner-2.png

baner-2.png

188 ms

baner-3.png

baner-3.png

199 ms

user.svg

user.svg

325 ms

Logo1_350x1501.jpg

Logo1_350x1501.jpg

326 ms

footernbg.png

footernbg.png

205 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

26 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

33 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

39 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

44 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

111 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

111 ms

ecommerce.js

ecommerce.js

63 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

19 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

19 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

18 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

232 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

19 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

20 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

20 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

21 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

22 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

21 ms

js

js

40 ms

sm.js

sm.js

867 ms

Accessibility Review

dhlgf.pl accessibility score

42

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

dhlgf.pl best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dhlgf.pl SEO score

79

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dhlgf.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dhlgf.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

dhlgf.pl

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