Website review, no card needed

pacapod.com logo

pacapod.com website review

Visit site (opens in a new tab)Reviewed 10 November 202622 issues · 74 checks

This review found 22 issues worth fixing on pacapod.com, 7 of them high impact, across 74 checks. The most urgent: 6,253 HTML elements. 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

Real-visitor load time (LCP)75th percentile, phones
950 ms734 msMay 23Nov 7788 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026925 ms
May 30, 2026849 ms
Jun 6, 2026789 ms
Jun 13, 2026759 ms
Jun 20, 2026772 ms
Jun 27, 2026762 ms
Jul 4, 2026800 ms
Jul 11, 2026864 ms
Jul 18, 2026875 ms
Jul 25, 2026875 ms
Aug 1, 2026865 ms
Aug 8, 2026814 ms
Aug 15, 2026761 ms
Aug 22, 2026775 ms
Aug 29, 2026775 ms
Sep 5, 2026822 ms
Sep 12, 2026888 ms
Sep 19, 2026837 ms
Sep 26, 2026799 ms
Oct 3, 2026817 ms
Oct 10, 2026790 ms
Oct 17, 2026787 ms
Oct 24, 2026813 ms
Oct 31, 2026788 ms
Nov 7, 2026788 ms
Real-visitor tap response (INP)75th percentile, phones
102 ms84 msMay 23Nov 788 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
Jun 13, 202686 ms
Jun 20, 202686 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202698 ms
Jul 18, 202699 ms
Jul 25, 2026100 ms
Aug 1, 202698 ms
Aug 8, 202695 ms
Aug 15, 202691 ms
Aug 22, 202691 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202697 ms
Sep 19, 202694 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202694 ms
Oct 31, 202690 ms
Nov 7, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. pacapod.com at 0.5 s0.5 s
  2. pacapod.com at 1.0 s1.0 s
  3. pacapod.com at 1.5 s1.5 s
  4. pacapod.com at 2.0 s2.0 s
  5. pacapod.com at 2.4 s2.4 s
  6. pacapod.com at 2.9 s2.9 s
  7. pacapod.com at 3.4 s3.4 s
  8. pacapod.com at 3.9 s3.9 s

Speed

3 to fix91
  • 6,253 HTML elements

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

  • Render-blocking requests

    450 ms

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

  • Shopify adds 78 ms

    78 ms

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

  • Improve image delivery

    150 ms · 233 KiB

    14 images could be 233 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, Google CDN and Stamped.io and others), adding 457 KiB and 123 ms of main-thread time.

  • Reduce unused JavaScript

    56 KiB

    About 56 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    23 KiB

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

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

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 349 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

1 to fix100
  • Largest Contentful Paint: 3.3 s

    3.3 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

12 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

    Real visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 422 ms

    422 ms

    Real visitors wait 422 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 3.3 s

    3.3 s

    The page is fully interactive after 3.3 s.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix83
  • Page weight: 2.3 MB in 306 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 306 requests on a phone: other files 937 KiB (142), images 655 KiB (25) and scripts 510 KiB (101). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Screenshot_2026-10-06_at_13.48.05.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).

  • 3 images below the first screen load straight away

    3 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9393
  • 28 text elements with low contrast

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

  • 8 tap targets too small

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Baby Changing Bags | Best loved & Organised Changing Bag At PacaPod”.

  • Meta description is long (288 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("outube.com/channel/UCE7sOP-BCuBtxfnrrd1s")”.

  • One H1 headline

    Your <h1> is empty.

  • 70 internal links, 9 external

    The homepage links to 70 pages on pacapod.com and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.pacapod.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.pacapod.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.pacapod.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.pacapod.com/blogs/pacapod-life, https://www.pacapod.com/policies/shipping-policy, https://www.pacapod.com/policies/refund-policy, https://www.pacapod.com/policies/terms-of-service, https://www.pacapod.com/policies/privacy-policy and https://www.pacapod.com/policies/contact-information have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.pacapod.com/pages/delivery, https://www.pacapod.com/collections/shop-baby-changing-bags, https://www.pacapod.com/collections/changing-bag-accessories and https://www.pacapod.com/pages/help-press have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 4 small tap targets

    4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No analytics detected

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

  • 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 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 316 words of copy

    The homepage carries about 316 words of visible text.

2 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop”, “Shop All” and “Contact”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 pacapod.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · cloudfront.net · stamped.io

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on pacapod.com, including 4 speed issues, 4 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