memorialize.art website review

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and Shopify and others), adding 4.0 MB and 714 ms of main-thread time.

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

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

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

Shopify costs a phone 100 ms of main-thread work and 2.6 MB 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.

alia-prod.com costs a phone 260 ms of main-thread work and 685 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.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 images could be 139 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.

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

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

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

About 12 KiB of CSS is downloaded but never applied on this page.

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

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 17.2 s. Good is under 3.8 s.

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 element shown below.

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

Real visitors wait 818 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 13.8 MB in 231 requests on a phone: media 10.5 MB (5), scripts 1.4 MB (139) and images 775 KiB (19). Under 2 MB keeps phones on slow connections fast.

2 images (113 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.

3 images further down the page (69 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

6 images have no alt text, which hurts accessibility and image search.

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

Structured data found (Product) but with 3 problems, for example “Product: missing name”.

The homepage links to 38 pages on memorialize.art and 5 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://memorialize.art/products/personalized-watercolor-memorial-portrait and https://memorialize.art/products/watercolor-memorial-portrait-top all use the title “Personalized Watercolor Portrait | Custom Memorial Art”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://memorialize.art/collections/best-sellers-today has no meta description, so Google writes the search snippet from whatever text it finds.

https://memorialize.art/products/personalized-watercolor-memorial-portrait and https://memorialize.art/products/watercolor-memorial-portrait-top use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://memorialize.art/collections/best-sellers-today/products/watercolor-house-portrait, whose canonical is https://memorialize.art/products/watercolor-house-portrait. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://memorialize.art/collections/best-sellers-today, https://memorialize.art/pages/reviews, https://memorialize.art/pages/about-us, https://memorialize.art/pages/faqs, https://memorialize.art/products/watercolor-memorial-portrait-top and https://memorialize.art/products/pet-memorial-portrait and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

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

The homepage carries about 735 words of visible text.

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