Tools & Wizards About Us
routeplanner.app screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

routeplanner.app

Route planner Ireland: Route search with map and distances

Page Load Speed

3.2 sec in total

First Response

243 ms

Resources Loaded

2 sec

Page Rendered

937 ms

routeplanner.app screenshot

About Website

Visit routeplanner.app now to see the best up-to-date Route Planner content and also check out these interesting facts you probably never knew about routeplanner.app

Use our easy to use map with driving directions to find your way from cities, airports, theme parks, stores and more. Route planner, distances and route search for free - easy to use map of Ireland an...

Visit routeplanner.app

Key Findings

We analyzed Routeplanner.app page load time and found that the first response time was 243 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

routeplanner.app performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.433

22/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

routeplanner.app

243 ms

routeplanner.app

522 ms

adsbygoogle.js

149 ms

app.js

689 ms

analytics.js

38 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 29% of them (4 requests) were addressed to the original Routeplanner.app, 21% (3 requests) were made to Google-analytics.com and 14% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (689 ms) belongs to the original domain Routeplanner.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.4 kB (51%)

Content Size

92.3 kB

After Optimization

44.9 kB

  • HTML
  • JavaScript

In fact, the total size of Routeplanner.app main page is 92.3 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. 25% of websites need less resources to load. Javascripts take 60.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 23.3 kB

  • Original 31.5 kB
  • After minification 31.0 kB
  • After compression 8.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 23.3 kB or 74% of the original size.

JavaScript Optimization

-40%

Potential reduce by 24.1 kB

  • Original 60.8 kB
  • After minification 60.8 kB
  • After compression 36.7 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 24.1 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (33%)

Requests Now

12

After Optimization

8

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

routeplanner.app

routeplanner.app

243 ms

routeplanner.app

routeplanner.app

522 ms

adsbygoogle.js

adsbygoogle.js

149 ms

app.js

app.js

689 ms

analytics.js

analytics.js

38 ms

collect

collect

135 ms

collect

collect

131 ms

show_ads_impl_fy2021.js

show_ads_impl_fy2021.js

81 ms

zrt_lookup.html

zrt_lookup.html

63 ms

collect

collect

58 ms

collect

collect

67 ms

ga-audiences

ga-audiences

44 ms

ga-audiences

ga-audiences

30 ms

translator.min.js

translator.min.js

443 ms

Accessibility Review

routeplanner.app accessibility score

69

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

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

High

Some elements have a [tabindex] value greater than 0

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 valid value for its [lang] attribute.

Best Practices

routeplanner.app best practices score

92

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

Page has valid source maps

SEO Factors

routeplanner.app SEO score

83

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

routeplanner.app

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: