asherunderwood.com website review

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

34 files are served with short cache lifetimes, so returning visitors download them again (1,009 KiB).

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

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (YouTube, Facebook and Google Tag Manager and others), adding 1.5 MB and 610 ms of main-thread time.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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.

Your homepage downloads 4.7 MB in 104 requests on a phone: scripts 2.1 MB (46), images 1.6 MB (10) and other files 582 KiB (18). Under 2 MB keeps phones on slow connections fast.

cropped-Asher-Underwood-Header-1.gif weighs 1.2 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example cropped-Asher-Underwood-Header-1.gif at 2,000 px wide, shown at 330 px. Resized copies would save about 916 KiB.

3 images (1.6 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.

Beacons.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 frames have no title, so screen-reader users cannot tell what they contain.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is only 15 characters: “@AsherUnderwood”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 3 <h1> headlines (“*”, “Check out the Patrick Bet-David interview playlis…” and “(even though we are shadow banned you can break t…”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 77 pages on asherunderwood.com and 31 external pages.

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.

There is no https://asherunderwood.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.

https://asherunderwood.com/gainesville-courthouse, https://asherunderwood.com/kings-and-queens-family-tree, https://asherunderwood.com/dusek-martinets-czech-ancestry-family-history, https://asherunderwood.com/great-frog-eating-sun-cherokee-north-carolina-and-the-deep-rabbit-hole, https://asherunderwood.com/blog and https://asherunderwood.com/production-timeline and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://asherunderwood.com' has been block…”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 310 words of visible text.

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

Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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