Website review, no card needed

3circlepartners.com logo

3circlepartners.com website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 75 checks

This review found 37 issues worth fixing on 3circlepartners.com, 15 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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 3circlepartners.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix53
  • Reduce unused JavaScript

    4.9 s · 1.2 MB

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

  • Render-blocking requests

    3.5 s

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

  • Improve image delivery

    3.5 MB

    9 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and hsappstatic.net and others), adding 2.1 MB and 998 ms of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Google CDN adds 444 ms

    444 ms

    Google CDN costs a phone 444 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.

  • Use efficient cache lifetimes

    300 ms · 113 KiB

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

  • Google Tag Manager adds 329 ms

    329 ms

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

    300 ms · 60 KiB

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

  • Main-thread work: 2.6 s

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

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

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

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

    48 ms

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

Core Web Vitals

5 to fix64
  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Belbin helps teams understand how people contribute, uncove…”.

  • Speed Index: 12.9 s

    12.9 s

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

  • Time to Interactive: 20.6 s

    20.6 s

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

  • 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
  • Total Blocking Time: 179 ms

    179 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 9.7 MB in 154 requests

    9.7 MB

    Your homepage downloads 9.7 MB in 154 requests on a phone: images 6.6 MB (33), scripts 2.2 MB (44) and other files 377 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    5.3 MB

    14 images are downloaded at several times the size a phone draws them, for example ClientLogos.png at 2,256 px wide, shown at 350 px. Resized copies would save about 5.3 MB.

  • 4 images over 500 KB

    4 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 16 images in older formats

    16 images (6.2 MB) 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.

  • 14 images below the first screen load straight away

    14 images further down the page (6.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.7 g of CO₂ per visit

    2.75 g

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

Accessibility

6 to fixGoogle 9392
  • 17 text elements with low contrast

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

  • [role="img"] and [role="image"] elements must have alternative text (8 elements)

    [role="img"] and [role="image"] elements must have alternative text: 8 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

  • 3 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10083
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Official Belbin Site For North America - Belbin Team Role and Training”.

  • 44 internal links, 6 external

    The homepage links to 44 pages on 3circlepartners.com and 6 external pages.

6 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Belbin is a research-based methodology that is used worldwide to help individuals and teams improve business performanc…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

4 to fix53
  • 9 linked pages are broken

    Your homepage links to https://belbinnorthamerica.com/clients, https://belbinnorthamerica.com/accreditation, https://belbinnorthamerica.com/individual-reports, https://belbinnorthamerica.com/team-reports, https://belbinnorthamerica.com/team-collaboration-mapping and https://belbinnorthamerica.com/workshop-solutions and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://belbinnorthamerica.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://belbinnorthamerica.com/home all use the title “Official Belbin Site For North America - Belbin Team Role and Training”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://belbinnorthamerica.com/home 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 17 found) and read each the way a search engine does.

3 checks passed
  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'value')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

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

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

    The homepage carries about 840 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Shop All Products” and “Start with an Individual Report →”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, HubSpot and LinkedIn Insight.

  • Direct contact links

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

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, LinkedIn Insight 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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 4 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.

  • 22 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
AWS

Company

Headquarters
Marysville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on 3circlepartners.com, including 15 speed issues, 2 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