Website review, no card needed

180fitnesstraining.com logo

180fitnesstraining.com website review

Visit site (opens in a new tab)Reviewed 19 November 202628 issues · 67 checks

This review found 28 issues worth fixing on 180fitnesstraining.com, 8 of them high impact, across 67 checks. The most urgent: 9 pages without a title. 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 180fitnesstraining.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix66
  • Mobile performance score: 66

    66/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Facebook, leadconnectorhq.com and Cloudflare and others), adding 1.8 MB and 291 ms of main-thread time.

  • Improve image delivery

    326 KiB

    14 images could be 326 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • leadconnectorhq.com adds 85 ms

    85 ms

    leadconnectorhq.com costs a phone 85 ms of main-thread work and 1.2 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.

  • Google Fonts adds 7 ms

    7 ms

    Google Fonts costs a phone 7 ms of main-thread work and 364 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.

  • Reduce unused JavaScript

    245 KiB

    About 245 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    198 KiB

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

5 to fix55
  • Cumulative Layout Shift: 0.564

    0.564

    The layout shifts by 0.564 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

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

  • Total Blocking Time: 240 ms

    240 ms

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

  • 11 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Speed Index: 2.4 s

    2.4 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    6ab6d315ea346ddd6228cb17.png 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).

  • About 0.5 g of CO₂ per visit

    0.52 g

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

3 checks passed
  • Page weight: 1.8 MB in 93 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 93 requests on a phone: images 684 KiB (21), scripts 660 KiB (46) and fonts 436 KiB (11). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9393
  • 7 text elements with low contrast

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

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (14 elements)

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

7 to fixGoogle 8250
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (Person, Service and WebPage) but with 1 problem, for example “Service: no offers (price) block”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 11 internal links, 10 external

    The homepage links to 11 pages on 180fitnesstraining.com and 10 external pages.

1 checks passed
  • 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.

  • No llms.txt

    There is no https://180fitnesstraining.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 (494 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix71
  • 9 pages without a title

    https://180fitnesstraining.com/home, https://180fitnesstraining.com/meet-terrie, https://180fitnesstraining.com/online-classes-191108, https://180fitnesstraining.com/online-classes, https://180fitnesstraining.com/online-zoom-class-schedule and https://180fitnesstraining.com/class-pricing and 3 others have no <title>, so Google invents the link text in results.

  • 9 pages without a meta description

    https://180fitnesstraining.com/home, https://180fitnesstraining.com/meet-terrie, https://180fitnesstraining.com/online-classes-191108, https://180fitnesstraining.com/online-classes, https://180fitnesstraining.com/online-zoom-class-schedule and https://180fitnesstraining.com/class-pricing and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://180fitnesstraining.com/home, https://180fitnesstraining.com/meet-terrie, https://180fitnesstraining.com/online-classes-191108, https://180fitnesstraining.com/online-classes, https://180fitnesstraining.com/online-zoom-class-schedule and https://180fitnesstraining.com/class-pricing and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://180fitnesstraining.com/meet-terrie, https://180fitnesstraining.com/online-classes-191108, https://180fitnesstraining.com/online-classes, https://180fitnesstraining.com/online-zoom-class-schedule, https://180fitnesstraining.com/class-pricing and https://180fitnesstraining.com/denise-v have 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.

  • 9 internal pages checked

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

3 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 465 words of copy

    The homepage carries about 465 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK A CHAT WITH ME”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Class Pricing” and “BOOK A CHAT WITH ME”.

  • Analytics in place

    Analytics detected: Meta Pixel and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 180fitnesstraining.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on 180fitnesstraining.com, including 10 speed issues, 7 SEO issues and 1 conversion gap. 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