blazevideo.es website review

41 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

8 third-party services load with your homepage (shoparize.com, Cloudflare and Cloudflare CDN and others), adding 1,003 KiB and 127 ms of main-thread time.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

1 long task block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.

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.

Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Compra segura | Enviar a ES | Entrega gratuita 3-5 días 🚚 …”.

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

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

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 2.5 MB in 102 requests on a phone: images 1.2 MB (24), other files 813 KiB (47) and scripts 446 KiB (18). Under 2 MB keeps phones on slow connections fast.

16 images (1.0 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example payment_icon_d5dbd800-712e-489a-9f0c-f9371b75edca_v-16847473 at 2,953 px wide, shown at 342 px. Resized copies would save about 90 KiB.

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

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

The page declares lang=“ShopLocaleD…”, which is not a usable language code, so screen readers and translation tools guess.

Your title is 69 characters, so Google will cut it off around 60: “BlazeVideo Camara Fototrampeo Nocturna para Monitorea tus alrededores”.

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

The homepage links to 78 pages on blazevideo.es and 15 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.

There is no https://blazevideo.es/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://blazevideo.es/collections/wifi-camara, https://blazevideo.es/collections/bundle-fototrampeo-paneles-solares and https://blazevideo.es/collections/bundle-4g-fototrampeo-paneles-solares have no meta description, so Google writes the search snippet from whatever text it finds.

https://blazevideo.es/collections/blaze-accesorios and https://blazevideo.es/collections/blazevideo-accesorios-de-caza use the same meta description. A description written for each page earns more clicks.

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

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

5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

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.

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

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

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