lippetaylor.com website review

About 531 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

About 277 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

5 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

8 third-party services load with your homepage (Squarespace, Hubspot and codepen.io and others), adding 1.6 MB and 586 ms of main-thread time.

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

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

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

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

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.

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The First Earned Marketing AOR”.

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

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

The first text or image appears after 4.3 s on a phone. Good is under 1.8 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.

Nature-Made-x-Donors-Choose-8.png weighs 491 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 86 requests on a phone: images 1.8 MB (7), scripts 1.3 MB (52) and stylesheets 270 KiB (18). Under 2 MB keeps phones on slow connections fast.

Nature-Made-x-Donors-Choose-8.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).

1 image (83 KiB) is 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.

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

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

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

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

Your title is only 27 characters: “Lippe Taylor is now https://www.lippetaylor.com/prompt”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 8 <h1> headlines (“The First Earned Marketing AOR”, “Ancestry” and “Nature Made”). One clear main headline is easier for people and search engines.

Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/62961480be5d8305548…”.

The homepage links to 26 pages on lippetaylor.com and 13 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://www.lippetaylor.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://www.lippetaylor.com/about, https://www.lippetaylor.com/work, https://www.lippetaylor.com/careers and https://www.lippetaylor.com/contact all use the title “Lippe Taylor is now https://www.lippetaylor.com/prompt — Lippe Taylor”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lippetaylor.com/work/ancestry, https://www.lippetaylor.com/work/nature-made and https://www.lippetaylor.com/work/q-mixers have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lippetaylor.com/about, https://www.lippetaylor.com/work, https://www.lippetaylor.com/careers and https://www.lippetaylor.com/contact use the same meta description. A description written for each page earns more clicks.

https://www.lippetaylor.com/policies-disclosures has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lippetaylor.com/work and https://www.lippetaylor.com/contact 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.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

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

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

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

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