Website review, no card needed

megatlon.com logo

megatlon.com website review

Visit site (opens in a new tab)Reviewed 19 November 202636 issues · 73 checks

This review found 36 issues worth fixing on megatlon.com, 17 of them high impact, across 73 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

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.3 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.5 s
Nov 7, 20261.5 s
Nov 14, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
142 ms117 msMay 30Nov 14138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026122 ms
Jun 13, 2026121 ms
Jun 20, 2026120 ms
Jun 27, 2026120 ms
Jul 4, 2026120 ms
Jul 11, 2026120 ms
Jul 18, 2026122 ms
Jul 25, 2026123 ms
Aug 1, 2026122 ms
Aug 8, 2026122 ms
Aug 15, 2026123 ms
Aug 22, 2026123 ms
Aug 29, 2026124 ms
Sep 5, 2026124 ms
Sep 12, 2026124 ms
Sep 19, 2026124 ms
Sep 26, 2026126 ms
Oct 3, 2026129 ms
Oct 10, 2026133 ms
Oct 17, 2026136 ms
Oct 24, 2026137 ms
Oct 31, 2026138 ms
Nov 7, 2026139 ms
Nov 14, 2026138 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

Full-page screenshot of megatlon.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. megatlon.com at 0.5 s0.5 s
  2. megatlon.com at 1.0 s1.0 s
  3. megatlon.com at 1.5 s1.5 s
  4. megatlon.com at 2.0 s2.0 s
  5. megatlon.com at 2.6 s2.6 s
  6. megatlon.com at 3.1 s3.1 s
  7. megatlon.com at 3.6 s3.6 s
  8. megatlon.com at 4.1 s4.1 s

Speed

9 to fix44
  • Use efficient cache lifetimes

    4.5 s · 3.9 MB

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

  • Reduce unused JavaScript

    2.7 s · 493 KiB

    About 493 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Improve image delivery

    1.5 s · 1.5 MB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 44

    44/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.1 MB and 932 ms of main-thread time.

  • Google Tag Manager adds 534 ms

    534 ms

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

    500 ms

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

  • Main-thread work: 2.5 s

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

  • Reduce unused CSS

    150 ms · 127 KiB

    About 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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.

1 checks passed
  • Server response: 393 ms

    393 ms

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

Core Web Vitals

9 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 FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 15.6 s

    15.6 s

    Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Conocé servicios y membresías Megatlon”. Most of its time is element render delay (10.0 s).

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 831 ms

    831 ms

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 51 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 51 requests on a phone: images 1.8 MB (7), media 1.7 MB (3) and scripts 1.1 MB (16). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9297
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“próximamente mar del plata” and “DESCARGÁ LA APP”). One clear main headline is easier for people and search engines.

  • Meta description is long (166 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 25 internal links, 15 external

    The homepage links to 25 pages on megatlon.com and 15 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://megatlon.com/.

  • 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://megatlon.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • 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://megatlon.com/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.

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://megatlon.com/sedes, https://megatlon.com/membresias, https://megatlon.com/pase-de-prueba, https://megatlon.com/kidsandteens, https://megatlon.com/contacto and https://megatlon.com/dudas and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://megatlon.com/sedes, https://megatlon.com/membresias, https://megatlon.com/pase-de-prueba, https://megatlon.com/kidsandteens, https://megatlon.com/contacto and https://megatlon.com/mar-del-plata and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://megatlon.com/kidsandteens, https://megatlon.com/contacto, https://megatlon.com/mar-del-plata, https://megatlon.com/dudas, https://megatlon.com/corporativo and https://megatlon.com/rrhh and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 18 small tap targets

    18 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 125 words

    The homepage has only about 125 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 megatlon.com, 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 36 issues on megatlon.com, including 18 speed issues, 4 SEO issues and 5 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