parksidecards.com website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Shopify, accessibilityassistant.com and improvedcontactform.com and others), adding 1,018 KiB and 200 ms of main-thread time.

1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

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

5 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Your homepage downloads 3.1 MB in 257 requests on a phone: images 1.1 MB (28), scripts 970 KiB (85) and other files 746 KiB (99). Under 2 MB keeps phones on slow connections fast.

2026-uswnt-fresh-faces.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).

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has 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.

Your title is 85 characters, so Google will cut it off around 60: “Collectible Trading Cards of Athletes for Fans and Collectors – Parkside Collectibles”.

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

Your <h1> is empty.

The homepage links to 77 pages on parksidecards.com and 12 external pages.

https://www.parksidecards.com/collections/all, https://www.parksidecards.com/policies/shipping-policy, https://www.parksidecards.com/collections/uswnt, https://www.parksidecards.com/collections/usl and https://www.parksidecards.com/collections/merch have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.parksidecards.com/collections/all, https://www.parksidecards.com/collections/indycar, https://www.parksidecards.com/collections/uswnt, https://www.parksidecards.com/collections/usl, https://www.parksidecards.com/collections/merch and https://www.parksidecards.com/products/2026-uswnt-the-future-of-u-s and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.improvedcontactform.com/css/widget.css' from origin 'https://www.parksidecards…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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