Website review, no card needed

stillwaterhc.com logo

stillwaterhc.com website review

Visit site (opens in a new tab)Reviewed 23 October 202645 issues · 81 checks

This review found 45 issues worth fixing on stillwaterhc.com, 14 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of stillwaterhc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stillwaterhc.com at 0.7 s0.7 s
  2. stillwaterhc.com at 1.4 s1.4 s
  3. stillwaterhc.com at 2.1 s2.1 s
  4. stillwaterhc.com at 2.8 s2.8 s
  5. stillwaterhc.com at 3.5 s3.5 s
  6. stillwaterhc.com at 4.2 s4.2 s
  7. stillwaterhc.com at 4.9 s4.9 s
  8. stillwaterhc.com at 5.6 s5.6 s

Speed

13 to fix43
  • Render-blocking requests

    4.2 s

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

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 4.2 s

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

  • Use efficient cache lifetimes

    7.7 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 10.2 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

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

  • website-files.com adds 121 ms

    121 ms

    website-files.com costs a phone 121 ms of main-thread work and 7.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.

  • Google CDN adds 657 ms

    657 ms

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

  • Google Tag Manager adds 621 ms

    621 ms

    Google Tag Manager costs a phone 621 ms of main-thread work and 800 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.

  • Improve image delivery

    300 ms · 72 KiB

    4 images could be 72 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 45 KiB

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

  • Facebook adds 244 ms

    244 ms

    Facebook costs a phone 244 ms of main-thread work and 306 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.

  • LiveChat adds 56 ms

    56 ms

    LiveChat costs a phone 56 ms of main-thread work and 365 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 on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    44 KiB

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

  • Minify JavaScript

    16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix51
  • Time to Interactive: 21.0 s

    21.0 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 5.7 s

    5.7 s

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

  • Total Blocking Time: 773 ms

    773 ms

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 11.0 MB in 111 requests

    11.0 MB

    Your homepage downloads 11.0 MB in 111 requests on a phone: media 7.3 MB (2), scripts 2.7 MB (48) and other files 366 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • About 3.1 g of CO₂ per visit

    3.11 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8389
  • 13 text elements with low contrast

    13 text elements don'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 (4 elements)

    All page content should be contained by landmarks: 4 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.

  • 5 form fields without a label

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

  • 5 links without text

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

  • 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 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10075
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“PROTECT CRITICAL MISSIONS.”, “Secure Our Nation.” and “Delivering At The Speed Of War”). 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 (235 characters)

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.stillwaterhc.com/sitemap.xml, so Google discovers your pages only by following links.

  • 20 internal links, 3 external

    The homepage links to 20 pages on stillwaterhc.com and 3 external pages.

2 checks passed
  • Title: 56 characters

    Your title is a healthy 56 characters: “Stillwater Human Capital - Scalable Recruiting Solutions”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.stillwaterhc.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 (1,162 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 1 linked page is broken

    Your homepage links to https://www.stillwaterhc.com/drafts/veterans, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages share a title

    https://www.stillwaterhc.com/stillwater-human-capital-careers, https://www.stillwaterhc.com/about-us and https://www.stillwaterhc.com/contact-us all use the title “Stillwater Human Capital”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.stillwaterhc.com/stillwater-human-capital-careers, https://www.stillwaterhc.com/about-us, https://www.stillwaterhc.com/veterans and https://www.stillwaterhc.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.stillwaterhc.com/categories/technical-services and https://www.stillwaterhc.com/categories/human-capital use the same meta description. A description written for each page earns more clicks.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9273
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56215591&tm=gtm002&Ver=2&mid=1a8220b0-d1c9-43d2-8135-2752cb00d1ed&bo=1&sid=feb18bb0cf1d11f1b12c6727ad98ec20&vid=feb1b3e0cf1d11f1ac7397ac70552d2d&vids=1&msclkid=N&pi=91.

  • 1 JavaScript error while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 745 words of copy

    The homepage carries about 745 words of visible text.

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Join Us” and “Contact”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 4 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 stillwaterhc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on stillwaterhc.com, including 19 speed issues, 6 SEO issues and 3 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25