Website review, no card needed

starlingjewelry.com logo

starlingjewelry.com website review

Visit site (opens in a new tab)Reviewed 12 November 202638 issues · 84 checks

This review found 38 issues worth fixing on starlingjewelry.com, 8 of them high impact, across 84 checks. The most urgent: fails Core Web Vitals for real visitors. 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.7 s2.4 sMay 23Nov 73.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.3 s
Aug 1, 20263.2 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Nov 7, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
179 ms102 msMay 23Nov 7170 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026128 ms
May 30, 2026123 ms
Jun 6, 2026131 ms
Jun 13, 2026138 ms
Jun 20, 2026135 ms
Jun 27, 2026142 ms
Jul 4, 2026133 ms
Jul 11, 2026131 ms
Jul 18, 2026132 ms
Jul 25, 2026129 ms
Aug 1, 2026126 ms
Aug 8, 2026127 ms
Aug 15, 2026128 ms
Aug 22, 2026128 ms
Aug 29, 2026123 ms
Sep 5, 2026120 ms
Sep 12, 2026117 ms
Sep 19, 2026111 ms
Sep 26, 2026120 ms
Oct 3, 2026122 ms
Oct 10, 2026128 ms
Oct 17, 2026147 ms
Oct 24, 2026154 ms
Oct 31, 2026162 ms
Nov 7, 2026170 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 starlingjewelry.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. starlingjewelry.com at 0.7 s0.7 s
  2. starlingjewelry.com at 1.3 s1.3 s
  3. starlingjewelry.com at 2.0 s2.0 s
  4. starlingjewelry.com at 2.7 s2.7 s
  5. starlingjewelry.com at 3.4 s3.4 s
  6. starlingjewelry.com at 4.0 s4.0 s
  7. starlingjewelry.com at 4.7 s4.7 s
  8. starlingjewelry.com at 5.4 s5.4 s

Speed

12 to fix77
  • Improve image delivery

    3.5 MB

    14 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (ContentSquare, Google Tag Manager and uploadly-cdn.com and others), adding 3.8 MB and 983 ms of main-thread time.

  • Reduce unused JavaScript

    1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    650 ms

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

  • Main-thread work: 3.3 s

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

  • cloudfront.net adds 50 ms

    50 ms

    cloudfront.net costs a phone 50 ms of main-thread work and 1.6 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.

  • Google Tag Manager adds 176 ms

    176 ms

    Google Tag Manager costs a phone 176 ms of main-thread work and 312 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.

  • monkcommerce.app adds 133 ms

    133 ms

    monkcommerce.app costs a phone 133 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.

  • 1,747 HTML elements

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

  • Klaviyo adds 127 ms

    127 ms

    Klaviyo costs a phone 127 ms of main-thread work and 389 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.

  • Shopify adds 69 ms

    69 ms

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

  • Legacy JavaScript

    150 ms · 57 KiB

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

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    104 KiB

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

  • Reduce unused CSS

    31 KiB

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

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

    7 ms

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

Core Web Vitals

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

  • Time to Interactive: 26.9 s

    26.9 s

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

  • Speed Index: 10.4 s

    10.4 s

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

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

    +32%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

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

  • 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 3.2 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 182 ms

    182 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Total Blocking Time: 159 ms

    159 ms

    Scripts block the page for only 159 ms while loading. Good is under 200 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.015

    0.015

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

Images and page weight

4 to fix25
  • Page weight: 8.1 MB in 308 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 308 requests on a phone: images 4.5 MB (45), scripts 2.5 MB (120) and other files 736 KiB (109). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    1.7 MB

    9 images are downloaded at several times the size a phone draws them, for example Starling020262026-6245.jpg at 3,704 px wide, shown at 390 px. Resized copies would save about 1.7 MB.

  • 1 image over 500 KB

    Starling020262026-6245.jpg weighs 841 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Frame_6_0e49e781-8653-404a-89fc-b6aeeed32c54.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 2.3 g of CO₂ per visit

    2.29 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9695
  • 8 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • Headings skip levels

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

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

SEO

2 to fixGoogle 10090
  • Meta description is short (63 characters)

    Your meta description is only 63 characters: “Fine jewelry moved by light and color. Made to be — ever yours.”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 238 internal links, 3 external

    The homepage links to 238 pages on starlingjewelry.com and 3 external pages.

6 checks passed
  • Title: 45 characters

    Your title is a healthy 45 characters: “Starling Jewelry - Fine Jewelry, Bespoke Gems”.

  • Canonical URL set

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

  • Structured data in place

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

  • llms.txt published

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

Other pages

3 to fix88
  • 1 page without a meta description

    https://www.starlingjewelry.com/pages/heirloom-revival-inquiry has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.starlingjewelry.com/pages/studio-appointments, https://www.starlingjewelry.com/pages/bespoke, https://www.starlingjewelry.com/collections/bespoke-archive, https://www.starlingjewelry.com/pages/finished-bespoke-gems and https://www.starlingjewelry.com/blogs/heirloom-projects use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.starlingjewelry.com/pages/studio-appointments, https://www.starlingjewelry.com/pages/bespoke, https://www.starlingjewelry.com/collections/bespoke-gems, https://www.starlingjewelry.com/collections/bespoke-archive, https://www.starlingjewelry.com/pages/finished-bespoke-gems and https://www.starlingjewelry.com/pages/heirloom-revival-inquiry have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.starlingjewelry.com/collections/bespoke-archive has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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 7785
  • 6 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 1 JavaScript error while loading

    1 error was 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 fix79
  • Thin social proof

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

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

  • Only about 187 words

    The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “Shop Starling x Meredith Peck”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Shop All Engagement Rings”, “Shop Bespoke Gems” and “Shop All Rings”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.

  • 24 cookies set on arrival

    24

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

  • 42 other companies contacted

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

Apps your storefront loads

Uploadly File Upload · Klaviyo Email Marketing Sms · Uploadly Extension · Monk Free Gift With Purchase · Forms · azureedge.net · stamped.io · vercel.app · nfcube.com · cloudfront.net · Swym Wishlist Plus

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on starlingjewelry.com, including 19 speed issues, 2 SEO 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