Website review, no card needed

casaroyal.cl logo

casaroyal.cl website review

Visit site (opens in a new tab)Reviewed 28 October 202660 issues · 99 checks

This review found 60 issues worth fixing on casaroyal.cl, 25 of them high impact, across 99 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
4.0 s3.2 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20263.6 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
335 ms224 msMay 9Oct 24304 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026322 ms
May 16, 2026317 ms
May 23, 2026309 ms
May 30, 2026303 ms
Jun 6, 2026312 ms
Jun 13, 2026310 ms
Jun 20, 2026311 ms
Jun 27, 2026311 ms
Jul 4, 2026298 ms
Jul 11, 2026292 ms
Jul 18, 2026252 ms
Jul 25, 2026237 ms
Aug 1, 2026238 ms
Aug 8, 2026247 ms
Aug 15, 2026275 ms
Aug 22, 2026295 ms
Aug 29, 2026302 ms
Sep 5, 2026301 ms
Sep 12, 2026297 ms
Sep 19, 2026294 ms
Sep 26, 2026294 ms
Oct 3, 2026297 ms
Oct 10, 2026306 ms
Oct 17, 2026304 ms
Oct 24, 2026304 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 casaroyal.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casaroyal.cl at 0.8 s0.8 s
  2. casaroyal.cl at 1.5 s1.5 s
  3. casaroyal.cl at 2.3 s2.3 s
  4. casaroyal.cl at 3.0 s3.0 s
  5. casaroyal.cl at 3.8 s3.8 s
  6. casaroyal.cl at 4.5 s4.5 s
  7. casaroyal.cl at 5.3 s5.3 s
  8. casaroyal.cl at 6.0 s6.0 s

Speed

15 to fix46
  • Render-blocking requests

    2.3 s

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

  • vtexassets.com adds 1.5 s

    1.5 s

    vtexassets.com costs a phone 1.5 s of main-thread work and 2.0 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.

  • Reduce initial server response time

    1.4 s

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

  • Document request latency

    1.4 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 5.6 s

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

  • 3,197 HTML elements

    The page has 3,197 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 (vtexassets.com, Google Tag Manager and Facebook and others), adding 2.9 MB and 2.6 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 535 KiB

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

  • Google Tag Manager adds 577 ms

    577 ms

    Google Tag Manager costs a phone 577 ms of main-thread work and 533 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 · 283 KiB

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

  • Reduce unused CSS

    300 ms · 52 KiB

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

  • Facebook adds 304 ms

    304 ms

    Facebook costs a phone 304 ms of main-thread work and 210 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.

  • 18 long tasks on the main thread

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

  • Server response: 1.5 s

    1.5 s

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    96 KiB

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

  • Legacy JavaScript

    59 KiB

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

  • Font display

    50 ms

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

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

Core Web Vitals

12 to fix0
  • 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 LCP: 4.7 s

    4.7 s

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

  • Real-user INP: 540 ms

    540 ms

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

  • Real-user FCP: 4.8 s

    4.8 s

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

  • Time to Interactive: 25.0 s

    25.0 s

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

  • Largest Contentful Paint: 8.7 s

    8.7 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 488 ms

    488 ms

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

  • 25 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

1 checks passed
  • Cumulative Layout Shift: 0.035

    0.035

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

Images and page weight

5 to fix18
  • Page weight: 5.5 MB in 236 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 236 requests on a phone: images 3.1 MB (70), scripts 1.5 MB (46) and HTML 398 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    sos.png weighs 2.0 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.2 MB

    1 image is downloaded at several times the size a phone draws it, for example sos.png at 1,537 px wide, shown at 328 px. Resized copies would save about 1.2 MB.

  • 18 images below the first screen load straight away

    18 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (2.1 MB) 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.6 g of CO₂ per visit

    1.56 g

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

Accessibility

11 to fixGoogle 7785
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 40 text elements with low contrast

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

  • 11 tap targets too small

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

  • Hidden but focusable

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

  • Malformed lists

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

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

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

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 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.

  • 36 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h5, h3 → h5 and h3 → h5), 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. (20 elements).

2 checks passed
  • Every image has alt text

    All 103 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10077
  • Title is long (98 characters)

    Your title is 98 characters, so Google will cut it off around 60: “Casa Royal.cl | Tienda online de electrónica, audio, seguridad, computación, telefonía y …”.

  • Meta description is long (282 characters)

    Your meta description is 282 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 XML sitemap

    No XML sitemap at https://www.MiTienda.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 171 internal links, 6 external

    The homepage links to 171 pages on casaroyal.cl and 6 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “CASA ROYAL: ESPECIALISTAS EN ELECTRÓNICA, TECNOLOGÍA Y HOGAR EN CHILE”.

  • Canonical URL set

    The canonical URL is https://www.casaroyal.cl/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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

Other pages

4 to fix79
  • 4 linked pages hidden from search

    https://www.casaroyal.cl/254, https://www.casaroyal.cl/307, https://www.casaroyal.cl/Top%20en%20Ventas and https://www.casaroyal.cl/servidor are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a title

    https://www.casaroyal.cl/venta-empresas, https://www.casaroyal.cl/contacto, https://www.casaroyal.cl/despacho-a-domicilio and https://www.casaroyal.cl/retiro-en-tienda all use the title “Casa Royal”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://www.casaroyal.cl/venta-empresas, https://www.casaroyal.cl/contacto, https://www.casaroyal.cl/254, https://www.casaroyal.cl/307, https://www.casaroyal.cl/despacho-a-domicilio and https://www.casaroyal.cl/retiro-en-tienda and 7 others use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.casaroyal.cl/venta-empresas, https://www.casaroyal.cl/tiendas, https://www.casaroyal.cl/contacto, https://www.casaroyal.cl/despacho-a-domicilio and https://www.casaroyal.cl/retiro-en-tienda have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.casaroyal.cl/venta-empresas, https://www.casaroyal.cl/contacto, https://www.casaroyal.cl/307, https://www.casaroyal.cl/-potensic-atom-drone-fly-more-combo-3-axis-gimbal-4k-gps/p and https://www.casaroyal.cl/introtech-tornamesa-bluetooth-con-cd-y-cassette---parlantes-externos-/p took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 24 small tap targets

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

  • 1 JavaScript error while loading

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

  • Urgency cues

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

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 5 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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

  • 24 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on casaroyal.cl, including 27 speed issues, 5 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