Programmable

Website review, no card needed

zales.com logo

zales.com website review

Visit site (opens in a new tab)Reviewed 12 October 202618 issues · 50 checks

This review found 18 issues worth fixing on zales.com, 7 of them high impact, across 50 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
5.0 s2.9 sApr 18Oct 34.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20263.2 s
Apr 25, 20263.1 s
May 2, 20263.2 s
May 9, 20263.4 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.7 s
Jul 11, 20263.9 s
Jul 18, 20264.1 s
Jul 25, 20264.2 s
Aug 1, 20264.3 s
Aug 8, 20264.2 s
Aug 15, 20264.3 s
Aug 22, 20264.5 s
Aug 29, 20264.6 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.4 s
Oct 3, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
216 ms170 msApr 18Oct 3197 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026178 ms
Apr 25, 2026176 ms
May 2, 2026175 ms
May 9, 2026179 ms
May 16, 2026179 ms
May 23, 2026179 ms
May 30, 2026180 ms
Jun 6, 2026180 ms
Jun 13, 2026183 ms
Jun 20, 2026184 ms
Jun 27, 2026184 ms
Jul 4, 2026186 ms
Jul 11, 2026186 ms
Jul 18, 2026187 ms
Jul 25, 2026194 ms
Aug 1, 2026196 ms
Aug 8, 2026203 ms
Aug 15, 2026206 ms
Aug 22, 2026211 ms
Aug 29, 2026211 ms
Sep 5, 2026211 ms
Sep 12, 2026210 ms
Sep 19, 2026210 ms
Sep 26, 2026205 ms
Oct 3, 2026197 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

www.zales.com (opens in a new tab)

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

6 to fix33

  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.36

    0.36

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

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

    +34%

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

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

    +14%

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

1 checks passed

  • Real-user INP: 190 ms

    190 ms

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

Images and page weight

100

  • About 0.1 g of CO₂ per visit

    0.14 g

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

1 checks passed

  • Page weight: 505 KiB

    505 KiB

    Your homepage downloads 505 KiB on a phone, 1 KiB of it images (0%). That is a lean page.

Accessibility

2 to fix88

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 checks passed

  • Every image has alt text

    All 90 images in the HTML carry an alt attribute.

  • 5 automated accessibility rules passed

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

SEO

3 to fix86

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 264 internal links, 13 external

    The homepage links to 264 pages on zales.com and 13 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “40% OFF*”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Zales | Your Online and Local Jewelry Store”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.zales.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 33 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65

  • 10 linked pages are broken

    Your homepage links to /sale-jewelry/c/011102101, /new-arrival-engagement/c/0111020557, /rings/new-arrival-rings/c/0111022013, /necklaces/new-arrival-necklaces/c/0111022015, /earrings/new-arrival-earrings/c/0111022014 and /bracelets/new-arrival-bracelets/c/0111022016 and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages without a meta description

    /store-finder, /customer-service, /book-appointment and /new have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    /book-appointment has 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 173 found) and read each the way a search engine does.

4 checks passed

  • 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 5 pages that loaded have a <title>.

Best practices

100
2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58

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

  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 926 words of visible text.

2 checks passed

  • 23 calls to action

    The homepage has 23 calls to action, for example “*Exclusions apply”, “Book an Appointment” and “Shop All”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 14 cookies set on arrival

    14

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

  • 2 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Angular

Company

Founded
1924
Headquarters
Irving

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on zales.com, including 6 speed issues, 3 SEO issues and 4 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