parentgiving.com website review

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 2.1 MB and 1.5 s of main-thread time.

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

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Shopify costs a phone 535 ms of main-thread work and 648 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.

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

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

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

10 images could be 313 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

Klaviyo costs a phone 221 ms of main-thread work and 619 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.

The page has 2,820 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

6 KiB could be saved by minifying CSS.

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 277 requests on a phone: scripts 2.3 MB (144), images 1.7 MB (32) and other files 793 KiB (62). Under 2 MB keeps phones on slow connections fast.

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

mobile_logo7--betterquality.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 (48 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.46 g of CO₂e: 175.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA roles used must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

The homepage links to 194 pages on parentgiving.com and 12 external pages.

There is no https://www.parentgiving.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.parentgiving.com/products/dry-direct-ultimate-protective-underwear and https://www.parentgiving.com/products/dry-direct-noir-extra-protective-underwear have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://parentgiving.myshopify.com/cdn/shop/files/pandectes-banner-logo.png?v=1770138607054.

6 of 28 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 “Invalid left-hand side in assignment”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Microsoft Ads and Microsoft Clarity and 1 more (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 24 cookies (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 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.