Website review, no card needed

eastonbjj.com logo

eastonbjj.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 82 checks

This review found 31 issues worth fixing on eastonbjj.com, 9 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
3.3 s1.8 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20262.8 s
Jul 11, 20262.6 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
164 ms111 msMay 2Oct 17158 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026123 ms
May 9, 2026121 ms
May 16, 2026119 ms
May 23, 2026119 ms
May 30, 2026118 ms
Jun 6, 2026117 ms
Jun 13, 2026121 ms
Jun 20, 2026122 ms
Jun 27, 2026121 ms
Jul 4, 2026122 ms
Jul 11, 2026121 ms
Jul 18, 2026118 ms
Jul 25, 2026118 ms
Aug 1, 2026119 ms
Aug 8, 2026121 ms
Aug 15, 2026125 ms
Aug 22, 2026124 ms
Aug 29, 2026127 ms
Sep 5, 2026126 ms
Sep 12, 2026130 ms
Sep 19, 2026135 ms
Sep 26, 2026138 ms
Oct 3, 2026146 ms
Oct 10, 2026154 ms
Oct 17, 2026158 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 eastonbjj.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eastonbjj.com at 0.5 s0.5 s
  2. eastonbjj.com at 0.9 s0.9 s
  3. eastonbjj.com at 1.4 s1.4 s
  4. eastonbjj.com at 1.8 s1.8 s
  5. eastonbjj.com at 2.3 s2.3 s
  6. eastonbjj.com at 2.7 s2.7 s
  7. eastonbjj.com at 3.2 s3.2 s
  8. eastonbjj.com at 3.6 s3.6 s

Speed

8 to fix52
  • Improve image delivery

    4.5 s · 1.6 MB

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

  • Render-blocking requests

    2.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and ksrndkehqnwntyxlhgto.com and others), adding 1.5 MB and 1.1 s of main-thread time.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 731 ms

    731 ms

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

  • Reduce unused JavaScript

    757 KiB

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

  • Main-thread work: 2.1 s

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

  • 1,854 HTML elements

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

  • Use efficient cache lifetimes

    226 KiB

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

  • Reduce unused CSS

    150 ms · 46 KiB

    About 46 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.

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • 13 long tasks on the main thread

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

  • Minify JavaScript

    25 KiB

    25 KiB could be saved by minifying JavaScript.

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

    7 ms

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

Core Web Vitals

8 to fix100
  • 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: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Jiu Jitsu at Easton”.

  • Time to Interactive: 16.4 s

    16.4 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

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

    +28%

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 523 ms

    523 ms

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

  • Speed Index: 4.3 s

    4.3 s

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 157 ms

    157 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

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

    -35%

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

  • Cumulative Layout Shift: 0.09

    0.09

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

Images and page weight

3 to fix53
  • Page weight: 5.0 MB in 74 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 74 requests on a phone: images 3.3 MB (23), scripts 1.6 MB (30) and fonts 83 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    muay-thai.avif 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).

  • 3 images far larger than shown

    337 KiB

    3 images are downloaded at several times the size a phone draws them, for example muay-thai.avif at 1,400 px wide, shown at 332 px. Resized copies would save about 337 KiB.

  • 2 images in older formats

    2 images (281 KiB) 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.

  • About 1.4 g of CO₂ per visit

    1.43 g

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

Accessibility

3 to fixGoogle 9596
  • 41 text elements with low contrast

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 checks passed
  • Every image has alt text

    All 55 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

2 to fixGoogle 9283
  • No meta description

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

  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Brazilian Jiu Jitsu, Muay Thai & Kickboxing in Colorado | Easton Training Center”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 176 internal links, 6 external

    The homepage links to 176 pages on eastonbjj.com and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “You’ve thought abouttrying martial artsfor years.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,330 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://eastonbjj.com/members is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://eastonbjj.com/free-class has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://eastonbjj.com/free-class has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://eastonbjj.com/kickboxing, https://eastonbjj.com/muay-thai and https://eastonbjj.com/locations took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 986 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ADULTS JIU JITSU START ON THE GROUND”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Try a Free Class”, “Book a Free Trial Class” and “Book a Free Class”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, a star rating and “1,000+ reviews”.

  • Analytics in place

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

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, Meta Pixel and Microsoft Clarity (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.

  • 14 cookies set on arrival

    14

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

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on eastonbjj.com, including 16 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

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