mapquest.com website review

79 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

A phone's processor spends 11.7 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and ay.delivery and others), adding 2.0 MB and 2.5 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 55 (desktop: 47). Pages that score under 90 lose visitors before the first paint.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

Google/Doubleclick Ads costs a phone 581 ms of main-thread work and 600 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 517 ms of main-thread work and 530 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

ay.delivery costs a phone 396 ms of main-thread work and 290 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Integral Ad Science costs a phone 299 ms of main-thread work and 106 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

confiant-integrations.net costs a phone 255 ms of main-thread work and 182 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

7 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 64 KiB JavaScript that modern phones do not need.

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

3 KiB could be saved by minifying JavaScript.

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.

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

Scripts block taps and scrolling for 3.9 s in total while the page loads. Good is under 200 ms.

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

Real visitors wait 272 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Search places or paste a link”.

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

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.6 MB in 393 requests on a phone: scripts 3.0 MB (77), other files 1.1 MB (224) and images 271 KiB (67). Under 2 MB keeps phones on slow connections fast.

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

<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

1 button has no accessible name, so screen readers announce just “button”.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 98 pages on mapquest.com and 16 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.mapquest.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.mapquest.com/travel and https://www.mapquest.com/routeplanner have no <title>, so Google invents the link text in results.

https://www.mapquest.com/plans and https://www.mapquest.com/collections declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.mapquest.com/plans and https://www.mapquest.com/collections all use the title “Official MapQuest - Maps, Driving Directions, Live Traffic”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mapquest.com/travel and https://www.mapquest.com/routeplanner have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mapquest.com/plans and https://www.mapquest.com/collections use the same meta description. A description written for each page earns more clicks.

https://www.mapquest.com/plans, https://www.mapquest.com/collections, https://www.mapquest.com/travel and https://www.mapquest.com/routeplanner have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mapquest.com/plans, https://www.mapquest.com/directions and https://www.mapquest.com/collections have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

89 of 110 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

17 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Google Ads, Google Analytics and Google Tag Manager and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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