Website review, no card needed

divinenoni.com logo

divinenoni.com website review

Visit site (opens in a new tab)Reviewed 25 October 202643 issues · 83 checks

This review found 43 issues worth fixing on divinenoni.com, 20 of them high impact, across 83 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
3.8 s2.8 sMay 2Oct 173.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.0 s
May 23, 20263.1 s
May 30, 20262.9 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.7 s
Aug 15, 20263.5 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
209 ms168 msMay 2Oct 17187 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026190 ms
May 9, 2026186 ms
Jun 13, 2026195 ms
Jun 20, 2026204 ms
Jun 27, 2026197 ms
Jul 4, 2026197 ms
Jul 11, 2026192 ms
Jul 18, 2026185 ms
Jul 25, 2026182 ms
Aug 1, 2026177 ms
Aug 8, 2026173 ms
Aug 15, 2026177 ms
Aug 22, 2026178 ms
Aug 29, 2026185 ms
Sep 5, 2026186 ms
Sep 12, 2026186 ms
Sep 19, 2026201 ms
Sep 26, 2026194 ms
Oct 3, 2026187 ms
Oct 10, 2026173 ms
Oct 17, 2026187 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 divinenoni.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. divinenoni.com at 1.2 s1.2 s
  2. divinenoni.com at 2.4 s2.4 s
  3. divinenoni.com at 3.6 s3.6 s
  4. divinenoni.com at 4.8 s4.8 s
  5. divinenoni.com at 6.0 s6.0 s
  6. divinenoni.com at 7.2 s7.2 s
  7. divinenoni.com at 8.4 s8.4 s
  8. divinenoni.com at 9.6 s9.6 s

Speed

11 to fix34
  • Reduce unused JavaScript

    31.3 s · 3.8 MB

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

  • YouTube adds 3.1 s

    3.1 s

    YouTube costs a phone 3.1 s of main-thread work and 6.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    2.5 s · 245 KiB

    About 245 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 9.5 s

    A phone's processor spends 9.5 s on main-thread work while loading, 4.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 (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 8.1 MB and 3.5 s of main-thread time.

  • Improve image delivery

    698 KiB

    29 images could be 698 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 261 ms

    261 ms

    Google Tag Manager costs a phone 261 ms of main-thread work and 441 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,587 HTML elements

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

  • Shopify adds 26 ms

    26 ms

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 10 KiB

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

  • Font display

    50 ms

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

  • 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

11 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: 5.0 s

    5.0 s

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

  • First Contentful Paint: 34.1 s

    34.1 s

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

  • Largest Contentful Paint: 50.8 s

    50.8 s

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

  • Speed Index: 34.1 s

    34.1 s

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

  • Time to Interactive: 56.9 s

    56.9 s

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

  • Total Blocking Time: 926 ms

    926 ms

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

  • Real-user INP: 217 ms

    217 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 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.

  • 29 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 10.7 MB in 331 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 331 requests on a phone: scripts 6.8 MB (90), images 1.6 MB (72) and other files 760 KiB (124). Under 2 MB keeps phones on slow connections fast.

  • 13 images below the first screen load straight away

    13 images further down the page (778 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.05 g

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

8 to fixGoogle 8288
  • Hidden but focusable

    42 elements hidden from screen readers can still receive keyboard focus.

  • 28 text elements with low contrast

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

  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    7 frames have no title, so screen-reader users cannot tell what they contain.

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

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 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: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Your Daily Wellness Essentials – The Wellness Divine Herbs Private Limited”.

  • 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 long (249 characters)

    Your meta description is 249 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 79 internal links, 8 external

    The homepage links to 79 pages on divinenoni.com and 8 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://divinenoni.com/.

  • 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://divinenoni.com/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.

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

4 to fixGoogle 5074
  • 6 broken images

    6 images failed to load on a phone, for example https://divinenoni.com/Liquid%20error%20(snippets/blog-grid-4%20line%2013):%20include%20usage%20is%20not%20allowed%20in%20this%20context.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

  • 2 low-resolution images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 22 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,298 words of copy

    The homepage carries about 1,298 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP OUR PRODUCTS”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop by Category”, “Shop All” and “Register”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and 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 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.

  • 7 cookies set on arrival

    7

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

  • 19 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on divinenoni.com, including 22 speed issues, 4 SEO issues and 1 conversion gap. 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