Website review, no card needed

amphora.pe logo

amphora.pe website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 83 checks

This review found 37 issues worth fixing on amphora.pe, 12 of them high impact, across 83 checks. The most urgent: 10,567 HTML elements. 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.9 s1.2 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
403 ms120 msMay 16Oct 31307 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026153 ms
May 23, 2026154 ms
May 30, 2026165 ms
Jun 6, 2026191 ms
Jun 13, 2026247 ms
Jun 20, 2026288 ms
Jun 27, 2026296 ms
Jul 4, 2026307 ms
Jul 11, 2026305 ms
Jul 18, 2026310 ms
Jul 25, 2026316 ms
Aug 1, 2026333 ms
Aug 8, 2026335 ms
Aug 15, 2026357 ms
Aug 22, 2026370 ms
Aug 29, 2026341 ms
Sep 5, 2026336 ms
Sep 12, 2026331 ms
Sep 19, 2026319 ms
Sep 26, 2026321 ms
Oct 3, 2026307 ms
Oct 10, 2026293 ms
Oct 17, 2026296 ms
Oct 24, 2026299 ms
Oct 31, 2026307 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 amphora.pe (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amphora.pe at 0.4 s0.4 s
  2. amphora.pe at 0.8 s0.8 s
  3. amphora.pe at 1.2 s1.2 s
  4. amphora.pe at 1.6 s1.6 s
  5. amphora.pe at 2.0 s2.0 s
  6. amphora.pe at 2.4 s2.4 s
  7. amphora.pe at 2.8 s2.8 s
  8. amphora.pe at 3.1 s3.1 s

Speed

9 to fix59
  • 10,567 HTML elements

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

  • Main-thread work: 6.0 s

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

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59. 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 (YouTube, retailrocket.net and Clarity and others), adding 1.6 MB and 719 ms of main-thread time.

  • Reduce unused JavaScript

    722 KiB

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

  • Render-blocking requests

    550 ms

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

  • YouTube adds 401 ms

    401 ms

    YouTube costs a phone 401 ms of main-thread work and 980 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.

  • 10 long tasks on the main thread

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

  • Shopify adds 47 ms

    47 ms

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

  • Reduce unused CSS

    150 ms · 161 KiB

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

  • Improve image delivery

    150 ms · 115 KiB

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

  • Use efficient cache lifetimes

    79 KiB

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

1 checks passed
  • Server response: 28 ms

    28 ms

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

Core Web Vitals

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

  • Time to Interactive: 19.7 s

    19.7 s

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

  • Largest Contentful Paint: 6.8 s

    6.8 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user INP: 435 ms

    435 ms

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

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

    +97%

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

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

    +30%

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

  • Total Blocking Time: 446 ms

    446 ms

    Scripts block taps and scrolling for 446 ms in total while the page loads. Good is under 200 ms.

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 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.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: 651 ms

    651 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 7.5 MB in 392 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 392 requests on a phone: images 4.8 MB (144), scripts 1.6 MB (91) and other files 859 KiB (142). Under 2 MB keeps phones on slow connections fast.

  • 27 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (198 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 2.1 g of CO₂ per visit

    2.14 g

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

7 to fixGoogle 8491
  • Frames without titles

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 89 links without text

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

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Hidden but focusable

    77 elements hidden from screen readers can still receive keyboard focus.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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

1 to fixGoogle 9295
  • Meta description is long (300 characters)

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

  • 335 internal links, 2 external

    The homepage links to 335 pages on amphora.pe and 2 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Amphora Peru”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “AMPHORA | Los mejores accesorios de moda para mujer”.

  • Canonical URL set

    The canonical URL is https://amphora.pe/.

  • Structured data in place

    Structured data found: FAQPage, 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://amphora.pe/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • 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 (1,765 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://amphora.pe/collections/calzados, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://amphora.pe/collections/carteras-new-arrivals, https://amphora.pe/collections/carteras-reversibles, https://amphora.pe/collections/crossbodies-new-arrivals, https://amphora.pe/collections/mochilas-new-arrivals, https://amphora.pe/collections/porta-laptops-new-in and https://amphora.pe/collections/billeteras-new-arrivals have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://amphora.pe/collections/carteras-new-arrivals, https://amphora.pe/collections/carteras-reversibles, https://amphora.pe/collections/crossbodies-new-arrivals, https://amphora.pe/collections/mochilas-new-arrivals, https://amphora.pe/collections/porta-laptops-new-in and https://amphora.pe/collections/billeteras-new-arrivals 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 116 found) and read each the way a search engine does.

4 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6991
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://rrstatic.retailrocket.net/widget/retailrocket.widget.css' from origin 'https://amp…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 509 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “SHOP NOW”.

  • 60 short forms

    60 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 4 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.

  • 32 other companies contacted

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

Apps your storefront loads

Retail Rocket Personalization · Mercado Pago Antifraud Plus · Microsoft Clarity · Mercadopago Pf App · Forms · hextom.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
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 37 issues on amphora.pe, including 17 speed issues, 1 SEO issue and 3 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