Website review, no card needed

habanos.com logo

habanos.com website review

Visit site (opens in a new tab)Reviewed 23 October 202647 issues · 87 checks

This review found 47 issues worth fixing on habanos.com, 21 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
6.5 s5.0 sMay 2Oct 175.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20266.3 s
May 9, 20266.2 s
May 16, 20266.0 s
May 23, 20265.8 s
May 30, 20265.9 s
Jun 6, 20265.9 s
Jun 13, 20266.0 s
Jun 20, 20266.1 s
Jun 27, 20266.1 s
Jul 4, 20265.9 s
Jul 11, 20265.7 s
Jul 18, 20265.5 s
Jul 25, 20265.4 s
Aug 1, 20265.4 s
Aug 8, 20265.4 s
Aug 15, 20265.4 s
Aug 22, 20265.4 s
Aug 29, 20265.3 s
Sep 5, 20265.3 s
Sep 12, 20265.3 s
Sep 19, 20265.2 s
Sep 26, 20265.2 s
Oct 3, 20265.2 s
Oct 10, 20265.2 s
Oct 17, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
109 ms100 msMay 2Oct 17102 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026104 ms
May 9, 2026105 ms
May 16, 2026107 ms
May 23, 2026107 ms
May 30, 2026108 ms
Jun 6, 2026108 ms
Jun 13, 2026106 ms
Jun 20, 2026106 ms
Jun 27, 2026106 ms
Jul 4, 2026107 ms
Jul 11, 2026107 ms
Jul 18, 2026106 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 2026102 ms
Aug 15, 2026102 ms
Aug 22, 2026102 ms
Aug 29, 2026101 ms
Sep 5, 2026102 ms
Sep 12, 2026102 ms
Sep 19, 2026102 ms
Sep 26, 2026102 ms
Oct 3, 2026102 ms
Oct 10, 2026102 ms
Oct 17, 2026102 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 habanos.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. habanos.com at 0.5 s0.5 s
  2. habanos.com at 1.1 s1.1 s
  3. habanos.com at 1.6 s1.6 s
  4. habanos.com at 2.2 s2.2 s
  5. habanos.com at 2.7 s2.7 s
  6. habanos.com at 3.2 s3.2 s
  7. habanos.com at 3.8 s3.8 s
  8. habanos.com at 4.3 s4.3 s

Speed

10 to fix33
  • Use efficient cache lifetimes

    5.5 s · 5.0 MB

    105 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).

  • Render-blocking requests

    5.3 s

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

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 5.8 s

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

  • Improve image delivery

    550 ms · 854 KiB

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

  • Reduce unused JavaScript

    640 ms · 678 KiB

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

  • Reduce unused CSS

    750 ms · 122 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Maps and others), adding 873 KiB and 600 ms of main-thread time.

  • Google Tag Manager adds 280 ms

    280 ms

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

  • Google CDN adds 172 ms

    172 ms

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

  • 9 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    8 KiB

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 31 ms

    31 ms

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

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 LCP: 6.0 s

    6.0 s

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

  • Real-user FCP: 5.0 s

    5.0 s

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

  • Real-user TTFB: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This Site Displays Content Related To Tobacco. Please Confi…”. Most of its time is element render delay (3.9 s).

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Time to Interactive: 16.8 s

    16.8 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Total Blocking Time: 538 ms

    538 ms

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

  • Cumulative Layout Shift: 0.189

    0.189

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

2 checks passed
  • Real-user INP: 104 ms

    104 ms

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

Images and page weight

3 to fix40
  • Page weight: 6.0 MB in 132 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 132 requests on a phone: images 4.0 MB (20), scripts 1.1 MB (47) and fonts 636 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    594 KiB

    4 images are downloaded at several times the size a phone draws them, for example hoyo_de_monterrey.png at 893 px wide, shown at 108 px. Resized copies would save about 594 KiB.

  • 7 images in older formats

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

    1.70 g

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

7 to fixGoogle 7489
  • Orphan list items

    Some list items are not inside a list.

  • 3 text elements with low contrast

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

  • Malformed lists

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

  • 7 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 33 links without text

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8571
  • No meta description

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

  • Title is short (29 characters)

    Your title is only 29 characters: “Habanos, S.A. – Official site”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Habanos, S.A. kicks off the “Cohiba Year” with th…”, “Habanos, S.A. has unveiled the Montecristo Fragat…” and “Third Habanos Sunset Party: Bring & Share Edition…”). One clear main headline is easier for people and search engines.

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

  • 117 internal links, 28 external

    The homepage links to 117 pages on habanos.com and 28 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.habanos.com/en/.

  • 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.habanos.com/wp-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.habanos.com/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 (504 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.habanos.com/en and / all use the title “Habanos, S.A. – Official site”. 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.habanos.com/en/unique-since-1492, https://www.habanos.com/en/the-world-of-the-habano, https://www.habanos.com/en/d-o-p-2, https://www.habanos.com/en/buy-smoke, https://www.habanos.com/en/the-habanos-brands-academia and https://www.habanos.com/en/vitolarios and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.habanos.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages slow to respond

    https://www.habanos.com/en/unique-since-1492, https://www.habanos.com/en/the-world-of-the-habano, https://www.habanos.com/en/d-o-p-2, https://www.habanos.com/en/buy-smoke, https://www.habanos.com/en/the-habanos-brands-academia and https://www.habanos.com/en/retail-concept and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 2 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    105 of 109 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 social proof

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

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

    The homepage carries about 502 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Where To Buy – Smoke”, “Contact” and “Where to Buy – Smoke”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 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.

  • 18 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

Company

Founded
1996

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on habanos.com, including 22 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