puppis.com.ar website review

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

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

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

vtexassets.com costs a phone 1.3 s of main-thread work and 8.3 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.

Google Tag Manager costs a phone 1.2 s of main-thread work and 562 KiB 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.

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

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

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

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

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

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

7 KiB could be saved by minifying JavaScript.

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

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

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

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.97 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 8.7 MB in 244 requests on a phone: images 5.0 MB (71), scripts 2.0 MB (60) and fonts 992 KiB (6). Under 2 MB keeps phones on slow connections fast.

c252cf7e-f275-4e69-a0cc-0fd7fd8aec44___4bae2588fc0a8579a57f6 weighs 851 KiB. On a phone connection a single image that size takes seconds.

2 images (1.0 MB) 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 avatar.png at 584 px wide, shown at 46 px. Resized copies would save about 178 KiB.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 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.

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

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

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

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

Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 183 pages on puppis.com.ar and 13 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://www.puppis.com.ar/perros/alimentos/alimentos-humedos has no <title>, so Google invents the link text in results.

https://www.puppis.com.ar/perros/alimentos/alimentos-humedos has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.puppis.com.ar/nosotros and https://www.puppis.com.ar/trabajaconnosotros use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.puppis.com.ar/trabajaconnosotros, whose canonical is https://www.puppis.com.ar/trabaja-con-nosotros. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.puppis.com.ar/nosotros and https://www.puppis.com.ar/perros/alimentos/alimentos-humedos have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.puppis.com.ar/perros, https://www.puppis.com.ar/perros/alimentos/alimentos-medicados, https://www.puppis.com.ar/perros/alimentos/alimentos-naturales, https://www.puppis.com.ar/perros/snacks, https://www.puppis.com.ar/perros/snacks/galletitas-secas and https://www.puppis.com.ar/perros/snacks/galletitas-humedas took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://www.puppis.com.ar/.

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

3 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

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

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

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.

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

The page uses urgency cues (a countdown or limited-time wording).

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