planetabrick.cl website review

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

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

29 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

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

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

Shopify costs a phone 167 ms of main-thread work and 575 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.

6 third-party services load with your homepage (Shopify, Cloudflare CDN and Google Fonts and others), adding 663 KiB and 186 ms of main-thread time.

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

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

9 KiB JavaScript is shipped twice across bundles.

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).

4 KiB could be saved by minifying CSS.

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile banner”.

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

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

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

The first text or image appears after 1.8 s on a phone. Good is under 1.8 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.3 MB in 235 requests on a phone: images 1.6 MB (53), other files 783 KiB (91) and scripts 680 KiB (49). Under 2 MB keeps phones on slow connections fast.

Fanatico_del_lego_5_37f6512c-8c1e-41f6-82cf-2102e1e96b01.png 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).

1 image is downloaded at several times the size a phone draws it, for example 5s.png at 1,080 px wide, shown at 100 px. Resized copies would save about 49 KiB.

1 image (395 KiB) is 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.92 g of CO₂e: 110.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

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

Your title is 83 characters, so Google will cut it off around 60: “Planetabrick.cl | Figuras y Accesorios LEGO coleccionables en Chile – Planeta Brick”.

Your <h1> is empty.

The homepage links to 269 pages on planetabrick.cl and 7 external pages.

https://planetabrick.cl/collections/all, https://planetabrick.cl/collections/episodio-i, https://planetabrick.cl/collections/episodio-ii, https://planetabrick.cl/collections/episodio-iii, https://planetabrick.cl/collections/episodio-ix-x-xi and https://planetabrick.cl/collections/episodio-vii and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 736 words of visible text.

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