Website review, no card needed

mybella.com logo

mybella.com website review

Visit site (opens in a new tab)Reviewed 5 November 202620 issues · 73 checks

This review found 20 issues worth fixing on mybella.com, 5 of them high impact, across 73 checks. The most urgent: render-blocking 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
2.3 s1.9 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20261.9 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
140 ms103 msMay 16Oct 31126 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026107 ms
May 23, 2026113 ms
May 30, 2026112 ms
Jun 6, 2026115 ms
Jun 13, 2026120 ms
Jun 20, 2026120 ms
Jun 27, 2026120 ms
Jul 4, 2026114 ms
Jul 11, 2026112 ms
Jul 18, 2026114 ms
Jul 25, 2026112 ms
Aug 1, 2026116 ms
Aug 8, 2026120 ms
Aug 15, 2026113 ms
Aug 22, 2026116 ms
Aug 29, 2026117 ms
Sep 5, 2026119 ms
Sep 12, 2026136 ms
Sep 19, 2026124 ms
Sep 26, 2026121 ms
Oct 3, 2026120 ms
Oct 10, 2026111 ms
Oct 17, 2026126 ms
Oct 24, 2026124 ms
Oct 31, 2026126 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 mybella.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix98
  • Render-blocking requests

    1.7 s

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

  • Use efficient cache lifetimes

    450 ms · 318 KiB

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

  • 2,567 HTML elements

    The page has 2,567 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 (termly.io, Shopify and Google CDN and others), adding 669 KiB and 84 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    45 KiB

    About 45 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    22 KiB

    About 22 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.

3 checks passed
  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • 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 fix67
  • 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: 3.2 s

    3.2 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 5 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

8 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • 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: 547 ms

    547 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We use essential cookies to make our site work. With your c…”.

  • Total Blocking Time: 21 ms

    21 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.31 g

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

4 checks passed
  • Page weight: 1.1 MB in 42 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 42 requests on a phone: scripts 785 KiB (24), images 175 KiB (5) and HTML 64 KiB (1). That is a lean page.

  • 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 9694
  • 2 tap targets too small

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

  • 4 images without alt text

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 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 9280
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (274 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("https://facebook.com/Bella Cosa Jewelers")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 668 internal links, 23 external

    The homepage links to 668 pages on mybella.com and 23 external pages.

5 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Jewelry Store in Willowbrook & Wilmette | Bella Cosa Jewelers”.

  • Canonical URL set

    The canonical URL is https://www.bellacosajewelers.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://www.bellacosajewelers.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.bellacosajewelers.com/pages/engagement-rings-in-chicago-il has 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 https://www.bellacosajewelers.com/collections/a-jaffe-engagement-rings, whose canonical is https://www.bellacosajewelers.com/collections/a-jaffe-engagement-rings-in-chicago. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 9687
  • 7 small tap targets

    7 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to construct 'Request': Failed to parse URL from //www.bellacosajewelers.com/cdn/shop/t/24/assets/worker-min.js?…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 378 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 52 calls to action

    The homepage has 52 calls to action, for example “Shop All Engagement Rings”, “Shop All Wedding Bands” and “Shop Diamonds”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • 8 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 mybella.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Powerful Form Builder · Klaviyo Email Marketing Sms · Region Restrictions · Product Filter Search · cloudfront.net · trafficmanager.net · nfcube.com · cart-bot.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

Framework
React
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Headquarters
Willowbrook

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on mybella.com, including 8 speed issues and 4 SEO issues. 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