lazpiur.com website review

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

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

About 346 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

About 152 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

Google Tag Manager costs a phone 315 ms of main-thread work and 333 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.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 399 KiB and 331 ms of main-thread time.

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

1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

Desktop scores 63 but mobile only 21. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

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

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

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

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

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 4.1 MB in 106 requests on a phone: images 2.5 MB (5), scripts 873 KiB (40) and fonts 419 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

4 tap targets are too small or too close together to hit reliably with a finger.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

The homepage links to 252 pages on lazpiur.com and 2 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://www.lazpiur.com/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://www.lazpiur.com/electronic-machines/pcb-cleaning, https://www.lazpiur.com/electronic-machines/maquina-de-montaje-de-tornillos-press-fit and https://www.lazpiur.com/electronic-machines/linea-de-montaje-de-componentes all use the title “Línea de fabricación de headers | Lazpiur”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lazpiur.com/electronic-machines/pcb-cleaning, https://www.lazpiur.com/electronic-machines/fabricacion-de-headers, https://www.lazpiur.com/electronic-machines/maquina-de-montaje-de-tornillos-press-fit and https://www.lazpiur.com/electronic-machines/linea-de-montaje-de-componentes use the same meta description. A description written for each page earns more clicks.

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

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.

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.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

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.