kay.com website review

Not measured in this review.

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

  0.33

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

• Real-user LCP: 3.5 s

  3.5 s

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

• Real-user FCP: 2.9 s

  2.9 s

  Real visitors see the first content after 2.9 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.

• Tap response (INP) held steady for real visitors

  +1%

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

• Largest content (LCP) held steady for real visitors

  +9%

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

• About 0.2 g of CO₂ per visit

  0.16 g

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

• No main landmark

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

  Elements (1)

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

  Elements (1)

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

• 480 internal links, 17 external

  The homepage links to 480 pages on kay.com and 17 external pages.

• 9 linked pages are broken

  Your homepage links to /l/new-arrivals/womens-new-arrivals, /l/new-arrivals/mens-new-arrivals, /l/new-arrivals/lab-grown-diamond, /rings/new-arrivals-rings/c/9000000074, /new-arrivals-engagement-and-wedding/c/9000001682 and /necklaces/new-arrivals-necklaces/c/9000000122 and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  Elements (8)

• 1 linked page hidden from search

  /online-custom-engagement-rings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 4 pages without a meta description

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

  Elements (4)

• 1 page without an H1

  /book-appointment has no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page slow to respond

  /customer-service took over 3 s to send its HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 165 found) and read each the way a search engine does.

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  View source

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

• 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 2,043 words of copy

  The homepage carries about 2,043 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

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