Website review, no card needed

bombora.com logo

bombora.com website review

Visit site (opens in a new tab)Reviewed 28 October 202630 issues · 74 checks

This review found 30 issues worth fixing on bombora.com, 11 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
2.8 s1.8 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.5 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
231 ms133 msMay 9Oct 24218 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026163 ms
May 16, 2026163 ms
May 23, 2026157 ms
May 30, 2026145 ms
Jun 6, 2026144 ms
Jun 13, 2026148 ms
Jun 20, 2026146 ms
Jun 27, 2026150 ms
Jul 4, 2026146 ms
Jul 11, 2026159 ms
Jul 18, 2026173 ms
Jul 25, 2026171 ms
Aug 1, 2026198 ms
Aug 8, 2026182 ms
Aug 15, 2026169 ms
Aug 22, 2026183 ms
Aug 29, 2026188 ms
Sep 5, 2026209 ms
Sep 12, 2026212 ms
Sep 19, 2026220 ms
Sep 26, 2026206 ms
Oct 3, 2026189 ms
Oct 10, 2026205 ms
Oct 17, 2026207 ms
Oct 24, 2026218 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 bombora.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bombora.com at 0.5 s0.5 s
  2. bombora.com at 1.0 s1.0 s
  3. bombora.com at 1.5 s1.5 s
  4. bombora.com at 1.9 s1.9 s
  5. bombora.com at 2.4 s2.4 s
  6. bombora.com at 2.9 s2.9 s
  7. bombora.com at 3.4 s3.4 s
  8. bombora.com at 3.9 s3.9 s

Speed

7 to fix55
  • Render-blocking requests

    4.0 s

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

  • Improve image delivery

    1.1 s · 734 KiB

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

  • Reduce unused JavaScript

    1.2 s · 214 KiB

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

  • Mobile performance score: 55

    55/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, datagrail.io and JSDelivr CDN and others), adding 841 KiB and 634 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 130 KiB

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

  • Google Tag Manager adds 496 ms

    496 ms

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    38 KiB

    About 38 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

12 to fix33
  • 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: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Time to Interactive: 10.9 s

    10.9 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 232 ms

    232 ms

    Real visitors wait 232 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +30%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 63 images without width and height

    63 images have no width and height attributes, so the layout jumps as each one loads.

  • Total Blocking Time: 251 ms

    251 ms

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix60
  • Page weight: 10.7 MB in 63 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 63 requests on a phone: media 8.7 MB (3), images 1.2 MB (28) and scripts 738 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    maxresdefault.jpg 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).

  • 4 images far larger than shown

    195 KiB

    4 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,534 px wide, shown at 390 px. Resized copies would save about 195 KiB.

  • 1 image in older formats

    1 image (59 KiB) is 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 below the first screen load straight away

    1 image further down the page (100 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.05 g

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

Accessibility

100
1 checks passed
  • Every image has alt text

    All 63 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10096
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 82 internal links, 10 external

    The homepage links to 82 pages on bombora.com and 10 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Elevate GTM results with the leader in B2B Intent, identity, and digital audience solutions. Built for enterprise brand…”.

  • One H1 headline

    Your main headline reads: “Bombora is the true pioneer in B2B data. Amplify your marketing and sales motions with industry-leading Intent, identit…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Bombora | B2B data provider for Intent, audience and identity”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://bombora.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17391086&tm=gtm002&Ver=2&mid=91fc3e61-cea1-4d09-ae32-d4542f6dd30b&bo=3&sid=473e0d90d30d11f18598ed9c0b254328&vid=473e6620d30d11f1aa2dfd394af8d9e9&vids=1&msclkid=N&pi=91.

  • 2 small tap targets

    2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 547 words of visible text.

4 checks passed
  • 2 calls to action

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

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 30 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (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.

  • 19 cookies set on arrival

    19

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

  • 46 other companies contacted

    Loading the homepage contacts 46 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 bombora.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 Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on bombora.com, including 19 speed issues, 2 SEO issues and 2 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