Website review, no card needed

Paula's Choice logo

paulaschoice.com website review

Visit site (opens in a new tab)Reviewed 17 November 202647 issues · 81 checks

This review found 47 issues worth fixing on paulaschoice.com, 20 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Paula's Choice

  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
3.6 s3.0 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.3 s
Oct 24, 20263.4 s
Oct 31, 20263.4 s
Nov 7, 20263.5 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
447 ms284 msMay 30Nov 14415 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026303 ms
Jun 6, 2026313 ms
Jun 13, 2026322 ms
Jun 20, 2026328 ms
Jun 27, 2026338 ms
Jul 4, 2026339 ms
Jul 11, 2026340 ms
Jul 18, 2026341 ms
Jul 25, 2026338 ms
Aug 1, 2026340 ms
Aug 8, 2026355 ms
Aug 15, 2026377 ms
Aug 22, 2026395 ms
Aug 29, 2026412 ms
Sep 5, 2026420 ms
Sep 12, 2026423 ms
Sep 19, 2026428 ms
Sep 26, 2026428 ms
Oct 3, 2026422 ms
Oct 10, 2026419 ms
Oct 17, 2026422 ms
Oct 24, 2026427 ms
Oct 31, 2026428 ms
Nov 7, 2026428 ms
Nov 14, 2026415 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 paulaschoice.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paulaschoice.com at 1.7 s1.7 s
  2. paulaschoice.com at 3.3 s3.3 s
  3. paulaschoice.com at 5.0 s5.0 s
  4. paulaschoice.com at 6.6 s6.6 s
  5. paulaschoice.com at 8.3 s8.3 s
  6. paulaschoice.com at 10.0 s10.0 s
  7. paulaschoice.com at 11.6 s11.6 s
  8. paulaschoice.com at 13.3 s13.3 s

Speed

14 to fix6
  • Reduce unused JavaScript

    6.1 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.

  • Use efficient cache lifetimes

    3.2 s · 1.1 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • pii.ai adds 2.8 s

    2.8 s

    pii.ai costs a phone 2.8 s of main-thread work and 188 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 17.9 s

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

  • Mobile performance score: 6

    6/100

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

  • 3,458 HTML elements

    The page has 3,458 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 (pii.ai, TikTok and poweredbyhue.app and others), adding 3.4 MB and 4.8 s of main-thread time.

  • poweredbyhue.app adds 460 ms

    460 ms

    poweredbyhue.app costs a phone 460 ms of main-thread work and 1.5 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.

  • Legacy JavaScript

    500 ms · 70 KiB

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

  • TikTok adds 498 ms

    498 ms

    TikTok costs a phone 498 ms of main-thread work and 279 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.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 407 ms

    407 ms

    Google Tag Manager costs a phone 407 ms of main-thread work and 308 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 326 ms

    326 ms

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

  • Render-blocking requests

    350 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

  • Improve image delivery

    215 KiB

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

  • Font display

    100 ms

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

  • Reduce unused CSS

    43 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 59 ms

    59 ms

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

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 4.9 s

    4.9 s

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

  • Real-user CLS: 1.05

    1.05

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

  • Largest Contentful Paint: 38.3 s

    38.3 s

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

  • Speed Index: 19.8 s

    19.8 s

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

  • Time to Interactive: 46.5 s

    46.5 s

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

  • Total Blocking Time: 4.1 s

    4.1 s

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

  • Cumulative Layout Shift: 0.706

    0.706

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

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

  • Real-user INP: 479 ms

    479 ms

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

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

    +37%

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

  • Real-user TTFB: 910 ms

    910 ms

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

  • 4 images without width and height

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

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

1 checks passed
  • Real-user FCP: 1.4 s

    1.4 s

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

Images and page weight

2 to fix60
  • Page weight: 10.8 MB in 334 requests

    10.8 MB

    Your homepage downloads 10.8 MB in 334 requests on a phone: images 5.5 MB (74), scripts 3.2 MB (88) and other files 1.3 MB (138). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    105 KiB

    2 images are downloaded at several times the size a phone draws them, for example 261101_nam_holiday-gift-guide_site_promo-tray.jpg at 1,451 px wide, shown at 276 px. Resized copies would save about 105 KiB.

  • About 3.0 g of CO₂ per visit

    3.05 g

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

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

Accessibility

6 to fixGoogle 8891
  • 29 buttons without a name

    29 buttons have no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

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

  • 11 text elements with low contrast

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

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (1 element).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 9 links crawlers can't follow

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

7 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Achieve radiant and healthy skin with Paula’s Choice Skincare. Shop our research-based skin care products for all skin …”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Paula's Choice | Shop Paula's Choice”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.paulaschoice.com/sitemap_index.xml.

AI search readiness

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

  • Organization data: 6 of 6 facts

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

  • llms.txt published

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

Best practices

3 to fixGoogle 7385
  • 7 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • Missing source maps

    Large scripts ship without source maps.

  • 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

5 to fix42
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 84 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Consultation”.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 27 cookies set on arrival

    27

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

  • 32 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on paulaschoice.com, including 27 speed issues, 3 SEO issues and 5 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