Website review, no card needed

alcione.mx logo

alcione.mx website review

Visit site (opens in a new tab)Reviewed 30 October 202645 issues · 81 checks

This review found 45 issues worth fixing on alcione.mx, 19 of them high impact, across 81 checks. The most urgent: improve image delivery. 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.2 s2.8 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.6 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20263.7 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
592 ms332 msMay 9Oct 24551 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026363 ms
May 16, 2026362 ms
May 23, 2026367 ms
May 30, 2026370 ms
Jun 6, 2026383 ms
Jun 13, 2026406 ms
Jun 20, 2026416 ms
Jun 27, 2026432 ms
Jul 4, 2026444 ms
Jul 11, 2026449 ms
Jul 18, 2026453 ms
Jul 25, 2026459 ms
Aug 1, 2026462 ms
Aug 8, 2026478 ms
Aug 15, 2026500 ms
Aug 22, 2026529 ms
Aug 29, 2026550 ms
Sep 5, 2026560 ms
Sep 12, 2026562 ms
Sep 19, 2026550 ms
Sep 26, 2026536 ms
Oct 3, 2026535 ms
Oct 10, 2026524 ms
Oct 17, 2026519 ms
Oct 24, 2026551 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 alcione.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alcione.mx at 1.0 s1.0 s
  2. alcione.mx at 1.9 s1.9 s
  3. alcione.mx at 2.9 s2.9 s
  4. alcione.mx at 3.8 s3.8 s
  5. alcione.mx at 4.8 s4.8 s
  6. alcione.mx at 5.7 s5.7 s
  7. alcione.mx at 6.7 s6.7 s
  8. alcione.mx at 7.6 s7.6 s

Speed

12 to fix39
  • Improve image delivery

    19.4 s · 7.3 MB

    20 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.4 s faster on a phone.

  • Reduce unused JavaScript

    4.2 s · 941 KiB

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

  • Use efficient cache lifetimes

    3.0 s · 961 KiB

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and elfsightcdn.com and others), adding 3.2 MB and 1.5 s of main-thread time.

  • 16 long tasks on the main thread

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

  • Render-blocking requests

    800 ms

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

  • Google Tag Manager adds 686 ms

    686 ms

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

  • elfsightcdn.com adds 300 ms

    300 ms

    elfsightcdn.com costs a phone 300 ms of main-thread work and 1.8 MB 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.

  • Facebook adds 318 ms

    318 ms

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

  • 1,703 HTML elements

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

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 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: 26 ms

    26 ms

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

Core Web Vitals

13 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 INP: 747 ms

    747 ms

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

  • Real-user CLS: 1.60

    1.60

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

  • Largest Contentful Paint: 48.6 s

    48.6 s

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

  • Speed Index: 21.1 s

    21.1 s

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

  • Time to Interactive: 49.3 s

    49.3 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

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

    +48%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 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.

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

1 checks passed
  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

2 to fix60
  • Page weight: 11.3 MB in 217 requests

    11.3 MB

    Your homepage downloads 11.3 MB in 217 requests on a phone: images 8.0 MB (47), scripts 2.9 MB (123) and fonts 186 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    30 KiB

    1 image is downloaded at several times the size a phone draws it, for example alcione-santiago logo.jpg at 846 px wide, shown at 210 px. Resized copies would save about 30 KiB.

  • 2 images in older formats

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

    3.20 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8894
  • 5 text elements with low contrast

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

  • 1 button without a name

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

2 checks passed
  • Every image has alt text

    All 168 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 10078
  • No H1 headline

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

  • Meta description is long (419 characters)

    Your meta description is 419 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: logo is not an absolute URL ("https://alcione.mx/content/files/images/productimages/a…”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 143 internal links, 6 external

    The homepage links to 143 pages on alcione.mx and 6 external pages.

4 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Alcione tu aliado en Material Eléctrico e Iluminación”.

  • Canonical URL set

    The canonical URL is https://alcione.mx/.

  • 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.alcione.mx/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://alcione.mx/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.

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://alcione.mx/sucursales has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://alcione.mx/sucursales, https://alcione.mx/productos, https://alcione.mx/cables, https://alcione.mx/bajo-voltaje, https://alcione.mx/telecomunicaciones and https://alcione.mx/especiales 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 62 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 9287
  • 13 small tap targets

    13 of 23 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')”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 94 words

    The homepage has only about 94 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

2 checks passed
  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

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

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Sana Commerce
Analytics
Google Tag Manager
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on alcione.mx, including 25 speed issues, 4 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