Website review, no card needed

goarmy.com logo

goarmy.com website review

Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 82 checks

This review found 35 issues worth fixing on goarmy.com, 8 of them high impact, across 82 checks. The most urgent: page weight: 11.9 MB in 240 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

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.7 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
333 ms166 msMay 16Oct 31314 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026185 ms
May 23, 2026186 ms
May 30, 2026188 ms
Jun 6, 2026191 ms
Jun 13, 2026195 ms
Jun 20, 2026197 ms
Jun 27, 2026201 ms
Jul 4, 2026204 ms
Jul 11, 2026219 ms
Jul 18, 2026235 ms
Jul 25, 2026253 ms
Aug 1, 2026273 ms
Aug 8, 2026284 ms
Aug 15, 2026293 ms
Aug 22, 2026301 ms
Aug 29, 2026303 ms
Sep 5, 2026298 ms
Sep 12, 2026299 ms
Sep 19, 2026296 ms
Sep 26, 2026301 ms
Oct 3, 2026305 ms
Oct 10, 2026305 ms
Oct 17, 2026312 ms
Oct 24, 2026312 ms
Oct 31, 2026314 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

Full-page screenshot of goarmy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goarmy.com at 0.7 s0.7 s
  2. goarmy.com at 1.3 s1.3 s
  3. goarmy.com at 2.0 s2.0 s
  4. goarmy.com at 2.7 s2.7 s
  5. goarmy.com at 3.3 s3.3 s
  6. goarmy.com at 4.0 s4.0 s
  7. goarmy.com at 4.7 s4.7 s
  8. goarmy.com at 5.3 s5.3 s

Speed

9 to fix54
  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Decibel Insight and Adobe Tag Manager and others), adding 849 KiB and 879 ms of main-thread time.

  • Render-blocking requests

    850 ms

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Reduce unused JavaScript

    300 ms · 539 KiB

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

  • Use efficient cache lifetimes

    537 KiB

    35 files are served with short cache lifetimes, so returning visitors download them again (537 KiB).

  • Minify JavaScript

    320 ms · 50 KiB

    50 KiB could be saved by minifying JavaScript.

  • Main-thread work: 3.4 s

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

  • Facebook adds 272 ms

    272 ms

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

  • 1,530 HTML elements

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

  • 11 long tasks on the main thread

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

  • Improve image delivery

    153 KiB

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

  • Legacy JavaScript

    51 KiB

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

  • 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: 56 ms

    56 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 18.1 s

    18.1 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FIELD TESTED”. Most of its time is element render delay (2.3 s).

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user INP: 253 ms

    253 ms

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

  • Tap response (INP) got 69% slower for real visitors

    +69%

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

  • Real-user TTFB: 849 ms

    849 ms

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

  • Total Blocking Time: 501 ms

    501 ms

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

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

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 11.9 MB in 240 requests

    11.9 MB

    Your homepage downloads 11.9 MB in 240 requests on a phone: media 9.3 MB (2), scripts 1.6 MB (120) and images 584 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    31 KiB

    1 image is downloaded at several times the size a phone draws it, for example homepage-female-soldier_lg.jpg at 1,140 px wide, shown at 354 px. Resized copies would save about 31 KiB.

  • 1 image in older formats

    1 image (234 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 3.4 g of CO₂ per visit

    3.38 g

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

1 checks passed
  • Images load when needed

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

Accessibility

4 to fixGoogle 9896
  • All page content should be contained by landmarks (30 elements)

    All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 40 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: 40 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is short (29 characters)

    Your title is only 29 characters: “Be All You Can Be | U.S. Army”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (174 characters)

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

  • 136 internal links, 5 external

    The homepage links to 136 pages on goarmy.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Your future starts here.”.

  • Canonical URL set

    The canonical URL is https://www.goarmy.com/.

  • Structured data in place

    Structured data found: GovernmentOrganization and WebSite.

  • 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.goarmy.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.goarmy.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.

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,362 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

5 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5682781&Ver=2&mid=1b280e9a-bbe4-4619-90c6-934c8b1de961&bo=1&sid=906d0740d83011f1bcef7773ec4bdd6e&vid=906d3990d83011f1b4a0dbdda1726d08&vids=1&msclkid=N&pi=918639831&lg=.

  • 4 small tap targets

    4 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • A 57-field form

    Your longest form asks for 57 fields (10 required). Every extra field lowers completion.

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

    The homepage carries about 344 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact a Recruiter” and “Call”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Reasons to Join”, “Army Reserve” and “Apply”.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 3 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

    25

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 goarmy.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
Hosting
Lumen Legacy L3 Customer Shared Use

Company

Founded
1775
Headquarters
The Pentagon

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on goarmy.com, including 18 speed issues, 2 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