Website review, no card needed

chronos.com.pe logo

chronos.com.pe website review

Visit site (opens in a new tab)Reviewed 23 October 202658 issues · 98 checks

This review found 58 issues worth fixing on chronos.com.pe, 28 of them high impact, across 98 checks. The most urgent: render-blocking requests. 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
3.3 s3.0 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
241 ms212 msMay 2Oct 17233 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026238 ms
May 9, 2026234 ms
May 16, 2026229 ms
May 23, 2026225 ms
May 30, 2026225 ms
Jun 6, 2026225 ms
Jun 13, 2026225 ms
Jun 20, 2026224 ms
Jun 27, 2026224 ms
Jul 4, 2026222 ms
Jul 11, 2026222 ms
Jul 18, 2026225 ms
Jul 25, 2026222 ms
Aug 1, 2026220 ms
Aug 8, 2026217 ms
Aug 15, 2026215 ms
Aug 22, 2026217 ms
Aug 29, 2026220 ms
Sep 5, 2026224 ms
Sep 12, 2026226 ms
Sep 19, 2026228 ms
Sep 26, 2026229 ms
Oct 3, 2026233 ms
Oct 10, 2026233 ms
Oct 17, 2026233 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 chronos.com.pe (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chronos.com.pe at 0.8 s0.8 s
  2. chronos.com.pe at 1.6 s1.6 s
  3. chronos.com.pe at 2.4 s2.4 s
  4. chronos.com.pe at 3.2 s3.2 s
  5. chronos.com.pe at 4.0 s4.0 s
  6. chronos.com.pe at 4.8 s4.8 s
  7. chronos.com.pe at 5.6 s5.6 s
  8. chronos.com.pe at 6.4 s6.4 s

Speed

15 to fix6
  • Render-blocking requests

    3.5 s

    38 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

  • Reduce initial server response time

    2.1 s

    Reduce initial server response time. Google estimates savings of 2.1 s on a phone.

  • Document request latency

    2.1 s

    The HTML itself could arrive about 2.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    1.4 s · 521 KiB

    8 images could be 521 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • vtexassets.com adds 1.3 s

    1.3 s

    vtexassets.com costs a phone 1.3 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 6

    6/100

    Your mobile performance score is 6 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.1 s

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

  • Server response: 2.2 s

    2.2 s

    Your server takes 2.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 3.6 MB and 3.3 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 961 KiB

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

  • Google Tag Manager adds 838 ms

    838 ms

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

    300 ms · 485 KiB

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

  • Google CDN adds 527 ms

    527 ms

    Google CDN costs a phone 527 ms of main-thread work and 736 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.

  • 20 long tasks on the main thread

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

  • 1,789 HTML elements

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

  • Reduce unused CSS

    150 ms · 58 KiB

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

  • Legacy JavaScript

    150 ms · 56 KiB

    Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Phones get a much slower page than desktops

    Desktop scores 58 but mobile only 6. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

Core Web Vitals

12 to fix33
  • 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.

  • Real-user CLS: 0.82

    0.82

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Cumulative Layout Shift: 1.157

    1.157

    The layout shifts by 1.157 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 8.0 s

    8.0 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • First Contentful Paint: 5.2 s

    5.2 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user INP: 257 ms

    257 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 929 ms

    929 ms

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

  • 24 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 238 ms to 233 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-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

Images and page weight

3 to fix53
  • Page weight: 4.3 MB in 198 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 198 requests on a phone: scripts 2.5 MB (58), images 977 KiB (43) and other files 379 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    109 KiB

    1 image is downloaded at several times the size a phone draws it, for example c2dd87eb-69f0-4031-b371-3af241703a45___b8a167ae356c8a7ec0d5f at 1,656 px wide, shown at 390 px. Resized copies would save about 109 KiB.

  • 3 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (152 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.2 g of CO₂ per visit

    1.22 g

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

Accessibility

13 to fixGoogle 6280
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • 19 text elements with low contrast

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

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

  • Hidden but focusable

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

  • Orphan list items

    Some list items are not inside a list.

  • 1 image without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (5 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 5 elements on the page fail this check, rated moderate by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 8 links without text

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

  • 1 form field without a label

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

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

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9278
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (213 characters)

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

  • Structured data has 1 problem

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

  • No social preview image

    No Open Graph image, 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.

  • 65 internal links, 3 external

    The homepage links to 65 pages on chronos.com.pe and 3 external pages.

4 checks passed
  • Title: 47 characters

    Your title is a healthy 47 characters: “chronos.com.pe | Ofertas y novedades en relojes”.

  • Canonical URL set

    The canonical URL is https://www.chronos.com.pe/.

  • 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.chronos.com.pe/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://www.chronos.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.

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

Other pages

3 to fix86
  • 2 pages share a title

    / and https://www.chronos.com.pe/tiendas all use the title “chronos.com.pe | Ofertas y novedades en relojes”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.chronos.com.pe/marcas-de-lujo, https://www.chronos.com.pe/novedades, https://www.chronos.com.pe/tiendas and https://www.chronos.com.pe/cyber-chronos use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.chronos.com.pe/marcas-de-lujo, https://www.chronos.com.pe/novedades, https://www.chronos.com.pe/accesorios, https://www.chronos.com.pe/ofertas-relojes, https://www.chronos.com.pe/tiendas and https://www.chronos.com.pe/cyber-chronos and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.chronos.com.pe/tiendas 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.

  • 4 pages slow to respond

    https://www.chronos.com.pe/marcas-de-lujo, https://www.chronos.com.pe/novedades, https://www.chronos.com.pe/ofertas-relojes and https://www.chronos.com.pe/cyber-chronos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 47 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://chronosperu.vtexassets.com/arquivos/libro-reclamaciones_2.jpg.

  • 13 small tap targets

    13 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 329 words of visible text.

3 checks passed
  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

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.

  • 21 cookies set on arrival

    21

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

  • 33 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on chronos.com.pe, including 27 speed issues, 4 SEO issues 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