Tools & Wizards About Us
pt.distance.to screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pt.distance.to

Calculador de distâncias - Calcula as distâncias online!

Page Load Speed

865 ms in total

First Response

134 ms

Resources Loaded

590 ms

Page Rendered

141 ms

pt.distance.to screenshot

About Website

Visit pt.distance.to now to see the best up-to-date Pt Distance content for United States and also check out these interesting facts you probably never knew about pt.distance.to

O calculador de distâncias populares calcula as distâncias em quilómetros entre quaisquer locais e coordenadas, oferecendo planeamento de rotas, mapas interativos e informações.

Visit pt.distance.to

Key Findings

We analyzed Pt.distance.to page load time and found that the first response time was 134 ms and then it took 731 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

pt.distance.to performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

pt.distance.to

134 ms

pt.distance.to

169 ms

jquery.min.js

53 ms

jquery.autocomplete.min.js

72 ms

jquery.cookie.min.js

82 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Pt.distance.to, 62% (24 requests) were made to Distance.to and 15% (6 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (272 ms) relates to the external source Cdns.symplr.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.9 kB (34%)

Content Size

97.6 kB

After Optimization

64.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pt.distance.to main page is 97.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. 40% of websites need less resources to load. HTML takes 37.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 27.7 kB

  • Original 37.6 kB
  • After minification 37.0 kB
  • After compression 9.9 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 27.7 kB or 74% of the original size.

Image Optimization

-19%

Potential reduce by 5.1 kB

  • Original 27.1 kB
  • After minification 22.0 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, Pt Distance needs image optimization as it can save up to 5.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 27.8 kB
  • After minification 27.8 kB
  • After compression 27.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

-2%

Potential reduce by 97 B

  • Original 5.0 kB
  • After minification 5.0 kB
  • After compression 4.9 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. Pt.distance.to has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (75%)

Requests Now

36

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pt 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 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pt.distance.to

pt.distance.to

134 ms

pt.distance.to

pt.distance.to

169 ms

jquery.min.js

jquery.min.js

53 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

72 ms

jquery.cookie.min.js

jquery.cookie.min.js

82 ms

moment.min.js

moment.min.js

85 ms

leaflet.css

leaflet.css

68 ms

leaflet.js

leaflet.js

83 ms

maplibre-gl.css

maplibre-gl.css

102 ms

maplibre-gl.js

maplibre-gl.js

110 ms

leaflet-maplibre-gl.js

leaflet-maplibre-gl.js

106 ms

leaflet.geodesic.umd.min.js

leaflet.geodesic.umd.min.js

103 ms

leaflet.encoded.min.js

leaflet.encoded.min.js

67 ms

directions-min.js

directions-min.js

71 ms

ui-min.js

ui-min.js

179 ms

distance.js

distance.js

272 ms

style-min.css

style-min.css

103 ms

mq-min.css

mq-min.css

102 ms

email-decode.min.js

email-decode.min.js

25 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

99 ms

ua.svg

ua.svg

14 ms

en-US.png

en-US.png

15 ms

de-DE.png

de-DE.png

18 ms

da-DK.png

da-DK.png

20 ms

cs-CZ.png

cs-CZ.png

22 ms

es-ES.png

es-ES.png

34 ms

pt-PT.png

pt-PT.png

28 ms

fr-FR.png

fr-FR.png

25 ms

it-IT.png

it-IT.png

30 ms

il.png

il.png

37 ms

nl-NL.png

nl-NL.png

32 ms

sv-SE.png

sv-SE.png

44 ms

ru-RU.png

ru-RU.png

43 ms

ro-RO.png

ro-RO.png

45 ms

ar.png

ar.png

44 ms

tr-TR.png

tr-TR.png

44 ms

pl-PL.png

pl-PL.png

67 ms

uk-UA.png

uk-UA.png

67 ms

roboto-v30-latin-regular.ttf

roboto-v30-latin-regular.ttf

66 ms

Accessibility Review

pt.distance.to accessibility score

87

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.

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.

Internationalization and localization

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

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

pt.distance.to best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pt.distance.to SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

pt.distance.to

Open Graph data is detected on the main page of Pt Distance. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: