staffcare.com website review

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

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

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

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Optimizely and TikTok and others), adding 1.3 MB and 1.8 s of main-thread time.

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

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

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

The page has 2,831 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

1 image could be 110 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

25 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

The first text or image appears after 2.8 s on a phone. Good is under 1.8 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 226 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 160 requests on a phone: scripts 2.3 MB (53), fonts 947 KiB (6) and other files 510 KiB (54). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example anesthesiology.jpg at 2,120 px wide, shown at 311 px. Resized copies would save about 96 KiB.

1 image further down the page (119 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 70 characters, so Google will cut it off around 60: “Physician Jobs: Permanent & Locum Tenens Opportunities| AMN Healthcare”.

There are 3 <h1> headlines (“Find Your Next Physician Opportunity, Locum Tenen…”, “Permanent Physician Salary” and “Locum Tenens Hourly Pay”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 286 pages on staffcare.com and 26 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://www.amnhealthcare.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.amnhealthcare.com/jobs, https://www.amnhealthcare.com/jobs/c/Nursing, https://www.amnhealthcare.com/jobs/c/Allied, https://www.amnhealthcare.com/jobs/c/Physician and https://www.amnhealthcare.com/jobs/c/Advanced-Practice have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 images failed to load on a phone, for example https://www.amnhealthcare.com/careers/physician/.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://www.clarity.ms/tag/uet/109001059' violates the following Content Security Policy directive:…”.

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

Large scripts ship without source maps.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 48 fields (28 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 3 mores (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 43 cookies, 1 of them by other companies (measured from a US location before any click).

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