tecnomyl.com.py website review

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

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

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

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

Your mobile performance score is 53 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

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

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

4 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 1.4 MB and 559 ms of main-thread time.

YouTube costs a phone 430 ms of main-thread work and 978 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.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google CDN costs a phone 120 ms of main-thread work and 347 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.

8 KiB could be saved by minifying JavaScript.

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

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.

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 82 ms to 77 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.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.4 MB in 105 requests on a phone: images 3.2 MB (24), scripts 1.4 MB (35) and fonts 531 KiB (9). Under 2 MB keeps phones on slow connections fast.

7 images (505 KiB) are 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.

1 image is downloaded at several times the size a phone draws it, for example logo-iso-768x768.png at 390 px wide, shown at 32 px. Resized copies would save about 130 KiB.

4 images further down the page (246 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 1.54 g of CO₂e: 184.7 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.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 13 characters: “Tecnomyl S.A.”. 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.

No Open Graph image (also missing: og:title, og:description), 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 63 pages on tecnomyl.com.py and 7 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.tecnomyl.com.py/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.tecnomyl.com.py/nosotros, https://www.tecnomyl.com.py/gestion-responsable, https://www.tecnomyl.com.py/social-y-ambiental, https://www.tecnomyl.com.py/soluciones, https://www.tecnomyl.com.py/tecnonews and https://www.tecnomyl.com.py/canal-de-denuncias and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tecnomyl.com.py/nosotros, https://www.tecnomyl.com.py/gestion-responsable, https://www.tecnomyl.com.py/social-y-ambiental, https://www.tecnomyl.com.py/soluciones, https://www.tecnomyl.com.py/tecnonews and https://www.tecnomyl.com.py/canal-de-denuncias have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tecnomyl.com.py/soluciones/herbicidas, https://www.tecnomyl.com.py/soluciones/insecticidas, https://www.tecnomyl.com.py/soluciones/biodefensivos, https://www.tecnomyl.com.py/soluciones/fungicidas, https://www.tecnomyl.com.py/soluciones/curasemillas and https://www.tecnomyl.com.py/soluciones/linea-spray-solutions and 1 other have 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://www.tecnomyl.com.py/social-y-ambiental, https://www.tecnomyl.com.py/soluciones, https://www.tecnomyl.com.py/tecnonews and https://www.tecnomyl.com.py/canal-de-denuncias took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Bootstrap's JavaScript requires jQuery”.

1 image is displayed at the wrong aspect ratio, so it looks 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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 162 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

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