Programmable

Website review, no card needed

leresaleclarev.com logo

leresaleclarev.com website review

Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 50 checks

This review found 20 issues worth fixing on leresaleclarev.com, 5 of them high impact, across 50 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

Site score

81B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.5 s1.4 sMay 23Jul 251.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
81 ms75 msMay 23Jul 2579 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202680 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202680 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202676 ms
Jul 18, 202678 ms
Jul 25, 202679 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

leresaleclarev.com (opens in a new tab)
Full-page screenshot of leresaleclarev.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix96

  • Use efficient cache lifetimes

    750 ms · 96 KiB

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused JavaScript

    106 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (truevaultcdn.com, Shopify and shop.app and others), adding 182 KiB and 85 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    13 KiB

    About 13 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.

3 checks passed

  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 281 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

1 to fix99

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

5 checks passed

  • Speed Index: 3.4 s

    3.4 s

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

  • Time to Interactive: 3.1 s

    3.1 s

    The page is fully interactive after 3.1 s.

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Le Resale has moved to a new platform! Navigate to https://…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 20 ms

    20 ms

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

Images and page weight

100

  • About 0.3 g of CO₂ per visit

    0.31 g

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

1 checks passed

  • Page weight: 1.1 MB in 125 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 125 requests on a phone: other files 697 KiB (81), scripts 334 KiB (35) and fonts 38 KiB (2). That is a lean page.

Accessibility

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed

  • 25 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 26 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 1 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 (16 characters)

    Your title is only 16 characters: “Clare V. Re-Sale”. 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://leresaleclarev.com/sitemap.xml, so Google discovers your pages only by following links.

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

2 checks passed

  • Canonical URL set

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

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

1 to fixGoogle 9692

  • 1 JavaScript error while loading

    1 error was 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 28 words

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

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 1 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 leresaleclarev.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Trove Resale Made Easy

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on leresaleclarev.com, including 3 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