nayhera.com website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

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

8 third-party services load with your homepage (iubenda, Shopify and Google Tag Manager and others), adding 1.0 MB and 1.2 s of main-thread time.

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

iubenda costs a phone 704 ms of main-thread work and 125 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.

4 images could be 203 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Shopify costs a phone 324 ms of main-thread work and 688 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 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

13 KiB could be saved by minifying JavaScript.

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

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.

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frau trägt modernen Diamantschmuck von NAYHERA mit Verlobun…”.

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

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 3.1 MB in 359 requests on a phone: other files 1.2 MB (210), scripts 1.1 MB (109) and images 597 KiB (11). Under 2 MB keeps phones on slow connections fast.

20240407_Amano-Jewels_1138.jpg 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).

3 images (210 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.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 86 pages on nayhera.com and 0 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.

The HTML your server sends has 321 of the 892 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://nayhera.com/pages/uber-uns and https://nayhera.com/pages/nachhaltigkeit use the same meta description. A description written for each page earns more clicks.

https://nayhera.com/collections, https://nayhera.com/collections/ringe, https://nayhera.com/collections/verlobungsringe, https://nayhera.com/collections/besondere-verlobungsringe, https://nayhera.com/pages/uber-uns and https://nayhera.com/pages/laborgewachsene-diamanten and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

The homepage carries about 892 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).

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