Website review, no card needed

gofitness.com.mx logo

gofitness.com.mx website review

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

This review found 52 issues worth fixing on gofitness.com.mx, 29 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.

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

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

Full-page screenshot of gofitness.com.mx (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gofitness.com.mx at 2.0 s2.0 s
  2. gofitness.com.mx at 4.0 s4.0 s
  3. gofitness.com.mx at 6.0 s6.0 s
  4. gofitness.com.mx at 8.0 s8.0 s
  5. gofitness.com.mx at 10.0 s10.0 s
  6. gofitness.com.mx at 12.0 s12.0 s
  7. gofitness.com.mx at 14.0 s14.0 s
  8. gofitness.com.mx at 16.0 s16.0 s

Speed

15 to fix36
  • Use efficient cache lifetimes

    41.1 s · 9.5 MB

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

  • Improve image delivery

    30.1 s · 6.5 MB

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

  • Render-blocking requests

    7.9 s

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

  • Reduce unused CSS

    6.8 s · 1.1 MB

    About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.8 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 1.1 MB

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

  • Font display

    1.6 s

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 4.6 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 1.8 MB and 1.0 s of main-thread time.

  • Minify CSS

    750 ms · 195 KiB

    195 KiB could be saved by minifying CSS.

  • Google Tag Manager adds 609 ms

    609 ms

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

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 439 ms. During a long task the page ignores taps.

  • Facebook adds 397 ms

    397 ms

    Facebook costs a phone 397 ms of main-thread work and 222 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

    305 KiB

    305 KiB could be saved by minifying JavaScript.

  • Cloudinary adds 0 ms

    0 ms

    Cloudinary costs a phone 0 ms of main-thread work and 1.0 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.

  • Document request latency

    37 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    12 KiB

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

  • 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: 190 ms

    190 ms

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

Core Web Vitals

10 to fix67
  • 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: 9.3 s

    9.3 s

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

  • Real-user FCP: 6.4 s

    6.4 s

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

  • Real-user TTFB: 3.9 s

    3.9 s

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

  • First Contentful Paint: 9.6 s

    9.6 s

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

  • Largest Contentful Paint: 51.4 s

    51.4 s

    Your largest element takes 51.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “imagen_movile”.

  • Speed Index: 29.5 s

    29.5 s

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

  • Time to Interactive: 51.7 s

    51.7 s

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

  • Total Blocking Time: 774 ms

    774 ms

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

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 11.2 MB in 90 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 90 requests on a phone: images 7.4 MB (18), scripts 2.3 MB (37) and stylesheets 1.2 MB (21). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    octubre2026.jpg weighs 6.1 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    4.5 MB

    2 images are downloaded at several times the size a phone draws them, for example octubre2026.jpg at 2,251 px wide, shown at 390 px. Resized copies would save about 4.5 MB.

  • 1 image in older formats

    1 image (6.1 MB) is 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.

  • About 3.2 g of CO₂ per visit

    3.18 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

10 to fixGoogle 5883
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Orphan list items

    Some list items are not inside a list.

  • 2 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

6 to fixGoogle 10072
  • Title is short (11 characters)

    Your title is only 11 characters: “GO! Fitness”. 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 long (181 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.gofitness.com.mx/sitemap.xml, so Google discovers your pages only by following links.

  • One H1 headline

    Your <h1> is empty.

  • 53 internal links, 11 external

    The homepage links to 53 pages on gofitness.com.mx and 11 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.gofitness.com.mx/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.

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 (374 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 3 linked pages are broken

    Your homepage links to https://www.gofitness.com.mx/clases/gimnasia-kids, https://www.gofitness.com.mx/clases/power-jump and https://www.gofitness.com.mx/clases/movilidad, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 12 pages without an H1

    https://www.gofitness.com.mx/centros, https://www.gofitness.com.mx/centros/altavista, https://www.gofitness.com.mx/centros/cancun, https://www.gofitness.com.mx/centros/del-valle, https://www.gofitness.com.mx/centros/el-rosario and https://www.gofitness.com.mx/centros/parque-jardin and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.gofitness.com.mx/centros has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 12 pages slow to respond

    https://www.gofitness.com.mx/centros, https://www.gofitness.com.mx/centros/altavista, https://www.gofitness.com.mx/centros/cancun, https://www.gofitness.com.mx/centros/del-valle, https://www.gofitness.com.mx/centros/el-rosario and https://www.gofitness.com.mx/centros/parque-jardin and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 12 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 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)”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 295 words of copy

    The homepage carries about 295 words of visible text.

4 checks passed
  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 3 customer or partner logos.

  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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 gofitness.com.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on gofitness.com.mx, including 25 speed issues, 6 SEO issues and 2 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