Website review, no card needed

pinkzebrahome.com logo

pinkzebrahome.com website review

Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 81 checks

This review found 39 issues worth fixing on pinkzebrahome.com, 16 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
2.0 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
167 ms133 msMay 9Oct 24163 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026141 ms
May 16, 2026141 ms
May 23, 2026140 ms
May 30, 2026139 ms
Jun 6, 2026140 ms
Jun 13, 2026139 ms
Jun 20, 2026138 ms
Jun 27, 2026137 ms
Jul 4, 2026137 ms
Jul 11, 2026137 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026137 ms
Aug 15, 2026138 ms
Aug 22, 2026140 ms
Aug 29, 2026141 ms
Sep 5, 2026139 ms
Sep 12, 2026144 ms
Sep 19, 2026146 ms
Sep 26, 2026154 ms
Oct 3, 2026161 ms
Oct 10, 2026162 ms
Oct 17, 2026163 ms
Oct 24, 2026163 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 pinkzebrahome.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

15 to fix34
  • Render-blocking requests

    4.8 s

    34 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.

  • Reduce unused CSS

    1.5 s · 183 KiB

    About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.1 s

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

  • 3,438 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, omnisnippet1.com and Bigcommerce and others), adding 3.9 MB and 2.6 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

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

  • Use efficient cache lifetimes

    150 ms · 793 KiB

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

  • Google Tag Manager adds 813 ms

    813 ms

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

  • Bigcommerce adds 364 ms

    364 ms

    Bigcommerce costs a phone 364 ms of main-thread work and 2.0 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.

  • omnisnippet1.com adds 483 ms

    483 ms

    omnisnippet1.com costs a phone 483 ms of main-thread work and 98 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.

  • Facebook adds 335 ms

    335 ms

    Facebook costs a phone 335 ms of main-thread work and 321 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.

  • Minify JavaScript

    300 ms · 53 KiB

    53 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    287 KiB

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

  • Legacy JavaScript

    60 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 59 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 38 ms

    38 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 29.1 s

    29.1 s

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

  • Largest Contentful Paint: 7.1 s

    7.1 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 text “LIVE NOW! LET IT SNOW, LET IT SCENT! SHOP NEW FRAGRANCE & D…”.

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • 3 images without width and height

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

7 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: 2.0 s

    2.0 s

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

  • Real-user INP: 162 ms

    162 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 341 ms

    341 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 269 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 269 requests on a phone: scripts 2.7 MB (115), images 1.3 MB (30) and other files 512 KiB (106). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.47 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9592
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

5 to fixGoogle 8584
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 14 H1 headlines

    There are 14 <h1> headlines (“My open parties”, “Your party” and “”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://pinkzebrahome.com/sitemap.xml, so Google discovers your pages only by following links.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 268 internal links, 10 external

    The homepage links to 268 pages on pinkzebrahome.com and 10 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Explore Pink Zebra Home for unique fragrances, wax melts, warmers, and home decor that elevate your space and create a …”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Discover Pink Zebra Home: Fragrance, Wax Melts & Home Decor”.

  • Canonical URL set

    The canonical URL is https://pinkzebrahome.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.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://pinkzebrahome.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

1 to fix0
  • 1 linked page is broken

    Your homepage links to https://pinkzebrahome.com/blendbash, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 15 internal pages checked

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

Best practices

3 to fixGoogle 9273
  • 1 broken image

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (8 required). Every extra field lowers completion.

  • Only about 37 words

    The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 44 calls to action

    The homepage has 44 calls to action, for example “Join My Team”, “Sign in/Register” and “Shop New”.

  • Analytics in place

    Analytics detected: Google Analytics and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on pinkzebrahome.com, including 21 speed issues, 5 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