jmsearch.com website review

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

2 third-party services load with your homepage (cloudfront.net and Adobe TypeKit), adding 2.7 MB and 340 ms of main-thread time.

cloudfront.net costs a phone 340 ms of main-thread work and 2.6 MB 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.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

About 191 KiB of JavaScript is downloaded but never used on this page.

About 182 KiB of CSS is downloaded but never applied on this page.

1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

Polyfills for old browsers add 10 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.

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.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The leading retained executive search firm for private equi…”.

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

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

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

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-31, real Chrome visitors' tap response (inp) went from 91 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.4 MB in 81 requests on a phone: media 2.0 MB (1), HTML 592 KiB (1) and scripts 491 KiB (65). Under 2 MB keeps phones on slow connections fast.

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

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

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

9 images have no alt text, which hurts accessibility and image search.

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

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

Structured data found (BreadcrumbList, NewsArticle, Organization and WebPage) but with 2 problems, for example “NewsArticle: missing datePublished”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 97 pages on jmsearch.com and 6 external pages.

There is no https://jmsearch.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://jmsearch.com/organization_category/private and https://jmsearch.com/organization_category/public have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://jmsearch.com/organization_category/private-equity-executive-search, whose canonical is https://jmsearch.com/organization/private-equity-executive-search. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://jmsearch.com/organization_category/private-equity-executive-search, https://jmsearch.com/organization_category/private, https://jmsearch.com/organization_category/public, https://jmsearch.com/functional_role/board, https://jmsearch.com/functional_role/ceo and https://jmsearch.com/functional_role/finance-accounting took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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 443 words of visible text.

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.