justpark.com website review

About 673 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

40 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 496 ms of main-thread time.

About 72 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.

Google CDN costs a phone 327 ms of main-thread work and 733 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.

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

4 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 first text or image appears after 12.4 s on a phone. Good is under 1.8 s.

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

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

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

Your homepage downloads 3.0 MB in 225 requests on a phone: scripts 1.6 MB (102), other files 574 KiB (60) and fonts 322 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 dropdown has no label.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

7 tap targets are too small or too close together to hit reliably with a finger.

There are 4 <h1> headlines (“The smarter way to find parking”, “Download the UK's favourite parking app” and “Find parking with us”). One clear main headline is easier for people and search engines.

Structured data found (Brand, ContactPoint, Country and DownloadAction) but with 1 problem, for example “Product: no offers (price) block”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.justpark.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at justpark.com/robots.txt, the first file search crawlers ask for.

The homepage links to 67 pages on justpark.com and 14 external pages.

Your homepage links to https://www.justpark.com/uk/parking/london/s/old-burlington-street-london-w1s3af, https://www.justpark.com/uk/parking/london/s/courtney-road-london-n7, https://www.justpark.com/uk/parking/london/s/woodrush-close-london-se146dj, https://www.justpark.com/uk/parking/london/s/byng-street-london-e14, https://www.justpark.com/uk/parking/london/s/blondin-street-london-e3-2tr-p5c756efe0817a and https://www.justpark.com/uk/parking/twickenham/s/varsity-drive-twickenham-tw1-p54d3e484b2f46 and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

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

The homepage carries about 912 words of visible text.

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.