Website review, no card needed
genneia.com.ar website review
Visit site (opens in a new tab)Reviewed 26 October 202648 issues · 89 checks
This review found 48 issues worth fixing on genneia.com.ar, 24 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 5.8 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 5.7 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 109 ms |
| May 16, 2026 | 107 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 154 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.3 s
4.9 s
Speed
Use efficient cache lifetimes
16.1 s · 4.0 MB67 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).
Render-blocking requests
4.8 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Reduce unused JavaScript
1.6 s · 290 KiBAbout 290 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.
Improve image delivery
1.0 s · 393 KiB2 images could be 393 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 73). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 170 KiBAbout 170 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 585 KiB and 326 ms of main-thread time.
Minify JavaScript
150 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Document request latency
41 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
20 KiB20 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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 893 ms of it running JavaScript. That is comfortably low.
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 5.7 s
5.7 sReal visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 23.6 s
23.6 sYour largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 109 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.2 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 174 ms
174 msReal visitors wait 174 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Total Blocking Time: 147 ms
147 msScripts block the page for only 147 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 79 requests
4.5 MBYour homepage downloads 4.5 MB in 79 requests on a phone: images 3.1 MB (24), scripts 904 KiB (28) and stylesheets 231 KiB (17). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (675 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 far larger than shown
151 KiB1 image is downloaded at several times the size a phone draws it, for example Pop6aac62a0119c3popupciberseguridad.jpg at 1,920 px wide, shown at 353 px. Resized copies would save about 151 KiB.
2 images below the first screen load straight away
2 images further down the page (66 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
45 text elements with low contrast
45 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (7 characters)
Your title is only 7 characters: “Genneia”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (24 characters)
Your meta description is only 24 characters: “En constante generación.”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at genneia.com.ar/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
46 internal links, 7 external
The homepage links to 46 pages on genneia.com.ar and 7 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.genneia.com.ar/.
XML sitemap found
Your XML sitemap is reachable at https://www.genneia.com.ar/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.genneia.com.ar/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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (689 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages hidden from search
https://www.genneia.com.ar/nosotros/perfil, https://www.genneia.com.ar/activos-proyectos, https://www.genneia.com.ar/compromiso, https://www.genneia.com.ar/nosotros/generalidades, https://www.genneia.com.ar/nosotros/comite and https://www.genneia.com.ar/nosotros/accionistas and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
16 pages share a title
/, https://www.genneia.com.ar/nosotros/perfil, https://www.genneia.com.ar/activos-proyectos, https://www.genneia.com.ar/compromiso, https://www.genneia.com.ar/nosotros/generalidades and https://www.genneia.com.ar/nosotros/comite and 10 others all use the title “Genneia”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.genneia.com.ar/nosotros/perfil, https://www.genneia.com.ar/activos-proyectos, https://www.genneia.com.ar/compromiso, https://www.genneia.com.ar/nosotros/generalidades, https://www.genneia.com.ar/nosotros/comite and https://www.genneia.com.ar/nosotros/accionistas and 8 others use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://www.genneia.com.ar/nosotros/perfil, https://www.genneia.com.ar/compromiso, https://www.genneia.com.ar/nosotros/generalidades, https://www.genneia.com.ar/nosotros/comite, https://www.genneia.com.ar/nosotros/accionistas and https://www.genneia.com.ar/servicios and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
4 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 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
17 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 580 words of copy
The homepage carries about 580 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) Ads (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
11 other companies contacted
Loading the homepage contacts 11 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 genneia.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on genneia.com.ar, including 17 speed issues, 8 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.