Website review, no card needed
tcb.org website review
Visit site (opens in a new tab)Reviewed 20 November 202654 issues · 90 checks
This review found 54 issues worth fixing on tcb.org, 23 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 227 ms |
| Jun 6, 2026 | 226 ms |
| Jun 13, 2026 | 227 ms |
| Jun 20, 2026 | 231 ms |
| Jun 27, 2026 | 236 ms |
| Jul 4, 2026 | 246 ms |
| Jul 11, 2026 | 248 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 230 ms |
| Aug 1, 2026 | 223 ms |
| Aug 8, 2026 | 238 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 227 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 224 ms |
| Sep 12, 2026 | 230 ms |
| Sep 19, 2026 | 243 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 255 ms |
| Oct 10, 2026 | 260 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 271 ms |
| Oct 31, 2026 | 233 ms |
| Nov 7, 2026 | 213 ms |
| Nov 14, 2026 | 204 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
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Use efficient cache lifetimes
13.6 s · 7.2 MB168 files are served with short cache lifetimes, so returning visitors download them again (7.2 MB).
Reduce unused JavaScript
5.2 s · 5.1 MBAbout 5.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.
Render-blocking requests
8.6 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.6 s.
Reduce unused CSS
6.6 s · 1.2 MBAbout 1.2 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Minify CSS
1.1 s · 221 KiB221 KiB could be saved by minifying CSS.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,602 HTML elements
The page has 4,602 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
700 ms · 4.3 MB13 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (botframework.com, Hubspot and weglot.com and others), adding 3.2 MB and 1.5 s of main-thread time.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 741 ms. During a long task the page ignores taps.
botframework.com adds 590 ms
590 msbotframework.com costs a phone 590 ms of main-thread work and 940 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.
Minify JavaScript
320 ms · 163 KiB163 KiB could be saved by minifying JavaScript.
Legacy JavaScript
350 ms · 61 KiBPolyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Document request latency
299 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Hubspot adds 234 ms
234 msHubspot costs a phone 234 ms of main-thread work and 404 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.
Google CDN adds 115 ms
115 msGoogle CDN costs a phone 115 ms of main-thread work and 352 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.
imagedelivery.net adds 0 ms
0 msimagedelivery.net costs a phone 0 ms of main-thread work and 1.0 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 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: 142 ms
142 msYour server sent the HTML in 142 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 11.1 s
11.1 sThe first text or image appears after 11.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 37.3 s
37.3 sYour largest element takes 37.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Explore the New Data Central Turn Trusted Data Into Better …”.
Time to Interactive: 102.8 s
102.8 sThe page becomes fully interactive after 102.8 s. Good is under 3.8 s.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 227 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.091
0.091The layout barely moves while loading (CLS 0.091, good is under 0.1).
Images and page weight
Page weight: 27.8 MB in 281 requests
27.8 MBYour homepage downloads 27.8 MB in 281 requests on a phone: images 17.6 MB (138), scripts 8.1 MB (36) and stylesheets 1.2 MB (15). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 7.3 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.1 MB1 image is downloaded at several times the size a phone draws it, for example 1182777182.jpg at 5,000 px wide, shown at 100 px. Resized copies would save about 1.1 MB.
10 images in older formats
10 images (8.0 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.
2 images below the first screen load straight away
2 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.9 g of CO₂ per visit
7.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.87 g of CO₂e: 943.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
185 images without alt text
185 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (91 elements)
All page content should be contained by landmarks: 91 elements on the page fail this check, rated moderate by axe-core.
101 links without text
101 visible links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
42 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: 42 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Explore the New Data Central”, “Navigating AI” and “Peer Networks. Actionable Insights. Trusted Exper…”). One clear main headline is easier for people and search engines.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
774 internal links, 22 external
The homepage links to 774 pages on tcb.org and 22 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “The Conference Board is the global, nonprofit think tank and business membership organization that delivers Trusted Ins…”.
Title: 58 characters
Your title is a healthy 58 characters: “The Conference Board | Trusted Insights for What's Ahead ®”.
Canonical URL set
The canonical URL is https://www.conference-board.org/north-america/index.cfm.
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://www.conference-board.org/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (4,499 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.conference-board.org/llms.txt (19 KiB, 99 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 192 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.conference-board.org/images/home/latestinsights/28/160306505.jpg.
14 small tap targets
14 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
9 distorted images
9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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 1,451 words of copy
The homepage carries about 1,451 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: “LEARN MORE” and “REGISTER”.
21 calls to action
The homepage has 21 calls to action, for example “Apply to a Council”, “Contact Us” and “Download TCB Insights App”.
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and HubSpot.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 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.
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 tcb.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on tcb.org, including 28 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.