Tools & Wizards About Us

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

routeplanner.app

AA Route planner Ireland: Maps, route search with driving directions and distances

Page Load Speed

1.2 sec in total

First Response

250 ms

Resources Loaded

823 ms

Page Rendered

95 ms

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. AA Route planner, distances and route search for free - easy to use map of Ireland...

Visit routeplanner.app

Key Findings

We analyzed Routeplanner.app page load time and found that the first response time was 250 ms and then it took 918 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

routeplanner.app performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.416

23/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

routeplanner.app

250 ms

routeplanner.app

438 ms

adsbygoogle.js

52 ms

app.js

113 ms

js

116 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Routeplanner.app, 20% (1 request) were made to Pagead2.googlesyndication.com and 20% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (438 ms) belongs to the original domain Routeplanner.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.5 kB (8%)

Content Size

303.9 kB

After Optimization

279.4 kB

  • HTML
  • JavaScript

In fact, the total size of Routeplanner.app main page is 303.9 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Javascripts take 270.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 24.5 kB

  • Original 33.3 kB
  • After minification 32.8 kB
  • After compression 8.8 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 24.5 kB or 74% of the original size.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 270.7 kB
  • After minification 270.7 kB
  • After compression 270.6 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.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • JavaScript

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Route Planner. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

routeplanner.app accessibility score

80

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

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

Missing source maps for large first-party JavaScript

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

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: