Website review, no card needed

paywut.com logo

paywut.com website review

Visit site (opens in a new tab)Reviewed 10 November 202623 issues · 75 checks

This review found 23 issues worth fixing on paywut.com, 7 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. 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.3 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
142 ms91 msMay 23Nov 7125 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202697 ms
May 30, 2026101 ms
Jun 6, 2026104 ms
Jun 13, 2026107 ms
Jun 20, 2026129 ms
Jun 27, 2026130 ms
Jul 4, 2026128 ms
Jul 11, 2026117 ms
Jul 18, 2026119 ms
Jul 25, 2026121 ms
Aug 1, 2026119 ms
Aug 8, 2026117 ms
Aug 15, 2026121 ms
Aug 22, 2026121 ms
Aug 29, 2026127 ms
Sep 5, 2026122 ms
Sep 12, 2026120 ms
Sep 19, 2026105 ms
Sep 26, 2026105 ms
Oct 3, 2026121 ms
Oct 10, 2026126 ms
Oct 17, 2026134 ms
Oct 24, 2026136 ms
Oct 31, 2026131 ms
Nov 7, 2026125 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 paywut.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix74
  • 6,936 HTML elements

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

  • Improve image delivery

    450 ms · 702 KiB

    28 images could be 702 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.3 s

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

  • Reduce unused JavaScript

    288 KiB

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

  • Shopify adds 53 ms

    53 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Clarity, Shopify and Google CDN and others), adding 576 KiB and 204 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    17 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (17 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.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix67
  • 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.

  • Largest Contentful Paint: 8.4 s

    8.4 s

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

  • Time to Interactive: 10.0 s

    10.0 s

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

  • Real-user INP: 242 ms

    242 ms

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

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

    +29%

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

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

    +14%

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

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

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

    1.6 s

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

  • Real-user TTFB: 768 ms

    768 ms

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

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 77 ms

    77 ms

    Scripts block the page for only 77 ms while loading. Good is under 200 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 fix85
  • Page weight: 3.5 MB in 260 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 260 requests on a phone: images 1.9 MB (68), other files 763 KiB (92) and scripts 646 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.99 g

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

2 to fixGoogle 9796
  • 32 text elements with low contrast

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

  • 1 image without alt text

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is short (6 characters)

    Your title is only 6 characters: “PayWut”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (67 characters)

    Your meta description is only 67 characters: “Bargain products for resellers and anyone looking for a great deal.”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 252 internal links, 10 external

    The homepage links to 252 pages on paywut.com and 10 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://paywut.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://paywut.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 (4,551 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://paywut.com/collections/just-dropped, https://paywut.com/pages/womens, https://paywut.com/pages/mens, https://paywut.com/pages/kids-clothing, https://paywut.com/pages/shoes and https://paywut.com/pages/electronics and 7 others 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 120 found) and read each the way a search engine does.

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

  • 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
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://shopify-extension.getredo.com/7036-a115bc9f.css' from origin 'https://paywut.com' …”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,913 words of copy

    The homepage carries about 1,913 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop Now”, “Contact Us” and “Contact”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Phone number on the homepage

    Your phone number is 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, Meta Pixel and Microsoft Clarity (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.

  • 13 cookies set on arrival

    13

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

  • 22 other companies contacted

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

Apps your storefront loads

Microsoft Clarity · Redo · Inbox · Forms

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
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on paywut.com, including 12 speed issues, 3 SEO issues and 2 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