Website review, no card needed

breakingheartsjewels.com logo

breakingheartsjewels.com website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 77 checks

This review found 33 issues worth fixing on breakingheartsjewels.com, 8 of them high impact, across 77 checks. The most urgent: page weight: 29.3 MB in 395 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

Full-page screenshot of breakingheartsjewels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. breakingheartsjewels.com at 1.0 s1.0 s
  2. breakingheartsjewels.com at 2.1 s2.1 s
  3. breakingheartsjewels.com at 3.1 s3.1 s
  4. breakingheartsjewels.com at 4.1 s4.1 s
  5. breakingheartsjewels.com at 5.2 s5.2 s
  6. breakingheartsjewels.com at 6.2 s6.2 s
  7. breakingheartsjewels.com at 7.3 s7.3 s
  8. breakingheartsjewels.com at 8.3 s8.3 s

Speed

9 to fix50
  • Main-thread work: 7.3 s

    A phone's processor spends 7.3 s on main-thread work while loading, 2.4 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 (Google CDN, Shopify and flodesk.com and others), adding 25.9 MB and 1.5 s of main-thread time.

  • Shopify adds 311 ms

    311 ms

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

  • Reduce unused JavaScript

    300 ms · 984 KiB

    About 984 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 849 ms

    849 ms

    Google CDN costs a phone 849 ms of main-thread work and 1.1 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.

  • Render-blocking requests

    850 ms

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

  • 2,080 HTML elements

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

  • flodesk.com adds 97 ms

    97 ms

    flodesk.com costs a phone 97 ms of main-thread work and 761 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

    192 KiB

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

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    46 KiB

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

  • Legacy JavaScript

    35 KiB

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

  • Use efficient cache lifetimes

    17 KiB

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

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix45
  • Time to Interactive: 24.1 s

    24.1 s

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

  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Cumulative Layout Shift: 0.203

    0.203

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

  • Total Blocking Time: 360 ms

    360 ms

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

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

1 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

2 to fix64
  • Page weight: 29.3 MB in 395 requests

    29.3 MB

    Your homepage downloads 29.3 MB in 395 requests on a phone: media 23.1 MB (3), scripts 1.9 MB (129) and images 1.9 MB (28). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Shopify_Banner_Untitled-14-Charm_Bar_-_Mobile.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).

  • About 8.3 g of CO₂ per visit

    8.32 g

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

5 to fixGoogle 10094
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious 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.

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

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

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

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 69 internal links, 12 external

    The homepage links to 69 pages on breakingheartsjewels.com and 12 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Permanent jewellery and memorial jewellery in Bolton, welded to fit at our St George's Road studio. Over 260 chains. Bo…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Permanent Jewellery Bolton | Breaking Hearts Jewels”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: JewelryStore, 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://breakingheartsjewels.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 (1,149 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix85
  • 9 pages without a meta description

    https://breakingheartsjewels.com/pages/memorial-jewellery, https://breakingheartsjewels.com/pages/groups-parties, https://breakingheartsjewels.com/collections/charm-bar, https://breakingheartsjewels.com/pages/book-an-event, https://breakingheartsjewels.com/pages/gallery and https://breakingheartsjewels.com/collections/%E2%9C%A8necklaces-%E2%9C%A8 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://breakingheartsjewels.com/collections/%E2%9C%A8necklaces-%E2%9C%A8, whose canonical is https://breakingheartsjewels.com/collections/%e2%9c%a8necklaces-%e2%9c%a8. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://breakingheartsjewels.com/collections/permanent-jewellery, https://breakingheartsjewels.com/pages/birthday-packages, https://breakingheartsjewels.com/pages/groups-parties, https://breakingheartsjewels.com/collections/charm-bar, https://breakingheartsjewels.com/pages/book-an-event and https://breakingheartsjewels.com/pages/gallery and 6 others 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 40 found) and read each the way a search engine does.

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

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

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Flickity is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 860 words of visible text.

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “BOOK US FOR AN EVENT”, “SHOP” and “CONTACT”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 1 customer or partner logo.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Meta Pixel and Pinterest Tag (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.

  • 8 cookies set on arrival

    8

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 breakingheartsjewels.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gsc Instagram Feed · Inbox · King Product Options · Bookeasy · Repocean Google Reviews

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on breakingheartsjewels.com, including 14 speed issues, 1 SEO issue and 5 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