Website review, no card needed
andyhalko.com website review
Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 74 checks
This review found 31 issues worth fixing on andyhalko.com, 10 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.5 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Reduce unused JavaScript
280 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71. 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 (YouTube, Other Google APIs/SDKs and Cloudflare and others), adding 1.7 MB and 703 ms of main-thread time.
YouTube adds 444 ms
444 msYouTube costs a phone 444 ms of main-thread work and 1.2 MB 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
471 KiB2 images could be 471 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Other Google APIs/SDKs adds 240 ms
240 msOther Google APIs/SDKs costs a phone 240 ms of main-thread work and 357 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.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 123 KiBAbout 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
Minify JavaScript
74 KiB74 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.279
0.279The layout shifts by 0.279 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “I work at the intersection of human psychology and artifici…”. Most of its time is element render delay (1.3 s).
2 images without width and height
2 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.
1 checks passed
Total Blocking Time: 131 ms
131 msScripts block the page for only 131 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.3 MB in 84 requests
7.3 MBYour homepage downloads 7.3 MB in 84 requests on a phone: media 4.7 MB (2), scripts 1.6 MB (34) and images 636 KiB (13). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Andy-Halko-Two-Books.png.webp weighs 532 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
317 KiB2 images are downloaded at several times the size a phone draws them, for example Andy-Halko-Two-Books.png.webp at 1,618 px wide, shown at 365 px. Resized copies would save about 317 KiB.
1 image below the first screen load straight away
1 image further down the page (532 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.08 g of CO₂e: 250.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“I work at the intersection of human psychology an…” and “Andy Halko”). One clear main headline is easier for people and search engines.
11 internal links, 10 external
The homepage links to 11 pages on andyhalko.com and 10 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Andy Halko is a consultant, author, speaker, CEO of Insivia and Founder of BuyerTwin with an emphasis on Buyer Psycholo…”.
Title: 63 characters
Your title is a healthy 63 characters: “Andy Halko | Buyer Psychology & Artificial Intelligence Speaker”.
Canonical URL set
The canonical URL is https://andyhalko.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://frictionlesshq.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://andyhalko.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (313 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://andyhalko.com/books, https://andyhalko.com/speaking, https://andyhalko.com/consulting, https://andyhalko.com/insights, https://andyhalko.com/speaking-to-private-equity-leaders-about-ai and https://andyhalko.com/speaking-at-fortune-500-marketing-sales-corporate-event have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://andyhalko.com/books took over 3 s to send its HTML from our server.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 7 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://andyhalko.com/wp-content/uploads/search-filter/style.css?ver=37' because its MIME …”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 317 words of copy
The homepage carries about 317 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (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.
18 other companies contacted
Loading the homepage contacts 18 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 andyhalko.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 Tag Manager
- Hosting
- Cloudflare
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 andyhalko.com, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.