joneswalker.com website review

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

15 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

About 1.5 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

2 third-party services load with your homepage (Adobe TypeKit and Google Fonts), adding 252 KiB and 0 ms of main-thread time.

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

7 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (2.5 s).

The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 11.6 MB in 46 requests on a phone: images 9.6 MB (29), scripts 1.7 MB (5) and fonts 255 KiB (7). Under 2 MB keeps phones on slow connections fast.

abstract-technology-background.png weighs 785 KiB. On a phone connection a single image that size takes seconds.

26 images (4.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example shutterstock_551288071-homepage-fa.jpg at 1,040 px wide, shown at 234 px. Resized copies would save about 176 KiB.

3 images further down the page (169 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

28 elements hidden from screen readers can still receive keyboard focus.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

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

All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

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

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.

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

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

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

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

38 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 271 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 103 pages on joneswalker.com and 13 external pages.

There is no https://www.joneswalker.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.joneswalker.com/en and / all use the title “Jones Walker LLP | Homepage | Jones Walker LLP”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.joneswalker.com/en/insights/blogs/index.html and https://www.joneswalker.com/en/services/practices/economic-development/jones-walker-consulting-llc.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.joneswalker.com/en/professionals/index.html and https://www.joneswalker.com/professionals/index.html use the same meta description. A description written for each page earns more clicks.

/ has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.joneswalker.com/en/offices/index.html, https://www.joneswalker.com/en/contact-us.html and https://www.joneswalker.com/offices/index.html 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 36 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/ric1brt.css' violates the following Content Security Policy directive: "connect-…”.

Large scripts ship without source maps.

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

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

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

The homepage carries about 1,354 words of visible text.

Opening the homepage sets 1 cookie (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.