Website review, no card needed

alaninu.com logo

alaninu.com website review

Visit site (opens in a new tab)Reviewed 11 October 202643 issues · 88 checks

This review found 43 issues worth fixing on alaninu.com, 18 of them high impact, across 88 checks. The most urgent: page weight: 54.2 MB in 346 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
1.9 s1.2 sApr 18Oct 31.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.7 s
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
193 ms147 msApr 18Oct 3183 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026154 ms
Apr 25, 2026153 ms
May 2, 2026152 ms
May 9, 2026164 ms
May 16, 2026166 ms
May 23, 2026166 ms
May 30, 2026169 ms
Jun 6, 2026171 ms
Jun 13, 2026176 ms
Jun 20, 2026186 ms
Jun 27, 2026188 ms
Jul 4, 2026185 ms
Jul 11, 2026183 ms
Jul 18, 2026184 ms
Jul 25, 2026184 ms
Aug 1, 2026184 ms
Aug 8, 2026179 ms
Aug 15, 2026162 ms
Aug 22, 2026163 ms
Aug 29, 2026163 ms
Sep 5, 2026165 ms
Sep 12, 2026175 ms
Sep 19, 2026179 ms
Sep 26, 2026181 ms
Oct 3, 2026183 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 alaninu.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alaninu.com at 0.9 s0.9 s
  2. alaninu.com at 1.7 s1.7 s
  3. alaninu.com at 2.6 s2.6 s
  4. alaninu.com at 3.5 s3.5 s
  5. alaninu.com at 4.4 s4.4 s
  6. alaninu.com at 5.2 s5.2 s
  7. alaninu.com at 6.1 s6.1 s
  8. alaninu.com at 7.0 s7.0 s

Speed

13 to fix40
  • Reduce unused JavaScript

    3.1 s · 633 KiB

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

  • Improve image delivery

    2.5 s · 846 KiB

    15 images could be 846 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 308 KiB

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

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 6.4 s

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

  • 3,448 HTML elements

    The page has 3,448 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 (Shopify, rebuyengine.com and Optanon and others), adding 2.6 MB and 731 ms of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    450 ms · 92 KiB

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

  • Legacy JavaScript

    450 ms · 76 KiB

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

  • Minify JavaScript

    450 ms · 37 KiB

    37 KiB could be saved by minifying JavaScript.

  • Shopify adds 241 ms

    241 ms

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

  • rebuyengine.com adds 150 ms

    150 ms

    rebuyengine.com costs a phone 150 ms of main-thread work and 747 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.

  • 8 long tasks on the main thread

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

  • 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

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A can of Alani Nu Witch's Brew Energy topped with a caramel…”.

  • Time to Interactive: 25.7 s

    25.7 s

    The page becomes fully interactive after 25.7 s. Good is under 3.8 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: 10.3 s

    10.3 s

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

  • Real-user INP: 262 ms

    262 ms

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

  • Real-user CLS: 0.18

    0.18

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

  • Cumulative Layout Shift: 0.217

    0.217

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

  • Total Blocking Time: 259 ms

    259 ms

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

  • 2 images without width and height

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

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

    +19%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 154 ms to 183 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-03, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 385 ms

    385 ms

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

Images and page weight

2 to fix69
  • Page weight: 54.2 MB in 346 requests

    54.2 MB

    Your homepage downloads 54.2 MB in 346 requests on a phone: media 48.3 MB (13), images 2.6 MB (46) and scripts 1.9 MB (128). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Stretch_AN-WBR-Mini-Text_V2.png 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).

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 15.4 g of CO₂ per visit

    15.36 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8990
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 13 links without text

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 76 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

Google 100100
  • 123 internal links, 14 external

    The homepage links to 123 pages on alaninu.com and 14 external pages.

8 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Sip into a sweet escape with Alani Nu. Discover a brighter way to fuel your day with energy drinks and wellness favorit…”.

  • One H1 headline

    Your main headline reads: “Alani Nu”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Alani Nu | Big Flavor. Bright Energy.”.

  • Canonical URL set

    The canonical URL is https://www.alaninu.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

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

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

AI search readiness

1 to fix88
  • 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.

3 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 (631 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.alaninu.com/llms.txt (4 KiB, 5 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.alaninu.com/pages/find-witchs-brew-near-you-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.alaninu.com/pages/about-alani-nu and https://www.alaninu.com/pages/ambassadors 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 38 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

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://www.alaninu.com/.

  • 26 small tap targets

    26 of 84 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 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 780 words of copy

    The homepage carries about 780 words of visible text.

3 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “shop”, “shop all” and “contact us”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 39 testimonial or review blocks and a star rating.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies (measured from a US location before any click).

  • 49 other companies contacted

    Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 alaninu.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 alaninu.com, including 23 speed 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