Tools & Wizards About Us
distance.pl screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

distance.pl

Sites-snse-PL-Site

Page Load Speed

4.6 sec in total

First Response

763 ms

Resources Loaded

3.5 sec

Page Rendered

407 ms

distance.pl screenshot

About Website

Click here to check amazing Distance content for Belarus. Otherwise, check out these important facts you probably never knew about distance.pl

SNIPES

Visit distance.pl

Key Findings

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

distance.pl performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value12,060 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.501

16/100

15%

TTI (Time to Interactive)

Value29.6 s

0/100

10%

Network Requests Diagram

distance.pl

763 ms

main_min.css

337 ms

PopUp.css

222 ms

ld.js

25 ms

PopUp.js

213 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 43% of them (43 requests) were addressed to the original Distance.pl, 7% (7 requests) were made to M.goadservices.com and 5% (5 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Distance.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (53%)

Content Size

2.0 MB

After Optimization

941.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 304.6 kB

  • Original 335.0 kB
  • After minification 182.4 kB
  • After compression 30.4 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 152.6 kB, which is 46% 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 304.6 kB or 91% of the original size.

Image Optimization

-9%

Potential reduce by 63.6 kB

  • Original 673.9 kB
  • After minification 610.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. Distance images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 581.7 kB

  • Original 858.6 kB
  • After minification 851.9 kB
  • After compression 276.9 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 581.7 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 103.3 kB

  • Original 127.0 kB
  • After minification 126.4 kB
  • After compression 23.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. Distance.pl needs all CSS files to be minified and compressed as it can save up to 103.3 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

82

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

distance.pl

distance.pl

763 ms

main_min.css

main_min.css

337 ms

PopUp.css

PopUp.css

222 ms

ld.js

ld.js

25 ms

PopUp.js

PopUp.js

213 ms

main.js

main.js

668 ms

b159132b-4064-4d0a-80b0-bd02761ab408

b159132b-4064-4d0a-80b0-bd02761ab408

203 ms

fonts_all_min.css

fonts_all_min.css

122 ms

dc.js

dc.js

67 ms

logo_dp.png

logo_dp.png

345 ms

22b9f838003345e338b751fbbf091425.jpg

22b9f838003345e338b751fbbf091425.jpg

506 ms

fc87d76df019722960fa13eb984d9e1f.jpg

fc87d76df019722960fa13eb984d9e1f.jpg

345 ms

cc7bd4ee308ace11cee0363af2f7c8f2.jpg

cc7bd4ee308ace11cee0363af2f7c8f2.jpg

506 ms

ca8e61e5674da3af6ddcb327d7174b65.png

ca8e61e5674da3af6ddcb327d7174b65.png

344 ms

3ee154d55923a4a92811ce77058fd99c.png

3ee154d55923a4a92811ce77058fd99c.png

618 ms

8920aeef4e7cf7e58859ad13b36b5e4b.png

8920aeef4e7cf7e58859ad13b36b5e4b.png

620 ms

8c881adf077ddce62e84238cc26c5f48.png

8c881adf077ddce62e84238cc26c5f48.png

621 ms

8aa42528b1294abe03337776fddb1c93.png

8aa42528b1294abe03337776fddb1c93.png

644 ms

a4961c5bd753c248858e19d9093fc803.png

a4961c5bd753c248858e19d9093fc803.png

715 ms

befdf41b9f9a9c94cda97d3924ff935c.png

befdf41b9f9a9c94cda97d3924ff935c.png

717 ms

1e8e82486b7bf54ca90dea1a64ada98d.png

1e8e82486b7bf54ca90dea1a64ada98d.png

826 ms

news_insta.png

news_insta.png

828 ms

news_fb.png

news_fb.png

830 ms

scl-yt.png

scl-yt.png

864 ms

blog_logo.png

blog_logo.png

935 ms

c1c23af61205996fdebdf77b2c485386.jpg

c1c23af61205996fdebdf77b2c485386.jpg

1433 ms

85c59cbf8d433923af3c26e1c803de89.jpg

85c59cbf8d433923af3c26e1c803de89.jpg

1156 ms

b1f4d3b1f134feccdac80299c567e1b2.jpg

b1f4d3b1f134feccdac80299c567e1b2.jpg

1434 ms

f5e5a47bacc418f782f83919ef1d03f1.jpg

f5e5a47bacc418f782f83919ef1d03f1.jpg

1653 ms

38a9bf443d53c90c9ef3cc74f81f1a4c.jpg

38a9bf443d53c90c9ef3cc74f81f1a4c.jpg

1671 ms

empty.gif

empty.gif

1157 ms

rapidssl.png

rapidssl.png

1540 ms

platnosci.png

platnosci.png

1652 ms

widget_v2.132.js

widget_v2.132.js

54 ms

header1.png

header1.png

1595 ms

header2.png

header2.png

1593 ms

header3.png

header3.png

1698 ms

header4.png

header4.png

1813 ms

search.png

search.png

1811 ms

user.png

user.png

1814 ms

cart.png

cart.png

1815 ms

loader.gif

loader.gif

1830 ms

gtm.js

gtm.js

144 ms

script.php

script.php

860 ms

event

event

141 ms

Lato-Regular.woff

Lato-Regular.woff

1954 ms

Lato-Light.woff

Lato-Light.woff

2090 ms

Lato-Bold.woff

Lato-Bold.woff

2069 ms

__utm.gif

__utm.gif

89 ms

b159132b-4064-4d0a-80b0-bd02761ab408

b159132b-4064-4d0a-80b0-bd02761ab408

128 ms

__$$__stringtable_lang_pl.js

__$$__stringtable_lang_pl.js

27 ms

event

event

263 ms

ga-audiences

ga-audiences

64 ms

__utm.gif

__utm.gif

44 ms

conversion_async.js

conversion_async.js

23 ms

analytics.js

analytics.js

29 ms

fbevents.js

fbevents.js

207 ms

hotjar-77043.js

hotjar-77043.js

103 ms

w.js

w.js

52 ms

b159132b-4064-4d0a-80b0-bd02761ab408

b159132b-4064-4d0a-80b0-bd02761ab408

112 ms

46 ms

60 ms

collect

collect

13 ms

collect

collect

61 ms

collect

collect

24 ms

Lato-Black.woff

Lato-Black.woff

1886 ms

clickstream.min.js

clickstream.min.js

19 ms

collect

collect

54 ms

18 ms

20 ms

storage.luckyorange.net

storage.luckyorange.net

124 ms

modules-1f5c71aea63f8df71401422ed80fbe5f.js

modules-1f5c71aea63f8df71401422ed80fbe5f.js

118 ms

ga-audiences

ga-audiences

89 ms

b159132b-4064-4d0a-80b0-bd02761ab408

b159132b-4064-4d0a-80b0-bd02761ab408

118 ms

sprites.svg

sprites.svg

1639 ms

settings.luckyorange.net

settings.luckyorange.net

19 ms

97 ms

pixel

pixel

16 ms

Pug

Pug

25 ms

56 ms

270 ms

doubleclick

doubleclick

197 ms

pubmatic

pubmatic

192 ms

smart

smart

200 ms

netsprint

netsprint

115 ms

pixel

pixel

680 ms

visit-data

visit-data

257 ms

ibillboard

ibillboard

101 ms

129 ms

all4

all4

102 ms

adform

adform

104 ms

unified.js

unified.js

117 ms

sizzle.js

sizzle.js

458 ms

script2.php

script2.php

578 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

62 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

2 ms

nr-686.min.js

nr-686.min.js

39 ms

dis.aspx

dis.aspx

196 ms

d6a48d535a

d6a48d535a

56 ms

Accessibility Review

distance.pl accessibility score

100

Accessibility Issues

Best Practices

distance.pl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

distance.pl SEO score

100

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 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 Distance.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 Distance.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

distance.pl

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