Website review, no card needed

hunterfan.com.mx logo

hunterfan.com.mx website review

Visit site (opens in a new tab)Reviewed 8 November 202639 issues · 82 checks

This review found 39 issues worth fixing on hunterfan.com.mx, 15 of them high impact, across 82 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.3 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.7 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
247 ms171 msMay 16Oct 31238 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026180 ms
May 23, 2026189 ms
May 30, 2026187 ms
Jun 6, 2026196 ms
Jun 13, 2026200 ms
Jun 20, 2026199 ms
Jun 27, 2026212 ms
Jul 4, 2026202 ms
Jul 11, 2026200 ms
Jul 18, 2026199 ms
Jul 25, 2026198 ms
Aug 1, 2026204 ms
Aug 8, 2026207 ms
Aug 15, 2026215 ms
Aug 22, 2026218 ms
Aug 29, 2026214 ms
Sep 5, 2026220 ms
Sep 12, 2026217 ms
Sep 19, 2026221 ms
Sep 26, 2026225 ms
Oct 3, 2026217 ms
Oct 10, 2026218 ms
Oct 17, 2026230 ms
Oct 24, 2026237 ms
Oct 31, 2026238 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 hunterfan.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hunterfan.com.mx at 0.9 s0.9 s
  2. hunterfan.com.mx at 1.7 s1.7 s
  3. hunterfan.com.mx at 2.6 s2.6 s
  4. hunterfan.com.mx at 3.4 s3.4 s
  5. hunterfan.com.mx at 4.3 s4.3 s
  6. hunterfan.com.mx at 5.1 s5.1 s
  7. hunterfan.com.mx at 6.0 s6.0 s
  8. hunterfan.com.mx at 6.9 s6.9 s

Speed

14 to fix44
  • Reduce unused JavaScript

    3.2 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 7.3 s

    A phone's processor spends 7.3 s on main-thread work while loading, 3.8 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, Shopify and loox.io and others), adding 3.4 MB and 2.3 s of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 607 KiB

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

  • Google Tag Manager adds 654 ms

    654 ms

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

  • Shopify adds 593 ms

    593 ms

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

  • Render-blocking requests

    600 ms

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

  • Improve image delivery

    400 ms · 173 KiB

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

  • 18 long tasks on the main thread

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

  • loox.io adds 281 ms

    281 ms

    loox.io costs a phone 281 ms of main-thread work and 395 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.

  • dfktv2.com adds 222 ms

    222 ms

    dfktv2.com costs a phone 222 ms of main-thread work and 443 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.

  • 2,215 HTML elements

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

  • Klaviyo adds 150 ms

    150 ms

    Klaviyo costs a phone 150 ms of main-thread work and 324 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 · 69 KiB

    About 69 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

    26 KiB

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

    8 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 16.1 s

    16.1 s

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

  • Time to Interactive: 28.6 s

    28.6 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Total Blocking Time: 865 ms

    865 ms

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

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

    +29%

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

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

  • 3 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 184 ms

    184 ms

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

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

    777 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 5.7 MB in 488 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 488 requests on a phone: scripts 3.0 MB (103), other files 1.6 MB (274) and images 762 KiB (60). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    59628_mainbadged.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

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

    1.63 g

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

4 to fixGoogle 8694
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

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

  • 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. (2 elements).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 7780
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (20 characters)

    Your title is only 20 characters: “Room icon with couch”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 237 internal links, 9 external

    The homepage links to 237 pages on hunterfan.com.mx and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Bienvenido a Hunter Fan”.

  • Canonical URL set

    The canonical URL is https://www.hunterfan.com.mx/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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: 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,435 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 7 pages without a title

    https://www.hunterfan.com.mx/collections/residencial-y-comercial, https://www.hunterfan.com.mx/collections/mas-vendidos-2-0, https://www.hunterfan.com.mx/collections/ventiladores-de-techo-outlet, https://www.hunterfan.com.mx/collections/ventiladores-de-techo-exterior, https://www.hunterfan.com.mx/collections/ventiladores-de-techo-con-luz and https://www.hunterfan.com.mx/collections/ventiladores-de-techo-con-control-remoto and 1 other have no <title>, so Google invents the link text in results.

  • 8 pages share a title

    https://www.hunterfan.com.mx/pages/eleve-comfort, https://www.hunterfan.com.mx/pages/industrial, https://www.hunterfan.com.mx/pages/jan-fan, https://www.hunterfan.com.mx/pages/hunter-b2b, https://www.hunterfan.com.mx/pages/comprar-ventiladores-por-categoria and https://www.hunterfan.com.mx/collections/ventiladores-de-techo-techos-bajos and 2 others all use the title “eSSENTIAL Accessibility Logo”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.hunterfan.com.mx/collections/residencial-y-comercial, https://www.hunterfan.com.mx/pages/eleve-comfort, https://www.hunterfan.com.mx/pages/industrial, https://www.hunterfan.com.mx/pages/jan-fan, https://www.hunterfan.com.mx/pages/hunter-b2b and https://www.hunterfan.com.mx/collections/mas-vendidos-2-0 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.hunterfan.com.mx/pages/eleve-comfort, https://www.hunterfan.com.mx/pages/industrial and https://www.hunterfan.com.mx/pages/hunter-b2b 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 93 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9293
  • 4 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • 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: 5 trust badges. 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 368 words of copy

    The homepage carries about 368 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 6 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, Klaviyo and Meta Pixel 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.

  • 17 cookies set on arrival

    17

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

  • 53 other companies contacted

    Loading the homepage contacts 53 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 hunterfan.com.mx, 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 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Powerful Form Builder · Triplewhale · Genesis · Dealeasy · Product Labels And Badges · Essential Pre Order Presale · widgetic.com · cornercart.io · kxcdn.com · usecorner.io · loox.io · pop-convert.com · revenuehunt.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 Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Monterrey

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on hunterfan.com.mx, including 21 speed issues, 3 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