ornamentshop.com website review

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

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (reamaze.com, rebuyengine.com and omnisnippet1.com and others), adding 1.5 MB and 821 ms of main-thread time.

About 130 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.

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

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

About 468 KiB of JavaScript is downloaded but never used on this page.

The page has 2,559 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

rebuyengine.com costs a phone 187 ms of main-thread work and 298 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 59 ms of main-thread work and 617 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.

13 KiB could be saved by minifying CSS.

Polyfills for old browsers add 18 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.

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.

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

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

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

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.5 s).

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

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

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

Your homepage downloads 4.2 MB in 277 requests on a phone: other files 1.4 MB (133), scripts 1.2 MB (86) and images 1.1 MB (37). Under 2 MB keeps phones on slow connections fast.

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

37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Structured data found (BreadcrumbList, ImageObject, OnlineStore and Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//ornamentshop.com/cdn/shop/files/ORN_800X800_1.png?v=1…”.

The homepage links to 243 pages on ornamentshop.com and 9 external pages.

https://ornamentshop.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://ornamentshop.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://ornamentshop.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://ornamentshop.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://ornamentshop.com/cdn/shop/files/desktop_hero_-6.png?pad_color=fff&v=1794225422&width=165.

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

Requests the notification permission on page load.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,185 words of visible text.

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 26 cookies, 3 of them by other companies (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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.