Website review, no card needed

angelpub.com logo

angelpub.com website review

Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 84 checks

This review found 40 issues worth fixing on angelpub.com, 16 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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.1 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.3 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.5 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.5 s
Oct 3, 20261.5 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
191 ms114 msMay 2Aug 15147 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026179 ms
May 9, 2026182 ms
May 16, 2026136 ms
May 23, 2026129 ms
May 30, 2026128 ms
Jun 6, 2026123 ms
Jun 13, 2026132 ms
Jun 20, 2026137 ms
Jun 27, 2026137 ms
Jul 4, 2026151 ms
Jul 11, 2026182 ms
Jul 18, 2026158 ms
Jul 25, 2026169 ms
Aug 1, 2026155 ms
Aug 8, 2026145 ms
Aug 15, 2026147 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 angelpub.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix27
  • Reduce unused JavaScript

    4.9 s · 1.5 MB

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

  • Render-blocking requests

    2.4 s

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

  • Google Tag Manager adds 2.1 s

    2.1 s

    Google Tag Manager costs a phone 2.1 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, YouTube and Google/Doubleclick Ads and others), adding 3.2 MB and 3.5 s of main-thread time.

  • Use efficient cache lifetimes

    950 ms · 899 KiB

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

  • YouTube adds 706 ms

    706 ms

    YouTube costs a phone 706 ms of main-thread work and 963 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.

  • Improve image delivery

    350 ms · 249 KiB

    10 images could be 249 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 147 KiB

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

  • 20 long tasks on the main thread

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

  • Google/Doubleclick Ads adds 213 ms

    213 ms

    Google/Doubleclick Ads costs a phone 213 ms of main-thread work and 334 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.

  • Legacy JavaScript

    150 ms · 53 KiB

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

  • Font display

    100 ms

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 61 but mobile only 27. 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.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • First Contentful Paint: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Angel Investment Research Check out our channel for the lat…”.

  • Time to Interactive: 30.2 s

    30.2 s

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

  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Real-user TTFB: 927 ms

    927 ms

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

  • 13 images without width and height

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

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

    -19%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix33
  • Page weight: 4.5 MB in 169 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 169 requests on a phone: scripts 3.3 MB (47), images 673 KiB (52) and fonts 378 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

Accessibility

4 to fixGoogle 8177
  • 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.

  • 4 images without alt text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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 skip levels

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

1 checks passed
  • 9 automated accessibility rules passed

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

SEO

4 to fixGoogle 8585
  • Meta description is short (38 characters)

    Your meta description is only 38 characters: “Angel Publishing : Investment Research”. 70 to 160 characters is enough to sell the click.

  • 14 H1 headlines

    There are 14 <h1> headlines (“Wealth Daily”, “Energy and Capital” and “The Wealth Advisory”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 14 links with vague text

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

  • 34 internal links, 25 external

    The homepage links to 34 pages on angelpub.com and 25 external pages.

5 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Angel Publishing : Investment Research”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.angelpub.com/sitemap_index.xml.

AI search readiness

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

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

Other pages

3 to fix88
  • 6 pages without a meta description

    https://www.angelpub.com/experts, https://www.angelpub.com/experts/brian-hicks, https://www.angelpub.com/experts/keith-kohl, https://www.angelpub.com/experts/jason-simpkins, https://www.angelpub.com/experts/jason-williams and https://www.angelpub.com/premium-detailed/wwp have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://www.angelpub.com/eletters, https://www.angelpub.com/premium, https://www.angelpub.com/premium-detailed/wd, https://www.angelpub.com/premium-detailed/eac, https://www.angelpub.com/premium-detailed/qc and https://www.angelpub.com/premium-detailed/ttr and 1 other use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.angelpub.com/faq, https://www.angelpub.com/experts/brian-hicks, https://www.angelpub.com/experts/keith-kohl, https://www.angelpub.com/experts/jason-simpkins, https://www.angelpub.com/experts/jason-williams and https://www.angelpub.com/premium-detailed/ttr and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.angelpub.com/faq and https://www.angelpub.com/experts/jason-simpkins 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 29 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.

  • 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

3 to fixGoogle 6987
  • 5 third-party cookies

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

  • 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 429 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 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

4 to fix63
  • 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.

  • No social proof

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

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

  • Only about 33 words

    The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

  • No map or directions link

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

4 checks passed
  • 27 calls to action

    The homepage has 27 calls to action, for example “Learn More”, “Order Now” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

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 angelpub.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
Bootstrap
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 40 issues on angelpub.com, including 20 speed issues, 4 SEO issues and 4 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