Website review, no card needed

echelonfit.com logo

echelonfit.com website review

Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 79 checks

This review found 26 issues worth fixing on echelonfit.com, 7 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
2.4 s1.8 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
158 ms125 msMay 16Oct 31148 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026136 ms
May 23, 2026135 ms
May 30, 2026138 ms
Jun 6, 2026141 ms
Jun 13, 2026143 ms
Jun 20, 2026137 ms
Jun 27, 2026136 ms
Jul 4, 2026129 ms
Jul 11, 2026129 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026136 ms
Aug 8, 2026137 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026129 ms
Sep 5, 2026133 ms
Sep 12, 2026134 ms
Sep 19, 2026137 ms
Sep 26, 2026145 ms
Oct 3, 2026147 ms
Oct 10, 2026154 ms
Oct 17, 2026153 ms
Oct 24, 2026153 ms
Oct 31, 2026148 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 echelonfit.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. echelonfit.com at 0.4 s0.4 s
  2. echelonfit.com at 0.8 s0.8 s
  3. echelonfit.com at 1.1 s1.1 s
  4. echelonfit.com at 1.5 s1.5 s
  5. echelonfit.com at 1.9 s1.9 s
  6. echelonfit.com at 2.3 s2.3 s
  7. echelonfit.com at 2.6 s2.6 s
  8. echelonfit.com at 3.0 s3.0 s

Speed

5 to fix72
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 122 KiB

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

  • Use efficient cache lifetimes

    550 ms · 82 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (82 KiB).

  • 2,749 HTML elements

    The page has 2,749 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 26 KiB

    1 image could be 26 KiB 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 (flash-speed.com, Cloudflare CDN and JSDelivr CDN and others), adding 255 KiB and 50 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Minify CSS

    16 KiB

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 137 ms of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Next gen? We've had it”.

  • Time to Interactive: 11.1 s

    11.1 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.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) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 170 ms

    170 ms

    Real visitors wait 170 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 786 ms

    786 ms

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

  • Cumulative Layout Shift: 0.07

    0.07

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

  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix69
  • Page weight: 2.7 MB in 141 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 141 requests on a phone: images 1.7 MB (70), scripts 590 KiB (39) and fonts 194 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    echelon-fall-hero-bike-animated-v3.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).

  • 1 image far larger than shown

    84 KiB

    1 image is downloaded at several times the size a phone draws it, for example echelon-fall-hero-strength-v4-night.jpg at 1,672 px wide, shown at 390 px. Resized copies would save about 84 KiB.

  • 1 image in older formats

    1 image (484 KiB) 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 0.8 g of CO₂ per visit

    0.77 g

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

Accessibility

7 to fixGoogle 9290
  • ARIA attributes must conform to valid values (5 elements)

    ARIA attributes must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 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 (12 elements)

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

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

  • Alternative text of images should not be repeated as text (27 elements)

    Alternative text of images should not be repeated as text: 27 elements on the page fail this check, rated minor by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 10081
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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 (260 characters)

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

  • 254 internal links, 18 external

    The homepage links to 254 pages on echelonfit.com and 18 external pages.

5 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “Home Exercise Equipment | Echelon – Echelon Fit US”.

  • Canonical URL set

    The canonical URL is https://echelonfit.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://echelonfit.com/sitemap.xml.

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.

  • No llms.txt

    There is no https://echelonfit.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.

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

Other pages

2 to fix93
  • 3 pages share a meta description

    https://echelonfit.com/pages/truemed, https://echelonfit.com/collections/pilates and https://echelonfit.com/collections/stair-climber use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://echelonfit.com/pages/truemed has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

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

Best practices

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

2 checks passed
  • Tap targets are thumb-sized

    132 of 146 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 1,642 words of copy

    The homepage carries about 1,642 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL AN EXPERT 855-4-GETFIT” and “SCHEDULE A FREE DEMO”.

  • 50 calls to action

    The homepage has 50 calls to action, for example “CALL AN EXPERT855-4-GETFIT”, “SCHEDULE A FREE DEMO” and “SHOP ALL TREADMILLS”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 10 trust badges and “2M+ Active Riders”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, The Trade Desk and Xandr (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 echelonfit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Lucky Orange · Impact Com · Triplewhale · Selleasy · Applovin Shop Integration · Restockrocket · rechargecdn.com · avada.io · optimonk.com · pepperjam.com · govx.com · breadgateway.net · bazaarvoice.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Hiring

Hiring
9 open roles
Teams
Content (3), FAO (2), Support (2), International (1)
Job board
rippling

Company

Headquarters
Chattanooga

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on echelonfit.com, including 9 speed issues and 3 SEO issues. 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