Website review, no card needed

Gusto logo

gusto.com website review

Visit site (opens in a new tab)Reviewed 14 November 202625 issues · 46 checks

This review found 25 issues worth fixing on gusto.com, 9 of them high impact, across 46 checks. The most urgent: homepage answers HTTP 403. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Gusto

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

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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sMay 23Nov 72.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
193 ms154 msMay 23Nov 7166 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026188 ms
May 30, 2026178 ms
Jun 6, 2026164 ms
Jun 13, 2026162 ms
Jun 20, 2026162 ms
Jun 27, 2026162 ms
Jul 4, 2026163 ms
Jul 11, 2026162 ms
Jul 18, 2026162 ms
Jul 25, 2026164 ms
Aug 1, 2026164 ms
Aug 8, 2026164 ms
Aug 15, 2026165 ms
Aug 22, 2026164 ms
Aug 29, 2026164 ms
Sep 5, 2026163 ms
Sep 12, 2026163 ms
Sep 19, 2026161 ms
Sep 26, 2026161 ms
Oct 3, 2026159 ms
Oct 10, 2026158 ms
Oct 17, 2026160 ms
Oct 24, 2026160 ms
Oct 31, 2026163 ms
Nov 7, 2026166 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

1 to fix100
  • Largest content (LCP) got 30% slower for real visitors

    +30%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 618 ms

    618 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 188 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

4 to fix28
  • Page weight: 5.9 MB

    5.9 MB

    Your homepage downloads 5.9 MB on a phone, 3.3 MB of it images (56%). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    555 KiB

    6 images are downloaded at several times the size a phone draws them, for example Musicians_ypkd3a.png at 3,475 px wide, shown at 718 px. Resized copies would save about 555 KiB.

  • 24 images below the first screen load straight away

    24 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (89 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.

  • About 1.7 g of CO₂ per visit

    1.67 g

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

Accessibility

3 to fix97
  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 66 links without text

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

11 to fix30
  • Page is set to noindex

    The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (16 characters)

    Your title is only 16 characters: “Just a moment...”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at gusto.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • No X (Twitter) card tag

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

Best practices

1 to fix93
  • 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 403 ()”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • Homepage answers HTTP 403

    Your homepage answered with HTTP 403, so visitors and search engines may see an error page.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 793 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “See a demo” and “Get in touch”.

Privacy and tracking

  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Amazon Ads, FullStory, Google Ads, Google Tag Manager and LinkedIn Insight and 6 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.

  • 32 cookies set on arrival

    32

    Opening the homepage sets 32 cookies, 3 of them by other companies (measured from a US location before any click).

  • 38 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

Hiring

Hiring
75 open roles
Teams
Engineering (20), Sales (9), Customer Experience (8), People (5)
Job board
greenhouse

Company

Employees
3,042
Founded
2011
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on gusto.com, including 1 speed issue, 11 SEO issues and 5 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