Website review, no card needed
golomax.com.ar website review
Visit site (opens in a new tab)Reviewed 19 October 202654 issues · 95 checks
This review found 54 issues worth fixing on golomax.com.ar, 24 of them high impact, across 95 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
53FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.4 s |
| May 2, 2026 | 3.5 s |
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 159 ms |
| May 2, 2026 | 158 ms |
| May 9, 2026 | 162 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 162 ms |
| May 30, 2026 | 160 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 173 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.4 s
2.9 s
4.3 s
5.8 s
7.2 s
8.7 s
10.1 s
11.6 s
Speed
Use efficient cache lifetimes
4.3 s · 19.4 MB173 files are served with short cache lifetimes, so returning visitors download them again (19.4 MB).
Reduce unused JavaScript
3.1 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
YouTube adds 1.0 s
1.0 sYouTube costs a phone 1.0 s of main-thread work and 3.2 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.
Mobile performance score: 14
14/100Your mobile performance score is 14. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,647 HTML elements
The page has 3,647 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 14.6 MB54 images could be 14.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and cliengo.com and others), adding 4.4 MB and 1.8 s of main-thread time.
Reduce unused CSS
900 ms · 165 KiBAbout 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 609 ms
609 msGoogle Tag Manager costs a phone 609 ms of main-thread work and 872 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
450 ms · 116 KiB116 KiB could be saved by minifying JavaScript.
Render-blocking requests
450 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify CSS
28 KiB28 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: 362 ms
362 msYour server sent the HTML in 362 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 CLS: 0.60
0.60For real visitors the layout shifts by 0.60 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 18.8 s
18.8 sYour largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Golomax”.
Speed Index: 20.9 s
20.9 sVisually, the page fills in at 20.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 79.4 s
79.4 sThe page becomes fully interactive after 79.4 s. Good is under 3.8 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.539
0.539The layout shifts by 0.539 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 883 ms
883 msScripts block taps and scrolling for 883 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 253 ms
253 msReal visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 951 ms
951 msReal visitors wait 951 ms for your server to start answering (75th percentile). Good is under 800 ms.
124 images without width and height
124 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 159 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 23.9 MB in 290 requests
23.9 MBYour homepage downloads 23.9 MB in 290 requests on a phone: images 18.7 MB (145), scripts 4.1 MB (56) and HTML 427 KiB (13). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 13.7 MB together. On a phone connection a single image that size takes seconds.
23 images in older formats
23 images (17.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.
14 images below the first screen load straight away
14 images further down the page (356 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.8 g of CO₂ per visit
6.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.77 g of CO₂e: 812.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (66 elements)
All page content should be contained by landmarks: 66 elements on the page fail this check, rated moderate by axe-core.
108 links without text
108 visible links have no text or label, so screen readers cannot say where they go.
104 form fields without a label
104 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 checks passed
Every image has alt text
All 66 images in the HTML carry an alt attribute.
44 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: 44 passed and 8 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.
105 links crawlers can't follow
105 links have no real href, so search engines can't follow them.
Title is short (7 characters)
Your title is only 7 characters: “Golomax”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
No XML sitemap
No XML sitemap at https://www.golomax.com.ar/sitemap.xml, so Google discovers your pages only by following links.
174 internal links, 14 external
The homepage links to 174 pages on golomax.com.ar and 14 external pages.
4 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Distribuidora mayorista de golosinas, galletitas, bebidas y snacks para kioscos y comercios. Comprá online en Golomax a…”.
Canonical URL set
The canonical URL is https://www.golomax.com.ar/.
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.
AI search readiness
Most text only appears after JavaScript runs
26%A phone browser shows 1,386 words, but the HTML your server sends has only 365. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.golomax.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Other pages
2 pages share a meta description
https://www.golomax.com.ar/catalogo/ofertas and https://www.golomax.com.ar/catalogo/novedades use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 151 found) and read each the way a search engine does.
7 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
27 small tap targets
27 of 122 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 1,386 words of copy
The homepage carries about 1,386 words of visible text.
4 checks passed
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
21 other companies contacted
Loading the homepage contacts 21 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 golomax.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
- Framework
- Vue.js
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on golomax.com.ar, including 27 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.