Website review, no card needed
locumtenens.com website review
Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 87 checks
This review found 37 issues worth fixing on locumtenens.com, 16 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 181 ms |
| May 16, 2026 | 172 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 118 ms |
| Oct 24, 2026 | 127 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
13.9 s · 6.5 MB67 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).
Improve image delivery
7.0 s · 2.3 MB16 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.0 s faster on a phone.
Render-blocking requests
6.0 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.
Reduce unused JavaScript
4.3 s · 771 KiBAbout 771 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, VWO and Facebook and others), adding 1.4 MB and 1.2 s of main-thread time.
Google Tag Manager adds 499 ms
499 msGoogle Tag Manager costs a phone 499 ms of main-thread work and 527 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.4 s
8.4 sThe first text or image appears after 8.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 27.5 s
27.5 sYour largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 27.5 s
27.5 sThe page becomes fully interactive after 27.5 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 611 ms
611 msScripts block taps and scrolling for 611 ms in total while the page loads. Good is under 200 ms.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 165 ms
165 msReal visitors wait 165 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 733 ms
733 msReal visitors wait 733 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 181 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.0 MB in 142 requests
8.0 MBYour homepage downloads 8.0 MB in 142 requests on a phone: images 3.8 MB (47), media 2.1 MB (1) and scripts 1.8 MB (51). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
app-phones.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.
13 images far larger than shown
1.2 MB13 images are downloaded at several times the size a phone draws them, for example app-phones.png at 2,000 px wide, shown at 366 px. Resized copies would save about 1.2 MB.
19 images in older formats
19 images (3.2 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.
18 images below the first screen load straight away
18 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.26 g of CO₂e: 271.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Search thousands of locum tenens jobs”, “Post unlimited jobs. For free.” and “Your strategic partner in healthcare staffing”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
68 internal links, 10 external
The homepage links to 68 pages on locumtenens.com and 10 external pages.
4 checks passed
Title: 64 characters
Your title is a healthy 64 characters: “Locum Tenens Job Board & Healthcare Recruiting - locumtenens.com”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.locumtenens.com/sitemap/.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://locumtenens.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (974 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://locumtenens.com/Resources/ManageJobs/PostJobCreate has no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://locumtenens.com/facilities/solution-suite/transition-management, https://locumtenens.com/facilities/solution-suite/telehealth, https://locumtenens.com/facilities/solution-suite/consultative-services, https://locumtenens.com/facilities/solution-suite/workforce-management-software, https://locumtenens.com/facilities/solution-suite and https://locumtenens.com/facilities/solution-suite/provider-enrollment and 5 others use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://locumtenens.com/Resources/ManageJobs/PostJobCreate has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211024516&tm=gtm002&Ver=2&mid=f5911b09-93e5-4309-acf8-882f1eabdec8&bo=1&sid=ae38b230d1e611f1b265a3f8edcb7304&vid=ae38d870d1e611f1bc4ab33ab091f323&vids=1&msclkid=N>m_.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
59 of 59 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 691 words of copy
The homepage carries about 691 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us” and “Sign up”.
1 call to action
The homepage has 1 call to action, for example “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar, Heap and LinkedIn Insight.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Heap and Hotjar and 4 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (measured from a US location before any click).
No consent tool detected
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.
35 other companies contacted
Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at locumtenens.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Heap
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on locumtenens.com, including 14 speed issues, 5 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.