Website review, no card needed

gonzalezgimenez.com.py logo

gonzalezgimenez.com.py website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 92 checks

This review found 52 issues worth fixing on gonzalezgimenez.com.py, 25 of them high impact, across 92 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s3.1 sApr 25Oct 103.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.3 s
May 2, 20263.4 s
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
306 ms208 msApr 25Oct 10295 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026224 ms
May 2, 2026221 ms
May 9, 2026220 ms
May 16, 2026219 ms
May 23, 2026221 ms
May 30, 2026225 ms
Jun 6, 2026232 ms
Jun 13, 2026243 ms
Jun 20, 2026252 ms
Jun 27, 2026255 ms
Jul 4, 2026256 ms
Jul 11, 2026252 ms
Jul 18, 2026256 ms
Jul 25, 2026264 ms
Aug 1, 2026267 ms
Aug 8, 2026278 ms
Aug 15, 2026279 ms
Aug 22, 2026286 ms
Aug 29, 2026285 ms
Sep 5, 2026284 ms
Sep 12, 2026284 ms
Sep 19, 2026285 ms
Sep 26, 2026289 ms
Oct 3, 2026291 ms
Oct 10, 2026295 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gonzalezgimenez.com.py (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gonzalezgimenez.com.py at 0.8 s0.8 s
  2. gonzalezgimenez.com.py at 1.5 s1.5 s
  3. gonzalezgimenez.com.py at 2.2 s2.2 s
  4. gonzalezgimenez.com.py at 3.0 s3.0 s
  5. gonzalezgimenez.com.py at 3.7 s3.7 s
  6. gonzalezgimenez.com.py at 4.5 s4.5 s
  7. gonzalezgimenez.com.py at 5.2 s5.2 s
  8. gonzalezgimenez.com.py at 6.0 s6.0 s

Speed

13 to fix16
  • Improve image delivery

    7.1 s · 9.0 MB

    75 images could be 9.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.

  • Reduce unused JavaScript

    10.9 s · 1.9 MB

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

  • Use efficient cache lifetimes

    3.9 s · 3.7 MB

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

  • 21,568 HTML elements

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

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 16

    16/100

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

  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

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

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

  • Google Tag Manager adds 858 ms

    858 ms

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

  • Reduce unused CSS

    450 ms · 73 KiB

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

  • Google Maps adds 141 ms

    141 ms

    Google Maps costs a phone 141 ms of main-thread work and 383 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 CDN adds 97 ms

    97 ms

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    31 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 333 ms

    333 ms

    Your server sent the HTML in 333 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix0
  • Fails Core Web Vitals for real visitors

    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-user INP: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.26

    0.26

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

  • Largest Contentful Paint: 51.8 s

    51.8 s

    Your largest element takes 51.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “🎉 ¡Viví tu #MomentoAltech y ganá un iPhone Duo! 📱”.

  • Time to Interactive: 53.3 s

    53.3 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Cumulative Layout Shift: 0.286

    0.286

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Tap response (INP) got 32% slower for real visitors

    +32%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

1 checks passed
  • Real-user TTFB: 682 ms

    682 ms

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

Images and page weight

4 to fix40
  • Page weight: 14.8 MB in 249 requests

    14.8 MB

    Your homepage downloads 14.8 MB in 249 requests on a phone: images 10.8 MB (131), scripts 3.4 MB (39) and fonts 180 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 12 images far larger than shown

    1.8 MB

    12 images are downloaded at several times the size a phone draws them, for example promocion_desktop1541_1791468668.png at 1,900 px wide, shown at 360 px. Resized copies would save about 1.8 MB.

  • 40 images in older formats

    40 images (6.7 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.

  • An image on the first screen is lazy-loaded

    banner_mobi1186_1791469291.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.19 g

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

Accessibility

8 to fixGoogle 8389
  • 51 buttons without a name

    51 buttons have no accessible name, so screen readers announce just “button”.

  • 25 tap targets too small

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

  • 11 text elements with low contrast

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

  • 2 images without alt text

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

  • Page should contain a level-one heading (1 element)

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

  • ARIA role should be appropriate for the element (24 elements)

    ARIA role should be appropriate for the element: 24 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (24 elements)

    Elements marked as presentational should be consistently ignored: 24 elements on the page fail this check, rated minor by axe-core.

  • 5 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9269
  • No H1 headline

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

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Página Principal - González Giménez & Cía. - Tienda Online de Electrodomésticos”.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (204 characters)

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 1,364 internal links, 6 external

    The homepage links to 1,364 pages on gonzalezgimenez.com.py and 6 external pages.

3 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gonzalezgimenez.com.py/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    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.

  • Some text only appears after JavaScript runs

    55%

    The HTML your server sends has 3,262 of the 5,936 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

1 to fix95
  • 10 pages without an H1

    https://www.gonzalezgimenez.com.py/lista-bodas, https://www.gonzalezgimenez.com.py/favoritos, https://www.gonzalezgimenez.com.py/categoria/104/climatizacion, https://www.gonzalezgimenez.com.py/categoria/130/ventilacion, https://www.gonzalezgimenez.com.py/categoria/264/ventilador-combinado and https://www.gonzalezgimenez.com.py/categoria/261/ventiladores-de-mesa and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.gonzalezgimenez.com.py/lista-bodas took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Refused to execute script from 'https://ads01.groovinads.com/grv/track/bhpx.os?idc=2669' because its MIME type ('image/…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    429 of 451 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 5,936 words of copy

    The homepage carries about 5,936 words of visible text.

4 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 34 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gonzalezgimenez.com.py, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Vue.js
Analytics
Google Analytics | Google Tag Manager | Hotjar

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on gonzalezgimenez.com.py, including 25 speed issues, 6 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25