route.com website review

Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.

About 239 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

4 images could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

2 third-party services load with your homepage (Google Tag Manager and datagrail.io), adding 232 KiB and 123 ms of main-thread time.

4 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.

1 file is served with short cache lifetimes, so returning visitors download them again (51 KiB).

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “woman smiling”.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 855 ms for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 6.1 s. Good is under 3.8 s.

By the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

32 visible links have no text or label, so screen readers cannot say where they go.

The homepage links to 75 pages on route.com and 13 external pages.

There is no https://www.route.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.route.com/integrations has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 396 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.