gurhan.com website review

6 images could be 493 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Google Tag Manager and others), adding 2.1 MB and 669 ms of main-thread time.

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

Klaviyo costs a phone 180 ms of main-thread work and 619 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 costs a phone 148 ms of main-thread work and 355 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.

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

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

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

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

6 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.7 MB in 254 requests on a phone: media 2.6 MB (1), scripts 1.7 MB (122) and images 1.4 MB (21). Under 2 MB keeps phones on slow connections fast.

4 images (560 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

4 images are downloaded at several times the size a phone draws them, for example necklaces_8dc0b544-cebf-4936-a979-4c0d1760b46c.webp at 800 px wide, shown at 183 px. Resized copies would save about 296 KiB.

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 257 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 167 pages on gurhan.com and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://gurhan.com/pages/tourmaline-designs-in-24k-gold and https://gurhan.com/pages/24k-gold-designs have no meta description, so Google writes the search snippet from whatever text it finds.

https://gurhan.com/pages/opal and https://gurhan.com/pages/featured-collections have no <h1> headline, so visitors and search engines get no clear main topic.

https://gurhan.com/collections/all-bracelets, https://gurhan.com/collections/unique-pendant-necklaces, https://gurhan.com/collections/24k-gold-handcrafted-pendants-charms, https://gurhan.com/collections/all-products, https://gurhan.com/collections/birthstone-gifts-may-emeralds and https://gurhan.com/collections/birthstone-gifts-july-ruby and 5 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=283007272&tm=gtm002&Ver=2&mid=88a2c1e3-df5e-4e54-bea8-0a077010b799&bo=1&sid=4592b090dcc511f18378b7eccaa87391&vid=4592bb10dcc511f18e10ef0879af1c59&vids=1&msclkid=N&pi=9.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

Chrome logged issues while loading the page (“Cookie”).

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

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.

The homepage shows no opening hours. If customers visit or call, show when.

The homepage carries about 320 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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 22 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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.