Website review, no card needed
gigot.com.ar website review
Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 84 checks
This review found 39 issues worth fixing on gigot.com.ar, 21 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
70C- #103,608 of 124,455 reviewed websitesbeats 14%
- #62,764 of 69,907 online storesbeats 8%
- #2,232 of 2,919 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 9.0 s |
| May 16, 2026 | 9.0 s |
| May 23, 2026 | 9.1 s |
| May 30, 2026 | 9.5 s |
| Jun 6, 2026 | 9.7 s |
| Jun 13, 2026 | 9.7 s |
| Jun 20, 2026 | 9.8 s |
| Jun 27, 2026 | 9.7 s |
| Jul 4, 2026 | 9.7 s |
| Jul 11, 2026 | 9.8 s |
| Jul 18, 2026 | 9.9 s |
| Jul 25, 2026 | 10.0 s |
| Aug 1, 2026 | 10.3 s |
| Aug 8, 2026 | 10.1 s |
| Aug 15, 2026 | 9.3 s |
| Aug 22, 2026 | 8.6 s |
| Aug 29, 2026 | 7.2 s |
| Sep 5, 2026 | 6.9 s |
| Sep 12, 2026 | 7.1 s |
| Sep 19, 2026 | 7.1 s |
| Sep 26, 2026 | 7.1 s |
| Oct 3, 2026 | 7.0 s |
| Oct 10, 2026 | 6.8 s |
| Oct 17, 2026 | 6.4 s |
| Oct 24, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 340 ms |
| May 16, 2026 | 333 ms |
| May 23, 2026 | 328 ms |
| May 30, 2026 | 334 ms |
| Jun 6, 2026 | 343 ms |
| Jun 13, 2026 | 349 ms |
| Jun 20, 2026 | 354 ms |
| Jun 27, 2026 | 350 ms |
| Jul 4, 2026 | 348 ms |
| Jul 11, 2026 | 348 ms |
| Jul 18, 2026 | 349 ms |
| Jul 25, 2026 | 355 ms |
| Aug 1, 2026 | 359 ms |
| Aug 8, 2026 | 369 ms |
| Aug 15, 2026 | 373 ms |
| Aug 22, 2026 | 379 ms |
| Aug 29, 2026 | 381 ms |
| Sep 5, 2026 | 381 ms |
| Sep 12, 2026 | 377 ms |
| Sep 19, 2026 | 376 ms |
| Sep 26, 2026 | 382 ms |
| Oct 3, 2026 | 386 ms |
| Oct 10, 2026 | 395 ms |
| Oct 17, 2026 | 393 ms |
| Oct 24, 2026 | 390 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
1.3 s
2.7 s
4.0 s
5.3 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Reduce unused JavaScript
8.0 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.
Render-blocking requests
5.3 s55 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Use efficient cache lifetimes
1.8 s · 401 KiB19 files are served with short cache lifetimes, so returning visitors download them again (401 KiB).
YouTube adds 1.3 s
1.3 sYouTube costs a phone 1.3 s of main-thread work and 2.9 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.
Main-thread work: 10.1 s
A phone's processor spends 10.1 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,149 HTML elements
The page has 3,149 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google CDN and Facebook and others), adding 4.5 MB and 2.3 s of main-thread time.
Reduce unused CSS
750 ms · 266 KiBAbout 266 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.
Improve image delivery
450 ms · 172 KiB6 images could be 172 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 438 ms
438 msGoogle CDN costs a phone 438 ms of main-thread work and 741 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
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 325 ms. During a long task the page ignores taps.
Facebook adds 281 ms
281 msFacebook costs a phone 281 ms of main-thread work and 371 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.
Minify JavaScript
150 ms · 33 KiB33 KiB could be saved by minifying JavaScript.
Legacy JavaScript
100 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
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: 228 ms
228 msYour server sent the HTML in 228 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: 7.9 s
7.9 sReal visitors wait 7.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 32.4 s
32.4 sYour largest element takes 32.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 46.7 s
46.7 sThe page becomes fully interactive after 46.7 s. Good is under 3.8 s.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Real-user INP: 497 ms
497 msReal visitors wait 497 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 340 ms to 390 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 9.0 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 8.6 MB in 311 requests
8.6 MBYour homepage downloads 8.6 MB in 311 requests on a phone: scripts 5.2 MB (140), images 1.9 MB (61) and stylesheets 485 KiB (64). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
63 KiB2 images are downloaded at several times the size a phone draws them, for example cyber-mobilelogo-768x519.png at 768 px wide, shown at 173 px. Resized copies would save about 63 KiB.
9 images in older formats
9 images (434 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 below the first screen load straight away
1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 293.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
79 links without text
79 visible links have no text or label, so screen readers cannot say where they go.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 4 mores 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.
Title is short (16 characters)
Your title is only 16 characters: “GIGOT Cosméticos”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
213 internal links, 31 external
The homepage links to 213 pages on gigot.com.ar and 31 external pages.
6 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Belleza, bienestar y cosmética natural. Comercializamos nuestros productos a través del sistema de venta directa o reve…”.
Canonical URL set
The canonical URL is https://www.gigot.com.ar/.
Structured data in place
Structured data found: Article, HealthAndBeautyBusiness, ImageObject, Organization and Person.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.gigot.com.ar/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
No llms.txt
There is no https://www.gigot.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,127 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 69 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
90 of 95 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 897 words of copy
The homepage carries about 897 words of visible text.
8 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Register”.
5 short forms
5 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 31 testimonial or review blocks, 13 customer or partner logos and 48 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 1 of them by other companies (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.
22 other companies contacted
Loading the homepage contacts 22 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 gigot.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- React
- E-commerce
- WooCommerce
- Analytics
- Microsoft Clarity
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on gigot.com.ar, including 25 speed issues, 3 SEO issues and 1 conversion gap. 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.