crystaltreecr.com website review

120 images could be 11.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

3 third-party services load with your homepage (Shopify, shop.app and securification.ai), adding 569 KiB and 520 ms of main-thread time.

Shopify costs a phone 520 ms of main-thread work and 566 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 61 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.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Temporada Studio Ghibli”.

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

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

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

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

Your homepage downloads 14.5 MB in 326 requests on a phone: images 12.7 MB (120), other files 796 KiB (84) and scripts 735 KiB (109). Under 2 MB keeps phones on slow connections fast.

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

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

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

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. (27 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 12 characters: “Crystal Tree”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 124 pages on crystaltreecr.com and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://crystaltreecr.com/en/collections/ropa, https://crystaltreecr.com/en/collections/prototipo-1-0, https://crystaltreecr.com/en/collections/gorras, https://crystaltreecr.com/en/collections/personalizado, https://crystaltreecr.com/en/collections/hoodie-sueter and https://crystaltreecr.com/en/blogs/info and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://crystaltreecr.com/products/botella-shift-violet-evergarden, whose canonical is https://crystaltreecr.com/en/products/botella-shift-violet-evergarden. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://crystaltreecr.com/en/pages/contactanos, https://crystaltreecr.com/en/collections and https://crystaltreecr.com/en/products/collector-pack-studio-ghibli have no <h1> headline, so visitors and search engines get no clear main topic.

https://crystaltreecr.com/en/collections has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Error loading currency rates: TypeError: Failed to fetch”.

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

Social proof on the homepage: 1 trust badge. 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.

The homepage has only about 47 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.

Opening the homepage sets 5 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.