sorteostec.org website review

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

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

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

8 third-party services load with your homepage (AppDynamics, Google Tag Manager and Facebook and others), adding 1.8 MB and 2.2 s of main-thread time.

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

AppDynamics costs a phone 942 ms of main-thread work and 179 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.

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

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

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

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

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

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

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.

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

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

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

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “El Sorteo para Ganar la mejor casa de tus sueños el hogar p…”.

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

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

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

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

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

Your homepage downloads 3.3 MB in 152 requests on a phone: scripts 2.4 MB (43), HTML 469 KiB (5) and images 268 KiB (51). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example sms36-3x2-nov-slider.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 57 KiB.

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

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

1 element hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 255 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 11 pages on sorteostec.org and 1 external page.

A phone browser shows 2,052 words, but the HTML your server sends has only 384. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://sorteostec.org/consulta-ganadores, https://sorteostec.org/tc-aviso-privacidad and https://sorteostec.org/avisos-de-privacidad declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://sorteostec.org/tc-aviso-privacidad and https://sorteostec.org/avisos-de-privacidad all use the title “Sorteos Tec. ¡Ganas más cuando das!”, 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://sorteostec.org/carrito/mi-cuenta/mi-perfil, https://sorteostec.org/carrito/mi-cuenta/ewallet, https://sorteostec.org/carrito/mi-cuenta/compras/boletos, https://sorteostec.org/carrito/mi-cuenta/rotulaciones, https://sorteostec.org/carrito/mi-cuenta/facturas and https://sorteostec.org/carrito/mi-cuenta/premios and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sorteostec.org/tc-aviso-privacidad and https://sorteostec.org/avisos-de-privacidad use the same meta description. A description written for each page earns more clicks.

https://sorteostec.org/carrito/mi-cuenta/mi-perfil, https://sorteostec.org/carrito/mi-cuenta/ewallet, https://sorteostec.org/carrito/mi-cuenta/compras/boletos, https://sorteostec.org/carrito/mi-cuenta/rotulaciones, https://sorteostec.org/carrito/mi-cuenta/facturas and https://sorteostec.org/carrito/mi-cuenta/premios and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sorteostec.org/consulta-ganadores 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.

https://sorteostec.org/tc-aviso-privacidad and https://sorteostec.org/avisos-de-privacidad took over 3 s to send their HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187013457&tm=gtm002&Ver=2&mid=f95d2af6-97a2-41c7-8fa3-dd04a6db94c9&bo=1&sid=fa422800d67c11f1812b63d2da8e616a&vid=fa422720d67c11f19506d786606b71fe&vids=1&msclkid=N&pi=9.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Requests the geolocation permission on page load.

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

Large scripts ship without source maps.

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.

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 2,052 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 8 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 29 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.