Website review, no card needed

pantydeal.com logo

pantydeal.com website review

Visit site (opens in a new tab)Reviewed 11 October 202625 issues · 75 checks

This review found 25 issues worth fixing on pantydeal.com, 3 of them high impact, across 75 checks. The most urgent: 8 text elements with low contrast. 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.1 s1.0 sApr 18Oct 31.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.0 s
Apr 25, 20261.0 s
May 2, 20261.0 s
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
70 ms68 msApr 18Oct 370 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202669 ms
Apr 25, 202669 ms
May 2, 202669 ms
May 9, 202669 ms
May 16, 202670 ms
May 23, 202670 ms
May 30, 202670 ms
Jun 6, 202670 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202669 ms
Jul 11, 202668 ms
Jul 18, 202669 ms
Jul 25, 202669 ms
Aug 1, 202669 ms
Aug 8, 202669 ms
Aug 15, 202669 ms
Aug 22, 202668 ms
Aug 29, 202668 ms
Sep 5, 202669 ms
Sep 12, 202669 ms
Sep 19, 202669 ms
Sep 26, 202670 ms
Oct 3, 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 pantydeal.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pantydeal.com at 0.5 s0.5 s
  2. pantydeal.com at 0.9 s0.9 s
  3. pantydeal.com at 1.4 s1.4 s
  4. pantydeal.com at 1.9 s1.9 s
  5. pantydeal.com at 2.4 s2.4 s
  6. pantydeal.com at 2.8 s2.8 s
  7. pantydeal.com at 3.3 s3.3 s
  8. pantydeal.com at 3.8 s3.8 s

Speed

5 to fix69
  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    790 ms · 102 KiB

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

  • Use efficient cache lifetimes

    450 ms · 53 KiB

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

  • Render-blocking requests

    450 ms

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

  • Reduce unused CSS

    320 ms · 40 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google Analytics and others), adding 420 KiB and 162 ms of main-thread time.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies to improve your experience. By conti…”.

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s 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.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: 69 ms

    69 ms

    Real visitors wait 69 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: 701 ms

    701 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 38 ms

    38 ms

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

Images and page weight

100
  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.2 g of CO₂ per visit

    0.20 g

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

3 checks passed
  • Page weight: 723 KiB in 39 requests

    723 KiB

    Your homepage downloads 723 KiB in 39 requests on a phone: scripts 316 KiB (8), images 180 KiB (17) and fonts 163 KiB (4). That is a lean page.

  • 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

3 to fixGoogle 8495
  • 8 text elements with low contrast

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 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 skip levels

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

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 33 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: 33 passed and 4 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 10088
  • No structured data

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

  • Meta description is long (161 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 31 internal links, 4 external

    The homepage links to 31 pages on pantydeal.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “World's #1 Marketplace for Used Panties”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Pantydeal - Sell used panties & buy worn underwear”.

  • Canonical URL set

    The canonical URL is https://pantydeal.com/.

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

  • No llms.txt

    There is no https://pantydeal.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.

2 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,180 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix74
  • 3 linked pages hidden from search

    https://pantydeal.com/selfcare, https://pantydeal.com/terms and https://pantydeal.com/privacy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://pantydeal.com/more-worn-items and https://pantydeal.com/lp/more-worn-items all use the title “Other worn items | Pantydeal”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://pantydeal.com/selfcare has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://pantydeal.com/more-worn-items and https://pantydeal.com/lp/more-worn-items use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://pantydeal.com/selfcare and https://pantydeal.com/complaint have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://pantydeal.com/more-worn-items and https://pantydeal.com/lp/more-worn-items have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 1 JavaScript error while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 form on the homepage

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

  • About 1,117 words of copy

    The homepage carries about 1,117 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: “add_shopping_cart BUY USED PANTIES” and “group_add SIGN UP”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Buy used panties”, “Sign up” and “add_shopping_cart Buy used panties”.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, 9 customer or partner logos and “Over 1.000.000 members”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 7 cookies set on arrival

    7

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on pantydeal.com, including 9 speed issues, 3 SEO issues and 1 conversion gap. 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