talkingpointcards.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, heatmap.com and cloudfront.net and others), adding 3.4 MB and 1.4 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 674 ms of main-thread work and 1,004 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.

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

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

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

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

cloudfront.net costs a phone 178 ms of main-thread work and 607 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.

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

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

7 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

3 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.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 359 requests on a phone: scripts 3.0 MB (114), images 1.3 MB (62) and other files 913 KiB (157). Under 2 MB keeps phones on slow connections fast.

12 images (1.1 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.

hf_20260324_010423_7c054ec9-b4b0-4761-b6a9-a8d095d0dcd0-1.jp 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 is downloaded at several times the size a phone draws it, for example EveryDayConnect_03_600x_81a04350-b971-4765-a982-876cdc700f26 at 600 px wide, shown at 40 px. Resized copies would save about 90 KiB.

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

8 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.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is 66 characters, so Google will cut it off around 60: “Talking Point Cards | Deep Conversation Starter Cards for Families”.

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

Structured data found (BreadcrumbList, OnlineStore, Organization and WebSite) but with 2 problems, for example “Organization: sameAs is an empty list”.

1 link has no real href, so search engines can't follow it.

The homepage links to 119 pages on talkingpointcards.com and 0 external pages.

https://talkingpointcards.com/collections/shop-all has no meta description, so Google writes the search snippet from whatever text it finds.

https://talkingpointcards.com/pages/everydayconnect, https://talkingpointcards.com/products/family-edition, https://talkingpointcards.com/products/kids-edition, https://talkingpointcards.com/products/couples-edition, https://talkingpointcards.com/products/teens-edition and https://talkingpointcards.com/products/big-laughs-edition and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://talkingpointcards.com/.

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'push')”.

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

The homepage carries about 734 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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 34 cookies, 2 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 73 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.