Website review, no card needed
onfit.com.ar website review
Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 76 checks
This review found 33 issues worth fixing on onfit.com.ar, 10 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 216 ms |
| May 9, 2026 | 213 ms |
| May 16, 2026 | 211 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 211 ms |
| Jun 6, 2026 | 223 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 220 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 211 ms |
| Jul 25, 2026 | 207 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 193 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 203 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
Speed
Improve image delivery
1.5 MB15 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 97 KiBAbout 97 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 178 KiB and 139 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 96 ms. During a long task the page ignores taps.
Reduce unused CSS
19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 869 ms of it running JavaScript. That is comfortably low.
Server response: 20 ms
20 msYour server sent the HTML in 20 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.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Real-user TTFB: 866 ms
866 msReal visitors wait 866 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 216 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 191 ms
191 msReal visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 48 requests
2.6 MBYour homepage downloads 2.6 MB in 48 requests on a phone: images 2.1 MB (23), scripts 404 KiB (16) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.
14 images in older formats
14 images (1.6 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
home-slider-3-mobile.webp 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).
2 images far larger than shown
160 KiB2 images are downloaded at several times the size a phone draws them, for example unilever.png at 3,000 px wide, shown at 160 px. Resized copies would save about 160 KiB.
6 images below the first screen load straight away
6 images further down the page (320 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 89.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 long (211 characters)
Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.
18 internal links, 3 external
The homepage links to 18 pages on onfit.com.ar and 3 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Mejorá tu bienestar en On Fit”.
Title: 32 characters
Your title is a healthy 32 characters: “On Fit - Tu Low Cost Premium Gym”.
Canonical URL set
The canonical URL is https://onfit.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://onfit.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://onfit.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 (556 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages point its canonical at the homepage
https://onfit.com.ar/clases, https://onfit.com.ar/planes, https://onfit.com.ar/empleos, https://onfit.com.ar/contacto, https://onfit.com.ar/tienda-onfit and https://onfit.com.ar/faqs and 2 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
8 pages share a title
/, https://onfit.com.ar/clases, https://onfit.com.ar/empleos, https://onfit.com.ar/contacto, https://onfit.com.ar/tienda-onfit and https://onfit.com.ar/faqs and 2 others all use the title “On Fit - Tu Low Cost Premium Gym”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages share a meta description
https://onfit.com.ar/clases, https://onfit.com.ar/empleos, https://onfit.com.ar/contacto, https://onfit.com.ar/tienda-onfit, https://onfit.com.ar/faqs and https://onfit.com.ar/sucursales and 1 other use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://onfit.com.ar/clases and https://onfit.com.ar/planes have no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Every page has a meta description
All 8 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
20 of 23 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 495 words of copy
The homepage carries about 495 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 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 onfit.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
- Next.js
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on onfit.com.ar, including 12 speed issues, 2 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.