Programmable

Website review, no card needed

discoverbrillia.com logo

discoverbrillia.com website review

Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 83 checks

This review found 28 issues worth fixing on discoverbrillia.com, 8 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

Site score

85B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
705 ms503 msMay 23Nov 7638 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026612 ms
May 30, 2026646 ms
Jun 6, 2026580 ms
Jun 13, 2026590 ms
Jun 20, 2026579 ms
Jun 27, 2026564 ms
Jul 4, 2026590 ms
Jul 11, 2026543 ms
Jul 18, 2026555 ms
Jul 25, 2026537 ms
Aug 1, 2026536 ms
Aug 8, 2026645 ms
Aug 15, 2026612 ms
Aug 22, 2026655 ms
Aug 29, 2026682 ms
Sep 5, 2026611 ms
Sep 12, 2026566 ms
Sep 19, 2026528 ms
Sep 26, 2026526 ms
Oct 3, 2026582 ms
Oct 10, 2026619 ms
Oct 17, 2026616 ms
Oct 24, 2026646 ms
Oct 31, 2026620 ms
Nov 7, 2026638 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms78 msMay 23Nov 787 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202684 ms
May 30, 202687 ms
Jun 6, 202683 ms
Jun 13, 202685 ms
Jun 20, 202684 ms
Jun 27, 202682 ms
Jul 4, 202684 ms
Jul 11, 202681 ms
Jul 18, 202684 ms
Jul 25, 202685 ms
Aug 1, 202683 ms
Aug 8, 202686 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202680 ms
Sep 5, 202681 ms
Sep 12, 202683 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202683 ms
Oct 24, 202686 ms
Oct 31, 202687 ms
Nov 7, 202687 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

discoverbrillia.com (opens in a new tab)
Full-page screenshot of discoverbrillia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. discoverbrillia.com at 0.4 s0.4 s
  2. discoverbrillia.com at 0.8 s0.8 s
  3. discoverbrillia.com at 1.1 s1.1 s
  4. discoverbrillia.com at 1.5 s1.5 s
  5. discoverbrillia.com at 1.9 s1.9 s
  6. discoverbrillia.com at 2.3 s2.3 s
  7. discoverbrillia.com at 2.6 s2.6 s
  8. discoverbrillia.com at 3.0 s3.0 s

Speed

8 to fix63

  • Reduce unused JavaScript

    2.2 s · 515 KiB

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

  • Use efficient cache lifetimes

    1.3 s · 347 KiB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. 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 (Yotpo, Google Tag Manager and Shopify and others), adding 2.7 MB and 584 ms of main-thread time.

  • Shopify adds 103 ms

    103 ms

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

  • 2,555 HTML elements

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

  • Main-thread work: 2.0 s

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

  • Yotpo adds 146 ms

    146 ms

    Yotpo costs a phone 146 ms of main-thread work and 325 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.

  • Improve image delivery

    201 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    35 KiB

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

  • Legacy JavaScript

    26 KiB

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • 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

5 to fix100

  • Largest Contentful Paint: 13.3 s

    13.3 s

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 1 image without width and height

    1 image 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-11-07, real Chrome visitors' tap response (inp) went from 84 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

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

8 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: 0.6 s

    0.6 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 0.5 s

    0.5 s

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

  • Real-user TTFB: 152 ms

    152 ms

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

  • Total Blocking Time: 187 ms

    187 ms

    Scripts block the page for only 187 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

1 to fix85

  • Page weight: 4.0 MB in 248 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 248 requests on a phone: media 1.5 MB (1), scripts 1.3 MB (94) and other files 702 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.13 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

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

  • 12 text elements with low contrast

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

  • 3 images without alt text

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

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

  • 19 links without text

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

1 checks passed

  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 9281

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Brillia - Homeopathic Anxiety & Stress Medication – Non Prescription M”.

  • Structured data has 1 problem

    Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("discoverbrillia.com")”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 126 internal links, 6 external

    The homepage links to 126 pages on discoverbrillia.com and 6 external pages.

4 checks passed

  • Meta description: 136 characters

    Your meta description is 136 characters: “Discover Brillia, a holistic anxiety medication program that helps reduce anxiety in children and adults and improves f…”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

2 to fix90

  • 4 pages without a meta description

    https://discoverbrillia.com/pages/brillia-for-children-ages-5-6, https://discoverbrillia.com/pages/brillia-for-children-ages-7-8, https://discoverbrillia.com/pages/brillia-for-children-ages-9-10 and https://discoverbrillia.com/pages/brillia-for-teens-ages-13-17 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://discoverbrillia.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://discoverbrillia.com/pages/brillia-for-adults, https://discoverbrillia.com/pages/hyperactivity, https://discoverbrillia.com/pages/anxiety, https://discoverbrillia.com/pages/impulsive-behavior and https://discoverbrillia.com/pages/restlessness took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 9678

  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17236288&Ver=2&mid=f2ea3dfb-6a02-466e-82db-e845d3f5b4b4&bo=1&sid=4cdb88b0de3c11f1b93697325185beb4&vid=4cdb7ac0de3c11f1b279b314ff15c00f&vids=1&msclkid=N&pi=918639831&lg.

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

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,407 words of copy

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

8 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY NOW” and “SHOP NOW”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “BUY BRILLIA”, “Shop By” and “Contact Us”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 discoverbrillia.com, 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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Seo Manager Venntov · Sc Easy Redirects · Hs Slide Cart Drawer · yotpo.com · cloudfront.net

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

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Phoenix

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on discoverbrillia.com, including 13 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