atelegraham.com website review

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

About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 550 ms faster on a phone.

About 1.9 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (Calendly, Squarespace and Stripe and others), adding 5.1 MB and 1.3 s of main-thread time.

Calendly costs a phone 734 ms of main-thread work and 3.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.

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

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

Squarespace costs a phone 427 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.

2 images could be 520 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Stripe costs a phone 138 ms of main-thread work and 304 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.

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

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

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

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

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make Joy the First Chapter in Your Child’s Birth Story”. Most of its time is element render delay (1.4 s).

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

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 6.1 MB in 123 requests on a phone: scripts 3.4 MB (75), stylesheets 1.5 MB (18) and images 785 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

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

Your title is only 26 characters: “a telegraham: birthstories”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“Make Joy the First Chapter in Your Child’s Birth …”, “What does a doula do and why do I need one?” and “About Me”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “LocalBusiness: missing name”.

The homepage links to 31 pages on atelegraham.com and 5 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://atelegraham.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://atelegraham.com/about-brittany-graham-doula, https://atelegraham.com/contact-us and https://atelegraham.com/freebie have no meta description, so Google writes the search snippet from whatever text it finds.

https://atelegraham.com/freebie has no <h1> headline, so visitors and search engines get no clear main topic.

https://atelegraham.com/freebie 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 7 pages linked from your homepage and read each the way a search engine does.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

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 1,447 words of visible text.

Opening the homepage sets 4 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.