Website review, no card needed

coolspod.com logo

coolspod.com website review

Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 76 checks

This review found 35 issues worth fixing on coolspod.com, 11 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of coolspod.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. coolspod.com at 0.4 s0.4 s
  2. coolspod.com at 0.8 s0.8 s
  3. coolspod.com at 1.1 s1.1 s
  4. coolspod.com at 1.5 s1.5 s
  5. coolspod.com at 1.9 s1.9 s
  6. coolspod.com at 2.3 s2.3 s
  7. coolspod.com at 2.6 s2.6 s
  8. coolspod.com at 3.0 s3.0 s

Speed

8 to fix54
  • Improve image delivery

    22.9 s · 4.3 MB

    8 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.9 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 199 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Fonts and others), adding 8.2 MB and 555 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • sanity.io adds 0 ms

    0 ms

    sanity.io costs a phone 0 ms of main-thread work and 7.6 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.

  • Google Tag Manager adds 553 ms

    553 ms

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

  • 5 long tasks on the main thread

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

  • Main-thread work: 2.1 s

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 45.6 s

    45.6 s

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

  • Time to Interactive: 45.6 s

    45.6 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Total Blocking Time: 428 ms

    428 ms

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

6 to fix19
  • Page weight: 8.4 MB in 58 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 58 requests on a phone: images 7.6 MB (14), scripts 575 KiB (18) and fonts 173 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 7.3 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    3.7 MB

    1 image is downloaded at several times the size a phone draws it, for example 03ee9b3fc0d15db8121aec4bd9982a0ffb0f0ea7-3110x2000.png at 3,110 px wide, shown at 358 px. Resized copies would save about 3.7 MB.

  • 2 images in older formats

    2 images (7.3 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.

  • 1 image below the first screen load straight away

    1 image further down the page (4.3 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    7a9ce553b64a974f7df7e83a14a37c3b2d46ebf2-3430x1700.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).

  • About 2.4 g of CO₂ per visit

    2.38 g

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

Accessibility

6 to fixGoogle 8591
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

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

  • Alternative text of images should not be repeated as text (14 elements)

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 205 internal links, 5 external

    The homepage links to 205 pages on coolspod.com and 5 external pages.

6 checks passed
  • Meta description: 100 characters

    Your meta description is 100 characters: “A lightweight and minimalit Astro starter theme using Shopify with Svelte, Tailwind, and TypeScript.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Coolspod Personalized: Custom Tshirt, Blanket, Pillow, Canvas”.

  • Canonical URL set

    The canonical URL is https://coolspod.com/.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://coolspod.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (503 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://coolspod.com/llms.txt (13 KiB, 184 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 15 pages share a meta description

    https://coolspod.com/collections/3d-all-over-print, https://coolspod.com/collections/3d-t-shirts, https://coolspod.com/collections/men-polo-shirt, https://coolspod.com/collections/women-polo-shirt, https://coolspod.com/collections/baseball-jersey and https://coolspod.com/collections/sport-jersey-shirt and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page slow to respond

    https://coolspod.com/collections/3d-sweatshirt took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    104 of 108 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

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

  • About 283 words of copy

    The homepage carries about 283 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Sign Up” and “Track Your Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 11 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at coolspod.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Astro
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Vercel

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on coolspod.com, including 14 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25