tbri.com website review

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

90 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

6 images could be 515 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

Your mobile performance score is 46 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Hello Bar and others), adding 3.6 MB and 1.4 s of main-thread time.

YouTube costs a phone 766 ms of main-thread work and 1.9 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.

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

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

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

Hello Bar costs a phone 97 ms of main-thread work and 921 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.

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

9 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 32.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TBR Insight Center™”.

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

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

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

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

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.

Your homepage downloads 5.0 MB in 159 requests on a phone: scripts 2.7 MB (43), images 1.6 MB (20) and stylesheets 269 KiB (55). Under 2 MB keeps phones on slow connections fast.

The_Strategic_Bets_that__Will_Drive_IT_Services_Growth_and_I weighs 724 KiB. On a phone connection a single image that size takes seconds.

6 images (1.4 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.

4 images further down the page (570 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

10 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: 19 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.

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

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

Structured data found (BreadcrumbList, ImageObject, Organization and Person) but with 8 problems, for example “Organization: image is not an absolute URL ("https://tbri.com/wp-content/uploads/2024/12/Ecosystems-Refresh-2025-Ta…”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 44 pages on tbri.com and 23 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

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

https://tbri.com/competitive-intelligence-insights-analysis and https://tbri.com/competitive-intelligence-insights-analysis/the-blog are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://tbri.com/competitive-and-market-intelligence-research-portal-2 and https://tbri.com/ai-disruption-within-the-technology-industry have no <h1> headline, so visitors and search engines get no clear main topic.

https://tbri.com/cloud-and-software-competitive-intelligence, https://tbri.com/devices-competitive-intelligence, https://tbri.com/it-infrastructure-competitive-intelligence, https://tbri.com/professional-services-competitive-intelligence, https://tbri.com/tailored-services and https://tbri.com/who-uses-tbr and 2 others took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 674 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

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