walkerhealthforce.com website review

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

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

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, WordPress and WordPress Site Stats and others), adding 358 KiB and 292 ms of main-thread time.

20 KiB could be saved by minifying CSS.

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

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

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.

Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Healthcare’s Specialized Workforce Partner. From individual…”.

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

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

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

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

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

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

Your homepage downloads 7.1 MB in 51 requests on a phone: images 6.3 MB (20), fonts 314 KiB (5) and scripts 251 KiB (15). Under 2 MB keeps phones on slow connections fast.

whf_health-plans-panel-bkgd.webp weighs 631 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example color_SBA.png at 664 px wide, shown at 78 px. Resized copies would save about 73 KiB.

1 image (83 KiB) is 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.

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

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

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

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

Elements with visible text labels do not have matching accessible names. (3 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 25 characters: “Home | Walker Healthforce”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Healthcare’s Specialized Workforce Partner.”, “Join forces with us.” and “We are Walker Healthforce.”). One clear main headline is easier for people and search engines.

The homepage links to 89 pages on walkerhealthforce.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://walkerhealthforce.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://walkerhealthforce.com/careers, https://walkerhealthforce.com/insights, https://walkerhealthforce.com/who-we-are, https://walkerhealthforce.com/who-we-serve, https://walkerhealthforce.com/what-we-do and https://walkerhealthforce.com/who-we-are/leadership and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 14 pages linked from your homepage 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”.

1 image is served at too low a resolution for sharp phone screens.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.