Website review, no card needed

angeiongroup.com logo

angeiongroup.com website review

Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 81 checks

This review found 27 issues worth fixing on angeiongroup.com, 5 of them high impact, across 81 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
1.4 s829 msMay 2Oct 17982 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 2026962 ms
Jun 6, 2026938 ms
Jun 13, 2026895 ms
Jun 20, 2026903 ms
Jun 27, 2026916 ms
Jul 4, 2026952 ms
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 2026974 ms
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Oct 10, 2026995 ms
Oct 17, 2026982 ms
Real-visitor tap response (INP)75th percentile, phones
136 ms82 msMay 2Oct 17101 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202690 ms
May 9, 202688 ms
May 16, 2026100 ms
May 23, 2026108 ms
May 30, 2026117 ms
Jun 6, 2026118 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026100 ms
Jul 4, 2026100 ms
Jul 11, 202694 ms
Jul 18, 2026128 ms
Jul 25, 2026127 ms
Aug 1, 2026130 ms
Aug 8, 2026114 ms
Aug 15, 202695 ms
Aug 22, 202693 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 2026105 ms
Sep 19, 2026102 ms
Sep 26, 2026106 ms
Oct 3, 2026102 ms
Oct 10, 2026100 ms
Oct 17, 2026101 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 angeiongroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix62
  • Improve image delivery

    2.6 s · 722 KiB

    15 images could be 722 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    900 ms · 81 KiB

    About 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Hubspot and others), adding 712 KiB and 699 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 222 KiB

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

  • Google Tag Manager adds 469 ms

    469 ms

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

  • Reduce unused JavaScript

    150 ms · 233 KiB

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

  • 7 long tasks on the main thread

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

  • Minify CSS

    20 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 94 but mobile only 62. 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.

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

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

  • Server response: 11 ms

    11 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Writing the Rules in Progressive Settlement Administration”.

  • Time to Interactive: 12.5 s

    12.5 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.12

    0.12

    The layout shifts by 0.12 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 204 ms

    204 ms

    Scripts block taps and scrolling for 204 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.

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

    +13%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 313 ms

    313 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

Images and page weight

100
  • 1 image below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.52 g

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

3 checks passed
  • Page weight: 1.8 MB in 87 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 87 requests on a phone: images 923 KiB (31), scripts 760 KiB (24) and stylesheets 107 KiB (11). That is a lean page.

  • 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

3 to fixGoogle 9296
  • 27 tap targets too small

    27 tap targets are too small or too close together to hit reliably with a finger.

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

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Angeion Group – Progressive Settlement Administration | Angeion Group”.

  • No structured data

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

  • Meta description is long (198 characters)

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 105 internal links, 7 external

    The homepage links to 105 pages on angeiongroup.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Writing the Rules in Progressive Settlement Administration”.

  • Canonical URL set

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

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.angeiongroup.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.angeiongroup.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 (825 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 4 linked pages hidden from search

    https://www.angeiongroup.com/news/angeion-group-expands-mass-tort-litigation-management-capabilities-through-merger-with-case-works, https://www.angeiongroup.com/news/angeion-group-acquires-donlin-recano-elevating-bankruptcy-administration-with-industry-leading-innovation, https://www.angeiongroup.com/news/angeion-group-acquires-medquest-ltd-expanding-capabilities-in-the-single-event-personal-injury-market and https://www.angeiongroup.com/news are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.angeiongroup.com/insights and https://www.angeiongroup.com/events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 21 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 “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 608 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST FOR PROPOSAL”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Request for Proposal” and “Request For Proposal”.

  • 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 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 angeiongroup.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
HubSpot CMS
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 27 issues on angeiongroup.com, including 14 speed issues, 4 SEO issues and 1 conversion gap. 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