Website review, no card needed

jajatequila.com logo

jajatequila.com website review

Visit site (opens in a new tab)Reviewed 22 October 202643 issues · 75 checks

This review found 43 issues worth fixing on jajatequila.com, 14 of them high impact, across 75 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

Full-page screenshot of jajatequila.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jajatequila.com at 0.6 s0.6 s
  2. jajatequila.com at 1.2 s1.2 s
  3. jajatequila.com at 1.8 s1.8 s
  4. jajatequila.com at 2.3 s2.3 s
  5. jajatequila.com at 2.9 s2.9 s
  6. jajatequila.com at 3.5 s3.5 s
  7. jajatequila.com at 4.1 s4.1 s
  8. jajatequila.com at 4.7 s4.7 s

Speed

7 to fix55
  • Reduce unused JavaScript

    1.5 s · 266 KiB

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

  • Use efficient cache lifetimes

    1.0 s · 704 KiB

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

  • Improve image delivery

    550 ms · 821 KiB

    21 images could be 821 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.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Mailchimp and Amazon Web Services and others), adding 1.8 MB and 387 ms of main-thread time.

  • Mailchimp adds 145 ms

    145 ms

    Mailchimp costs a phone 145 ms of main-thread work and 728 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.

  • sanity.io adds 0 ms

    0 ms

    sanity.io costs a phone 0 ms of main-thread work and 631 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.

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Font display

    150 ms

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 950 ms of it running JavaScript. That is comfortably low.

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

5 to fix63
  • Largest Contentful Paint: 15.2 s

    15.2 s

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

  • Time to Interactive: 15.6 s

    15.6 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 198 ms

    198 ms

    Scripts block the page for only 198 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix40
  • 1 image over 500 KB

    d67942d282ba7f2211f8ba6356a2eda107342bd4-2880x2172.jpg weighs 632 KiB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    637 KiB

    4 images are downloaded at several times the size a phone draws them, for example d67942d282ba7f2211f8ba6356a2eda107342bd4-2880x2172.jpg at 2,880 px wide, shown at 390 px. Resized copies would save about 637 KiB.

  • Page weight: 3.4 MB in 73 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 73 requests on a phone: images 2.5 MB (32), scripts 600 KiB (19) and fonts 233 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (632 KiB) is 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.0 g of CO₂ per visit

    0.96 g

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

9 to fixGoogle 7585
  • 1 button without a name

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

  • 4 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

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

  • 1 image without alt text

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

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

  • 4 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

7 to fixGoogle 8372
  • No structured data

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

  • Meta description is short (35 characters)

    Your meta description is only 35 characters: “JAJA Tequila | Made For Magic Hour.”. 70 to 160 characters is enough to sell the click.

  • 32 H1 headlines

    There are 32 <h1> headlines (“Life's Too Short For Bad Choices.”, “The most award winning tequila in its class, the …” and “Meet Our Award Winners:”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at jajatequila.com/robots.txt, the first file search crawlers ask for.

  • Only 4 internal links

    The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

2 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “JAJA Tequila 100% Agave Azul | Made For Magic Hour.”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix81
  • 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://jajatequila.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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (459 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 4 pages share a title

    /, https://jajatequila.com/stockists, https://jajatequila.com/merch and https://jajatequila.com/terms-and-conditions all use the title “JAJA Tequila 100% Agave Azul | Made For Magic Hour.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://jajatequila.com/stockists, https://jajatequila.com/merch and https://jajatequila.com/terms-and-conditions use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://jajatequila.com/stockists and https://jajatequila.com/merch have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://jajatequila.com/stockists and https://jajatequila.com/merch have 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.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 2 small tap targets

    2 of 10 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 “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-061523.css' from origin 'https://jajate…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 412 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Subscribe”.

  • 1 short form

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

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.

  • 3 cookies set on arrival

    3

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 jajatequila.com, 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 43 issues on jajatequila.com, including 12 speed issues, 7 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