potofcards.com website review

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

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

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

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

2 third-party services load with your homepage (Shopify and shop.app), adding 66 KiB and 33 ms of main-thread time.

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

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 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The layout shifts by 0.165 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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 2.5 MB in 181 requests on a phone: images 1.4 MB (20), other files 782 KiB (101) and scripts 168 KiB (33). Under 2 MB keeps phones on slow connections fast.

Screenshot_2023-06-22_at_4.15.46_pm.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.71 g of CO₂e: 85.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Your title is only 12 characters: “Pot of Cards”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 26 characters: “Yu-gi-oh and Pokemon Cards”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 59 pages on potofcards.com and 1 external page.

/pages/contact, /collections/yu-gi-oh-dimension-force-booster-box, /collections/pokemon, /collections/dragon-ball-z-sealed-product, /collections/yu-gi-oh-singles and /collections/starlight-rare-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/products/fusion-destiny-blcr-en088-secret-rare-1st-edition, /products/a-124, /products/evil-twin-lil-la-blcr-en097-secret-rare-1st-edition and /products/aa use the same meta description. A description written for each page earns more clicks.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://potofcards.com/customer_authentication/redirect?locale=en&region_country=AU.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

potofcards.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

potofcards.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 has only about 203 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

potofcards.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be potofcards.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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