marthabeck.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, FontAwesome CDN and termly.io and others), adding 1.6 MB and 481 ms of main-thread time.

FontAwesome CDN costs a phone 157 ms of main-thread work and 621 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.

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

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

22 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 8 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 21.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 21.6 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 13.1 MB in 121 requests on a phone: images 11.0 MB (30), scripts 1.6 MB (46) and fonts 328 KiB (8). Under 2 MB keeps phones on slow connections fast.

8 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example onken_20221024_MarthaBeck_NYC_1847-cropped-scaled.jpg at 1,574 px wide, shown at 390 px. Resized copies would save about 585 KiB.

15 images (9.9 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.

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

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

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

All page content should be contained by landmarks: 23 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 11 characters: “Martha Beck”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 54 pages on marthabeck.com and 11 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.

https://marthabeck.com/speaking is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://marthabeck.com/speaking and https://marthabeck.com/gathering-pod have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://marthabeck.com/2023/06/resources-to-track-your-purpose, whose canonical is https://marthabeck.com/2023/06/17/resources-to-track-your-purpose. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://marthabeck.com/newsletter-opt-in and https://marthabeck.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://marthabeck.com/newsletter-opt-in has 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.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.3.0/css/all.css?ver=6.3.0' from origin 'https://ma…”.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 375 words of visible text.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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