sertres.com website review

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

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

1 image could be 51 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

1 third-party service load with your homepage (Google Fonts), adding 50 KiB and 0 ms of main-thread time.

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.

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Somos expertos en infraestructura de misión crítica”. Most of its time is element render delay (4.3 s).

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

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

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

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

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

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

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

Your homepage downloads 7.6 MB in 85 requests on a phone: media 5.2 MB (2), images 1.9 MB (78) and scripts 528 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example logo-envolvente.png at 1,920 px wide, shown at 40 px. Resized copies would save about 51 KiB.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 491 words, but the HTML your server sends has only 0. 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.

There is no https://sertres.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.

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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