Website review, no card needed

goengen.com logo

goengen.com website review

Visit site (opens in a new tab)Reviewed 26 October 202641 issues · 82 checks

This review found 41 issues worth fixing on goengen.com, 18 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
6.8 s5.9 sMay 9Oct 246.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.5 s
May 16, 20266.1 s
May 23, 20266.3 s
May 30, 20266.3 s
Jun 6, 20266.0 s
Jun 13, 20266.2 s
Jun 20, 20266.1 s
Jun 27, 20266.2 s
Jul 4, 20266.2 s
Jul 11, 20266.4 s
Jul 18, 20266.3 s
Jul 25, 20266.7 s
Aug 1, 20266.7 s
Aug 8, 20266.6 s
Aug 15, 20266.7 s
Aug 22, 20266.7 s
Aug 29, 20266.7 s
Sep 5, 20266.7 s
Sep 12, 20266.7 s
Sep 19, 20266.4 s
Sep 26, 20266.5 s
Oct 3, 20266.4 s
Oct 10, 20266.4 s
Oct 17, 20266.6 s
Oct 24, 20266.5 s
Real-visitor tap response (INP)75th percentile, phones
122 ms96 msMay 9Oct 24114 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026107 ms
May 16, 2026115 ms
May 23, 2026114 ms
May 30, 2026109 ms
Jun 6, 2026109 ms
Jun 13, 202699 ms
Jun 20, 2026101 ms
Jun 27, 2026101 ms
Jul 4, 2026101 ms
Jul 11, 2026104 ms
Jul 18, 2026105 ms
Jul 25, 2026114 ms
Aug 1, 2026118 ms
Aug 8, 2026119 ms
Aug 15, 2026118 ms
Aug 22, 2026118 ms
Aug 29, 2026113 ms
Sep 5, 2026111 ms
Sep 12, 2026114 ms
Sep 19, 2026107 ms
Sep 26, 2026101 ms
Oct 3, 2026104 ms
Oct 10, 2026105 ms
Oct 17, 2026108 ms
Oct 24, 2026114 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 goengen.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goengen.com at 0.4 s0.4 s
  2. goengen.com at 0.8 s0.8 s
  3. goengen.com at 1.1 s1.1 s
  4. goengen.com at 1.5 s1.5 s
  5. goengen.com at 1.9 s1.9 s
  6. goengen.com at 2.3 s2.3 s
  7. goengen.com at 2.6 s2.6 s
  8. goengen.com at 3.0 s3.0 s

Speed

6 to fix56
  • Improve image delivery

    25.6 s · 5.7 MB

    8 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 25.6 s faster on a phone.

  • Render-blocking requests

    6.9 s

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

  • Reduce unused JavaScript

    3.3 s · 508 KiB

    About 508 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Reduce unused CSS

    1.9 s · 373 KiB

    About 373 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 344 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.

  • Use efficient cache lifetimes

    200 ms · 58 KiB

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

  • Legacy JavaScript

    200 ms · 36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Adobe Tag Manager, Cloudflare CDN and jQuery CDN and others), adding 630 KiB and 127 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Document request latency

    83 KiB

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

  • 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: 1.0 s

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

  • Server response: 103 ms

    103 ms

    Your server sent the HTML in 103 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.

  • Real-user LCP: 7.0 s

    7.0 s

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

  • Real-user FCP: 6.2 s

    6.2 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • First Contentful Paint: 8.8 s

    8.8 s

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

  • Largest Contentful Paint: 40.9 s

    40.9 s

    Your largest element takes 40.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “enGen powers healthtech for payers, providers, and patients.”.

  • Time to Interactive: 41.1 s

    41.1 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

4 checks passed
  • Real-user INP: 106 ms

    106 ms

    Real visitors wait 106 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.

  • Total Blocking Time: 79 ms

    79 ms

    Scripts block the page for only 79 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

4 to fix43
  • Page weight: 13.0 MB in 42 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 42 requests on a phone: images 6.1 MB (10), media 5.2 MB (2) and scripts 795 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.0 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.

  • 5 images below the first screen load straight away

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

  • 1 image far larger than shown

    21 KiB

    1 image is downloaded at several times the size a phone draws it, for example engen-reversedcolor-horizontal-tagline.png at 1,280 px wide, shown at 328 px. Resized copies would save about 21 KiB.

  • About 3.7 g of CO₂ per visit

    3.68 g

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

Accessibility

6 to fixGoogle 8489
  • 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.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings should not be empty (4 elements)

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

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 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

7 to fixGoogle 8363
  • No meta description

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

  • Title is short (5 characters)

    Your title is only 5 characters: “enGen”. 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.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Powering healthtech.”, “We simplify the payvider experience” and “enGen's Payvider Ecosystem”). One clear main headline is easier for people and search engines.

  • 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://goengen.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • No X (Twitter) card tag

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

  • 23 internal links, 1 external

    The homepage links to 23 pages on goengen.com and 1 external page.

1 checks passed
  • Canonical URL set

    The canonical URL is https://goengen.com/.

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://goengen.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://goengen.com/content/hmhs/en/engenhealth/en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://goengen.com/content/hmhs/en/engenhealth/en all use the title “enGen”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://goengen.com/content/hmhs/en/engenhealth/en, https://goengen.com/contact, https://goengen.com/solutions, https://goengen.com/solutions/enrollment, https://goengen.com/solutions/clinical and https://goengen.com/solutions/core-administrative-processing-system and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://goengen.com/solutions/clinical, https://goengen.com/general and https://goengen.com/general/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://goengen.com/contact and https://goengen.com/general have 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 19 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 10087
  • 5 small tap targets

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • 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 259 words of copy

    The homepage carries about 259 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”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Request a Demo open_in_new” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

Privacy and tracking

  • 11 cookies set on arrival

    11

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Hosting
Highmark

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on goengen.com, including 15 speed issues, 7 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