Website review, no card needed

tboneadvisory.com logo

tboneadvisory.com website review

Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 59 checks

This review found 24 issues worth fixing on tboneadvisory.com, 4 of them high impact, across 59 checks. The most urgent: use efficient cache lifetimes. 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 tboneadvisory.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tboneadvisory.com at 0.6 s0.6 s
  2. tboneadvisory.com at 1.2 s1.2 s
  3. tboneadvisory.com at 1.8 s1.8 s
  4. tboneadvisory.com at 2.4 s2.4 s
  5. tboneadvisory.com at 3.0 s3.0 s
  6. tboneadvisory.com at 3.6 s3.6 s
  7. tboneadvisory.com at 4.2 s4.2 s
  8. tboneadvisory.com at 4.8 s4.8 s

Speed

7 to fix85
  • Use efficient cache lifetimes

    1.4 s · 3.6 MB

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

  • Render-blocking requests

    1.7 s

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

  • Improve image delivery

    2.4 MB

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

  • Mobile performance score: 85

    85/100

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

  • Reduce unused CSS

    450 ms · 80 KiB

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

  • Font display

    350 ms

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

  • Google Tag Manager adds 266 ms

    266 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Fonts and others), adding 423 KiB and 268 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    144 KiB

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

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 126 ms

    126 ms

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

Core Web Vitals

5 to fix88
  • Time to Interactive: 7.1 s

    7.1 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We enable startups to take bolder leaps by bypassing the co…”. Most of its time is element render delay (1.7 s).

  • Speed Index: 4.1 s

    4.1 s

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

  • 1 image without width and height

    1 image 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: 102 ms

    102 ms

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

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

3 to fix50
  • Page weight: 4.1 MB in 53 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 53 requests on a phone: images 3.2 MB (6), scripts 406 KiB (15) and fonts 268 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (900 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.

  • 1 image far larger than shown

    315 KiB

    1 image is downloaded at several times the size a phone draws it, for example Frame-1-3-circle.png at 600 px wide, shown at 80 px. Resized copies would save about 315 KiB.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9597
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

5 to fixGoogle 8581
  • Title is short (29 characters)

    Your title is only 29 characters: “SaaS Growth Advisory | T-Bone”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at tboneadvisory.com/robots.txt, the first file search crawlers ask for.

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

5 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “We enable startups to take bolder leaps by bypassing the common hurdles, allowing you to manage the unpredictable and b…”.

  • One H1 headline

    Your main headline reads: “SaaS Growth Advisory”.

  • Canonical URL set

    The canonical URL is https://www.tboneadvisory.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.

AI search readiness

100
  • No llms.txt

    There is no https://www.tboneadvisory.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
  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    9 of 10 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
  • 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 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 400 words of copy

    The homepage carries about 400 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”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 1 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 tboneadvisory.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
Analytics
Google Analytics
Hosting
One.com A/S

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on tboneadvisory.com, including 12 speed issues, 5 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