miresiduo.app website review

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

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

About 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.6 s faster on a phone.

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and leadster.com.br and others), adding 1.7 MB and 1.1 s of main-thread time.

140 KiB could be saved by minifying CSS.

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

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

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

23 KiB could be saved by minifying JavaScript.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 66 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.

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

Your largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “miResiduo entrega indicadores ESG, mejora la gestión de la …”.

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

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

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

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 5.7 MB in 147 requests on a phone: scripts 2.8 MB (63), stylesheets 1.4 MB (37) and images 937 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image (88 KiB) is 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.

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

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

[role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

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

Your title is only 16 characters: “Home - miResiduo”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 38 pages on miresiduo.app and 23 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.miresiduo.app/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.miresiduo.app/blog has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miresiduo.app/blog, https://www.miresiduo.app/transp-recep and https://www.miresiduo.app/generador have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.miresiduo.app/generador and https://www.miresiduo.app/que-son-los-cookies took over 3 s to send their HTML from our server.

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

3 images are served at too low a resolution for sharp phone screens.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 7 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.