Website review, no card needed

wandp.com logo

wandp.com website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 67 checks

This review found 31 issues worth fixing on wandp.com, 6 of them high impact, across 67 checks. The most urgent: no call to action on the first screen. 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
1.7 s1.2 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
128 ms63 msMay 16Oct 3170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026111 ms
Jun 20, 2026108 ms
Jun 27, 2026111 ms
Jul 4, 2026112 ms
Jul 11, 2026112 ms
Jul 18, 2026113 ms
Jul 25, 2026112 ms
Aug 1, 2026111 ms
Aug 8, 2026118 ms
Aug 15, 2026119 ms
Aug 22, 2026119 ms
Aug 29, 2026120 ms
Sep 5, 2026118 ms
Sep 12, 2026117 ms
Sep 19, 2026120 ms
Sep 26, 2026119 ms
Oct 3, 2026114 ms
Oct 10, 2026112 ms
Oct 17, 2026109 ms
Oct 24, 2026104 ms
Oct 31, 202670 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 wandp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix81
  • Mobile performance score: 81

    81/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (rebuyengine.com, corso.com and Klaviyo and others), adding 1.2 MB and 820 ms of main-thread time.

  • Reduce unused JavaScript

    432 KiB

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

  • rebuyengine.com adds 294 ms

    294 ms

    rebuyengine.com costs a phone 294 ms of main-thread work and 497 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.

  • 7 long tasks on the main thread

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

  • Klaviyo adds 212 ms

    212 ms

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

  • Main-thread work: 2.0 s

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

  • Use efficient cache lifetimes

    150 ms · 160 KiB

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

  • Render-blocking requests

    150 ms

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

  • Legacy JavaScript

    48 KiB

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

  • Reduce unused CSS

    43 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 12.2 s

    12.2 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • Total Blocking Time: 432 ms

    432 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

10 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.2 s

    1.2 s

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

  • Real-user INP: 76 ms

    76 ms

    Real visitors wait 76 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 614 ms

    614 ms

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

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

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

    -22%

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Thanks for visiting W&P.”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 189 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 189 requests on a phone: scripts 1.2 MB (85), other files 729 KiB (84) and stylesheets 98 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

6 to fixGoogle 9263
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (3 characters)

    Your title is only 3 characters: “W&P”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No XML sitemap

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

  • Only 2 internal links

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

3 checks passed
  • Canonical URL set

    The canonical URL is https://wandp.com/password.

  • 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://wandp.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.

Best practices

2 to fixGoogle 9687
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 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 401 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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 16 words

    The homepage has only about 16 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.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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 wandp.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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Rebuy Personalization Engine · Gorgias Live Chat Helpdesk · Instafeed · Klaviyo Email Marketing Sms · Okendo · Redo · Giftship · amazonaws.com · retention.com · socialsnowball.io · nfcube.com · shareasale.com · corso.com · getredo.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
New York

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 wandp.com, including 11 speed issues, 6 SEO issues and 6 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