Website review, no card needed

go2vanguard.com logo

go2vanguard.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 80 checks

This review found 31 issues worth fixing on go2vanguard.com, 11 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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 go2vanguard.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. go2vanguard.com at 1.9 s1.9 s
  2. go2vanguard.com at 3.8 s3.8 s
  3. go2vanguard.com at 5.7 s5.7 s
  4. go2vanguard.com at 7.7 s7.7 s
  5. go2vanguard.com at 9.6 s9.6 s
  6. go2vanguard.com at 11.5 s11.5 s
  7. go2vanguard.com at 13.4 s13.4 s
  8. go2vanguard.com at 15.3 s15.3 s

Speed

9 to fix55
  • Use efficient cache lifetimes

    21.6 s · 7.3 MB

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

  • Reduce unused CSS

    10.4 s · 1.8 MB

    About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.4 s faster on a phone.

  • Render-blocking requests

    12.0 s

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

  • Reduce unused JavaScript

    5.6 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.

  • Font display

    1.1 s

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 58). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    682 KiB

    5 images could be 682 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 326 ms

    326 ms

    Google Tag Manager costs a phone 326 ms of main-thread work and 605 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,728 HTML elements

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and LiveChat and others), adding 745 KiB and 358 ms of main-thread time.

  • Document request latency

    217 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    150 ms · 24 KiB

    24 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    32 KiB

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

  • Minify JavaScript

    30 KiB

    30 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 701 ms of it running JavaScript. That is comfortably low.

  • Server response: 218 ms

    218 ms

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

Core Web Vitals

5 to fix66
  • First Contentful Paint: 14.1 s

    14.1 s

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

  • Largest Contentful Paint: 32.6 s

    32.6 s

    Your largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (13.2 s).

  • Speed Index: 26.8 s

    26.8 s

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

  • Time to Interactive: 34.7 s

    34.7 s

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

  • 4 images without width and height

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

2 checks passed
  • Total Blocking Time: 71 ms

    71 ms

    Scripts block the page for only 71 ms while loading. Good is under 200 ms.

  • 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: 8.3 MB in 133 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 133 requests on a phone: images 3.4 MB (24), scripts 2.4 MB (76) and stylesheets 1.9 MB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.36 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9698
  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 22 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 1 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 9274
  • Title is long (105 characters)

    Your title is 105 characters, so Google will cut it off around 60: “Vanguard Integrity Professionals | z/OS Mainframe Software, Cybersecurity, Information Se…”.

  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“Enterprise Security Software and Training for Mai…”, “Security Solutions for z/OS Enterprise Systems” and “Mainframe Resources”). One clear main headline is easier for people and search engines.

  • Meta description is long (277 characters)

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

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 143 internal links, 13 external

    The homepage links to 143 pages on go2vanguard.com and 13 external pages.

3 checks passed
  • Canonical URL set

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

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

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.go2vanguard.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,339 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.go2vanguard.com/custzone/NIST.php has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.go2vanguard.com/about/executive-team, https://www.go2vanguard.com/partners-resellers, https://www.go2vanguard.com/custzone/NIST.php, https://www.go2vanguard.com/contact and https://www.go2vanguard.com/offerings have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://www.go2vanguard.com/about, https://www.go2vanguard.com/about/working-at-vanguard, https://www.go2vanguard.com/about/event-schedule, https://www.go2vanguard.com/about/executive-team, https://www.go2vanguard.com/about/innovators and https://www.go2vanguard.com/partners-resellers and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 5 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: License expired”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 660 words of visible text.

6 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Event Schedule”, “Contact Us” and “Training Schedule”.

  • 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: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 go2vanguard.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
WordPress
Framework
jQuery
Analytics
Google 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 31 issues on go2vanguard.com, including 14 speed issues, 6 SEO issues and 2 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