laisla.com.uy website review

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

fcdn.app costs a phone 1.3 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 10.1 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (fcdn.app, Google Tag Manager and Facebook and others), adding 7.4 MB and 3.4 s of main-thread time.

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

Google Tag Manager costs a phone 872 ms of main-thread work and 724 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.

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

Facebook costs a phone 658 ms of main-thread work and 404 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.

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

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

About 92 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.

Vimeo costs a phone 133 ms of main-thread work and 2.3 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.

scanandshield.com costs a phone 292 ms of main-thread work and 10 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.

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

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

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.

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.

For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ADIDAS AG26”.

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

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

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 268 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 7.8 MB in 242 requests on a phone: images 3.6 MB (152), scripts 2.0 MB (25) and other files 1.6 MB (53). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (568 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 2.22 g of CO₂e: 266.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

3 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is only 28 characters: “Surf y skate shop en Uruguay”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 1,065 pages on laisla.com.uy and 10 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://laisla.com.uy/salir declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://laisla.com.uy/salir all use the title “Surf y skate shop en Uruguay”, 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://laisla.com.uy/mi-cuenta/favoritos, https://laisla.com.uy/mi-cuenta, https://laisla.com.uy/mi-cuenta/mis-datos, https://laisla.com.uy/mi-cuenta/direcciones, https://laisla.com.uy/mi-cuenta/compras and https://laisla.com.uy/nuevo and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://laisla.com.uy/mi-cuenta/favoritos, https://laisla.com.uy/mi-cuenta, https://laisla.com.uy/mi-cuenta/mis-datos, https://laisla.com.uy/mi-cuenta/direcciones and https://laisla.com.uy/mi-cuenta/compras have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://f.fcdn.app/assets/manifest.json' from origin 'https://laisla.com.uy' has been blocked by…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

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.

Social proof on the homepage: 87 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,175 words of visible text.

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