Website review, no card needed

papayareusables.com logo

papayareusables.com website review

Visit site (opens in a new tab)Reviewed 12 November 202622 issues · 77 checks

This review found 22 issues worth fixing on papayareusables.com, 7 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.5 s1.3 sMay 23Nov 71.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Oct 31, 20261.7 s
Nov 7, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
213 ms125 msMay 23Nov 7135 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026196 ms
May 30, 2026176 ms
Jun 6, 2026171 ms
Jun 13, 2026171 ms
Jun 20, 2026166 ms
Jun 27, 2026178 ms
Jul 4, 2026187 ms
Jul 11, 2026178 ms
Jul 18, 2026169 ms
Jul 25, 2026175 ms
Aug 1, 2026179 ms
Aug 8, 2026191 ms
Aug 15, 2026199 ms
Aug 22, 2026203 ms
Aug 29, 2026196 ms
Sep 5, 2026196 ms
Sep 12, 2026195 ms
Sep 19, 2026195 ms
Sep 26, 2026195 ms
Oct 3, 2026189 ms
Oct 10, 2026195 ms
Oct 17, 2026189 ms
Oct 24, 2026175 ms
Oct 31, 2026153 ms
Nov 7, 2026135 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 papayareusables.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix65
  • Use efficient cache lifetimes

    1.7 s · 206 KiB

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

  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    600 ms · 268 KiB

    About 268 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    390 ms · 89 KiB

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

  • Shopify adds 18 ms

    18 ms

    Shopify costs a phone 18 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Judge.me, web.app and omnisnippet1.com and others), adding 606 KiB and 335 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    17 KiB

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

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 624 ms of it running JavaScript. That is comfortably low.

  • 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 fix100
  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • Time to Interactive: 8.8 s

    8.8 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • 1 image without width and height

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

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

    114 ms

    Real visitors wait 114 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: 514 ms

    514 ms

    Real visitors wait 514 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-11-07, real Chrome visitors' tap response (inp) went from 196 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    -28%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.5 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).

  • Total Blocking Time: 24 ms

    24 ms

    Scripts block the page for only 24 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 209 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 209 requests on a phone: other files 905 KiB (118), scripts 520 KiB (46) and fonts 203 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (42 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

2 checks passed
  • 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

4 to fixGoogle 9694
  • 9 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 36 internal links, 11 external

    The homepage links to 36 pages on papayareusables.com and 11 external pages.

7 checks passed
  • Meta description: 88 characters

    Your meta description is 88 characters: “Join the eco revolution with beautiful reusable paper towels. 1 sheet replaces 17 rolls!”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Papaya Reusables | Home of The Reusable Paper Towel”.

  • Canonical URL set

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

  • llms.txt published

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

Other pages

3 to fix86
  • 2 pages share a title

    https://www.papayareusables.com/pages/privacy-policy and https://www.papayareusables.com/pages/terms-of-use all use the title “...”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.papayareusables.com/products/8-pack-paper-towels, https://www.papayareusables.com/products/8-pack-gift-bundles, https://www.papayareusables.com/pages/why-papaya and https://www.papayareusables.com/pages/papaya-academy use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.papayareusables.com/pages/why-papaya, https://www.papayareusables.com/pages/our-story and https://www.papayareusables.com/pages/papaya-academy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=a43ca08b-b2ea-485c-be95-ec000001bf11&referrer=&landingpage=https%3A%2F%2Fwww.papayareusables.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 421 words of copy

    The homepage carries about 421 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 REUSABLE PAPER TOWELS” and “Shop All”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop”, “Shop All” and “SHOP REUSABLE PAPER TOWELS”.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 20 customer or partner logos.

  • Analytics in place

    Analytics detected: Hotjar.

  • Direct contact links

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

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 Pinterest Tag (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.

  • 19 cookies set on arrival

    19

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

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

Omnisend · web.app · cloudfront.net · goaffpro.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
Analytics
Hotjar
Hosting
Shopify

Company

Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on papayareusables.com, including 10 speed issues and 1 SEO issue. 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