Website review, no card needed

invicta.com.pe logo

invicta.com.pe website review

Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 95 checks

This review found 40 issues worth fixing on invicta.com.pe, 12 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. 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.3 s1.8 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
241 ms216 msMay 16Oct 31232 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026225 ms
May 23, 2026228 ms
May 30, 2026227 ms
Jun 6, 2026226 ms
Jun 13, 2026224 ms
Jun 20, 2026223 ms
Jun 27, 2026220 ms
Jul 4, 2026220 ms
Jul 11, 2026220 ms
Jul 18, 2026219 ms
Jul 25, 2026220 ms
Aug 1, 2026222 ms
Aug 8, 2026221 ms
Aug 15, 2026222 ms
Aug 22, 2026223 ms
Aug 29, 2026221 ms
Sep 5, 2026223 ms
Sep 12, 2026225 ms
Sep 19, 2026225 ms
Sep 26, 2026229 ms
Oct 3, 2026232 ms
Oct 10, 2026235 ms
Oct 17, 2026238 ms
Oct 24, 2026237 ms
Oct 31, 2026232 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 invicta.com.pe (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. invicta.com.pe at 0.9 s0.9 s
  2. invicta.com.pe at 1.7 s1.7 s
  3. invicta.com.pe at 2.6 s2.6 s
  4. invicta.com.pe at 3.5 s3.5 s
  5. invicta.com.pe at 4.3 s4.3 s
  6. invicta.com.pe at 5.2 s5.2 s
  7. invicta.com.pe at 6.0 s6.0 s
  8. invicta.com.pe at 6.9 s6.9 s

Speed

12 to fix56
  • Reduce unused JavaScript

    1.8 s · 941 KiB

    About 941 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Main-thread work: 5.8 s

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

  • 4,646 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 2.1 MB and 1.1 s of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    50 ms · 776 KiB

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

  • Shopify adds 319 ms

    319 ms

    Shopify costs a phone 319 ms of main-thread work and 948 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

    300 ms · 47 KiB

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

  • Minify JavaScript

    300 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 274 ms

    274 ms

    Google Tag Manager costs a phone 274 ms of main-thread work and 357 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.

  • Other Google APIs/SDKs adds 132 ms

    132 ms

    Other Google APIs/SDKs costs a phone 132 ms of main-thread work and 376 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 · 241 KiB

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

  • 9 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Legacy JavaScript

    42 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • 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: 23 ms

    23 ms

    Your server sent the HTML in 23 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.

  • Largest Contentful Paint: 12.3 s

    12.3 s

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • 43 images without width and height

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

  • Total Blocking Time: 408 ms

    408 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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: 652 ms

    652 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

3 to fix53
  • Page weight: 5.3 MB in 283 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 283 requests on a phone: images 2.4 MB (63), scripts 1.8 MB (86) and other files 769 KiB (98). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    193 KiB

    1 image is downloaded at several times the size a phone draws it, for example banner-categoria-mexico-tiendas_Mesa_de_trabajo_1_copia_2.jp at 8,000 px wide, shown at 390 px. Resized copies would save about 193 KiB.

  • 5 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (146 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.5 g of CO₂ per visit

    1.49 g

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

Accessibility

8 to fixGoogle 7981
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 5 images without alt text

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

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

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

  • Hidden but focusable

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

  • 7 links without text

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

  • Orphan list items

    Some list items are not inside a list.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 19 automated accessibility rules passed

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

SEO

2 to fixGoogle 7594
  • Structured data has 1 problem

    Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 138 internal links, 5 external

    The homepage links to 138 pages on invicta.com.pe and 5 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Encuentra variedad de relojes Invicta, aprovecha los descuentos de CYBER WEEK 75% OFF en toda la tienda. Hacemos envíos…”.

  • One H1 headline

    Your main headline reads: “<img src="//invicta.com.pe/cdn/shop/files/logo-invicta_180x_bfe8d43a-a121-444c-91d2-81eba6cba210_175x.png?v=1613187138"…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Invicta Perú | Relojes en Descuento hasta 75% OFF”.

  • Canonical URL set

    The canonical URL is https://invicta.com.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://invicta.com.pe/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://invicta.com.pe/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.

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,226 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://invicta.com.pe/pages/contactanos has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://invicta.com.pe/collections/relojes-bolt has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://invicta.com.pe/collections/relojes-bolt has 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 (of 76 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://invicta.com.pe/.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Identifier 'observer' has already been declared”.

  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 2,066 words of visible text.

7 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Reserve”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 203 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 invicta.com.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Smart Filter Search · Mercado Pago Antifraud Plus · Judge Me Reviews · Microsoft Clarity · Hulk Form Builder · Smart Product Filters · Mercadopago Pf App · Ctx Whatsapp Chat Marketing · hulkapps.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | 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 40 issues on invicta.com.pe, including 20 speed issues, 2 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