Website review, no card needed

reuse.pe logo

reuse.pe website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 85 checks

This review found 32 issues worth fixing on reuse.pe, 8 of them high impact, across 85 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
2.0 s1.6 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
357 ms190 msMay 30Nov 14222 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026237 ms
Jun 6, 2026240 ms
Jun 13, 2026242 ms
Jun 20, 2026240 ms
Jun 27, 2026238 ms
Jul 4, 2026244 ms
Jul 11, 2026247 ms
Jul 18, 2026251 ms
Jul 25, 2026256 ms
Aug 1, 2026257 ms
Aug 8, 2026261 ms
Aug 15, 2026263 ms
Aug 22, 2026269 ms
Aug 29, 2026271 ms
Sep 5, 2026283 ms
Sep 12, 2026303 ms
Sep 19, 2026320 ms
Sep 26, 2026331 ms
Oct 3, 2026338 ms
Oct 10, 2026336 ms
Oct 17, 2026298 ms
Oct 24, 2026259 ms
Oct 31, 2026221 ms
Nov 7, 2026209 ms
Nov 14, 2026222 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 reuse.pe (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. reuse.pe at 0.7 s0.7 s
  2. reuse.pe at 1.4 s1.4 s
  3. reuse.pe at 2.0 s2.0 s
  4. reuse.pe at 2.7 s2.7 s
  5. reuse.pe at 3.4 s3.4 s
  6. reuse.pe at 4.1 s4.1 s
  7. reuse.pe at 4.8 s4.8 s
  8. reuse.pe at 5.4 s5.4 s

Speed

9 to fix72
  • Reduce unused JavaScript

    450 ms · 709 KiB

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. 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 (Shopify, Google Maps and rebuyengine.com and others), adding 1.9 MB and 771 ms of main-thread time.

  • Render-blocking requests

    800 ms

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

  • Main-thread work: 3.4 s

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

  • 2,828 HTML elements

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

  • Shopify adds 179 ms

    179 ms

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

  • Google Maps adds 173 ms

    173 ms

    Google Maps costs a phone 173 ms of main-thread work and 464 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.

  • rebuyengine.com adds 120 ms

    120 ms

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

  • Use efficient cache lifetimes

    150 ms · 60 KiB

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

  • Reduce unused CSS

    150 ms · 53 KiB

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

  • Duplicated JavaScript

    150 ms · 50 KiB

    50 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Improve image delivery

    43 KiB

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

  • Legacy JavaScript

    36 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 18.2 s

    18.2 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.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.

  • Largest content (LCP) held steady for real visitors

    0%

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

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

    1.6 s

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

  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 562 ms

    562 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0.092

    0.092

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

  • Total Blocking Time: 147 ms

    147 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.7 MB in 388 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 388 requests on a phone: scripts 1.9 MB (127), other files 870 KiB (137) and images 713 KiB (89). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    BANNER_MOBILE_ULTIMAS_UNIDADES.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (89 KiB) are 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 1.0 g of CO₂ per visit

    1.05 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 1 image without alt text

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

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Meta description is long (298 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("www.youtube.com/@reuseperu")”.

  • One H1 headline

    Your <h1> is empty.

  • 237 internal links, 8 external

    The homepage links to 237 pages on reuse.pe and 8 external pages.

5 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Reuse Perú - Celulares y Tecnología Reacondicionada con Garantía”.

  • Canonical URL set

    The canonical URL is https://www.reuse.pe/.

  • 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.reuse.pe/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 (723 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 9 pages without a meta description

    https://www.reuse.pe/collections/celulares-samsung, https://www.reuse.pe/collections/celulares-xiaomi, https://www.reuse.pe/collections/celulares-motorola, https://www.reuse.pe/collections/honor, https://www.reuse.pe/collections/electronica and https://www.reuse.pe/collections/consolas-reacondicionadas and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.reuse.pe/collections/all, https://www.reuse.pe/collections/celulares, https://www.reuse.pe/collections/celulares-apple, https://www.reuse.pe/collections/celulares-samsung, https://www.reuse.pe/collections/celulares-xiaomi and https://www.reuse.pe/collections/celulares-motorola and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9678
  • 6 broken images

    6 images failed to load on a phone, for example https://lh3.googleusercontent.com/gpms-cs-s/APRy3c_pqj-g6bryq6l6b-3-2-tc5TpGU1ThvlLJfX77KVie9Qdi9scRKw16gtiXBz0yGSyOUm76HV81Ftv7U0qRZGAYt6d--S5PEmRTdlSELVGnkbIUuBNzDs6vCCKcdVofBm4aY7ZDYe3Eg3g=s160.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.reuse.pe/cdn/shop/t/27/assets/tiny.content.min.css?v=7223' because its MIME ty…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 10 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 20 cookies set on arrival

    20

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 reuse.pe, 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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Whatsapp Marketing Ck · Klaviyo Email Marketing Sms · Mercado Pago Antifraud Plus · Pagefly Ai Page Builder · Ta Labels Badges · Whatsapp Abandoned Cart · Mercadopago Pf App · Vizup · Essential Post Purchase Upsell · Polar Analytics · reputon.com · carthike.com · rebuyengine.com · Selleasy

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 32 issues on reuse.pe, including 13 speed issues, 3 SEO issues and 4 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