yafeini.com website review

About 658 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, chatra.io and TikTok and others), adding 1.4 MB and 1.1 s of main-thread time.

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

About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

chatra.io costs a phone 289 ms of main-thread work and 313 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.

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

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

3 KiB could be saved by minifying JavaScript.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

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

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

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.

Your homepage downloads 2.8 MB in 209 requests on a phone: scripts 1.6 MB (56), other files 705 KiB (127) and images 343 KiB (13). Under 2 MB keeps phones on slow connections fast.

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

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

4 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is 77 characters, so Google will cut it off around 60: “Personalized Jewelry | Custom Jewelry | YAFEINI– Yafeini Personalized Jewelry”.

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

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

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

The homepage links to 56 pages on yafeini.com and 20 external pages.

Your homepage links to https://www.yafeini.com/pages/wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.yafeini.com/collections/name-necklaces-1, https://www.yafeini.com/collections/heart-name-necklaces, https://www.yafeini.com/collections/infinity-name-necklaces-1 and https://www.yafeini.com/collections/necklaces-creative-necklaces all use the title “Name Necklace — Carry Your Name | Yafeini Jewelry– Yafeini Personaliz…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.yafeini.com/collections/necklaces, https://www.yafeini.com/collections/urn, https://www.yafeini.com/collections/necklaces-disc-circle-necklaces, https://www.yafeini.com/collections/earrings, https://www.yafeini.com/collections/earrings-np and https://www.yafeini.com/collections/bracelet-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.yafeini.com/collections/heart-name-necklaces, https://www.yafeini.com/collections/infinity-name-necklaces-1 and https://www.yafeini.com/collections/necklaces-creative-necklaces use the same meta description. A description written for each page earns more clicks.

https://www.yafeini.com/collections/necklaces, https://www.yafeini.com/collections/urn, https://www.yafeini.com/collections/name-necklaces-1, https://www.yafeini.com/collections/necklaces-photo-necklaces, https://www.yafeini.com/collections/engravable-necklaces and https://www.yafeini.com/collections/bar-engraved-necklaces and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.yafeini.com/collections/necklaces, https://www.yafeini.com/collections/name-necklaces-1, https://www.yafeini.com/collections/necklaces-photo-necklaces, https://www.yafeini.com/collections/engravable-necklaces, https://www.yafeini.com/collections/bar-engraved-necklaces and https://www.yafeini.com/collections/heart-name-necklaces and 7 others took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343008427&Ver=2&mid=2226cbc8-edcc-4c45-9846-9b2a2fde20d4&bo=1&sid=9f2bb010dd2111f192427d07e2eeb5a6&vid=9f2bc0b0dd2111f18814b30552437061&vids=1&msclkid=N&pi=918639831&l.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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.

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