Website review, no card needed

pacificabeauty.com logo

pacificabeauty.com website review

Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 80 checks

This review found 31 issues worth fixing on pacificabeauty.com, 8 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
5.2 s1.4 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20264.4 s
Jun 13, 20264.6 s
Jun 20, 20264.7 s
Jun 27, 20264.7 s
Jul 4, 20263.4 s
Jul 11, 20262.8 s
Jul 18, 20262.4 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
218 ms142 msMay 30Nov 14154 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026151 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026170 ms
Jun 27, 2026174 ms
Jul 4, 2026168 ms
Jul 11, 2026169 ms
Jul 18, 2026174 ms
Jul 25, 2026187 ms
Aug 1, 2026196 ms
Aug 8, 2026204 ms
Aug 15, 2026209 ms
Aug 22, 2026207 ms
Aug 29, 2026202 ms
Sep 5, 2026196 ms
Sep 12, 2026194 ms
Sep 19, 2026192 ms
Sep 26, 2026188 ms
Oct 3, 2026188 ms
Oct 10, 2026186 ms
Oct 17, 2026184 ms
Oct 24, 2026179 ms
Oct 31, 2026170 ms
Nov 7, 2026163 ms
Nov 14, 2026154 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 pacificabeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pacificabeauty.com at 1.0 s1.0 s
  2. pacificabeauty.com at 2.0 s2.0 s
  3. pacificabeauty.com at 3.0 s3.0 s
  4. pacificabeauty.com at 4.0 s4.0 s
  5. pacificabeauty.com at 5.1 s5.1 s
  6. pacificabeauty.com at 6.1 s6.1 s
  7. pacificabeauty.com at 7.1 s7.1 s
  8. pacificabeauty.com at 8.1 s8.1 s

Speed

12 to fix57
  • Reduce unused JavaScript

    3.2 s · 952 KiB

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

  • Use efficient cache lifetimes

    1.2 s · 421 KiB

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

  • Main-thread work: 7.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klevu Search, Klaviyo and monkcommerce.app and others), adding 2.1 MB and 1.0 s of main-thread time.

  • Mobile performance score: 57

    57/100

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

  • Reduce unused CSS

    750 ms · 167 KiB

    About 167 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Render-blocking requests

    850 ms

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

  • Klevu Search adds 303 ms

    303 ms

    Klevu Search costs a phone 303 ms of main-thread work and 240 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.

  • monkcommerce.app adds 173 ms

    173 ms

    monkcommerce.app costs a phone 173 ms of main-thread work and 562 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.

  • Klaviyo adds 178 ms

    178 ms

    Klaviyo costs a phone 178 ms of main-thread work and 423 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.

  • 2,057 HTML elements

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

  • LoyaltyLion adds 64 ms

    64 ms

    LoyaltyLion costs a phone 64 ms of main-thread work and 353 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.

  • Legacy JavaScript

    250 ms · 93 KiB

    Polyfills for old browsers add 93 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Improve image delivery

    165 KiB

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

  • 14 long tasks on the main thread

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

  • Font display

    50 ms

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.5 s

    16.5 s

    Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A crescent moon in a starry night sky”.

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 311 ms

    311 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

8 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: 1.6 s

    1.6 s

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

  • Real-user INP: 176 ms

    176 ms

    Real visitors wait 176 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.3 s

    1.3 s

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

  • Real-user TTFB: 597 ms

    597 ms

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

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

    -52%

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

  • 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: 4.6 MB in 340 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 340 requests on a phone: scripts 2.3 MB (154), images 932 KiB (24) and other files 882 KiB (134). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 155.1 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

2 to fixGoogle 10095
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 18 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 20 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 2 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 10090
  • 2 H1 headlines

    There are 2 <h1> headlines (“Pacifica” and “11/11 Celebration Sale”). One clear main headline is easier for people and search engines.

  • Meta description is long (217 characters)

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

  • 344 internal links, 9 external

    The homepage links to 344 pages on pacificabeauty.com and 9 external pages.

6 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Pacifica Beauty | Vegan Skincare, Haircare & Fragrance”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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.pacificabeauty.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.pacificabeauty.com/collections/11-11 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.pacificabeauty.com/collections/11-11 and https://www.pacificabeauty.com/collections/new-skincare-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 144 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot redefine property: includes”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 576 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 29 calls to action

    The homepage has 29 calls to action, for example “shop brightening”, “shop barrier care” and “shop mood-boosting fragrance”.

  • 6 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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, 3 of them by other companies (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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 pacificabeauty.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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pieeye · Loyalty Rewards And Referrals · Ordergroove Subscriptions · Starapps Variant Image · Klaviyo Email Marketing Sms · Gsc Countdown Timer · Monk Free Gift With Purchase · Livemeup · hulkapps.com · rise-ai.com · pii.ai · gorgias.chat · pepperjam.com · cloudfront.net · 9gtb.com · designpackscdn.com

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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

Company

Employees
190
Headquarters
Carpinteria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on pacificabeauty.com, including 18 speed issues, 2 SEO issues and 3 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