Skip to content
https://bloomberry.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Checks
9
6 PASS 2 REVIEW 1 FIX
F
Image Optimization
Action
5 issues found across 17 images
FIX
5 issues found across 17 images
Warning::
14 images significantly larger than display size
Resizing to display dimensions could save approximately 0 KB.
Got: ~0 KB wasted
Warning::
3 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
17 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 17 images use legacy formats (JPEG/PNG/GIF)
WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
Info::
2 image(s) wider than 400px without srcset (no responsive serving)
These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://bloomberry.com/blog/wp-content/uploads/2026/01/Screenshot-2026-01-04-134207.png, https://bloomberry.com/blog/wp-content/uploads/2026/01/Screenshot-2026-01-04-144207.png.
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

66/100

Site name appears as

Page titleReal-Time Technographic Data & API
og:site_name—
twitter:site—
Organization.nameBloomberry

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

10/10

contact page + mailto link

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • twitter:card missing
  • Consider adding contactPoint — helps appear in "contact us" rich results

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
A
Open Graph
Open Graph tags are well configured for social sharing.
PASS
Open Graph tags are well configured for social sharing.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

bloomberry.com

Bloomberry - Real-Time Technographic Data & API

Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.

Preview quality · Twitter/X D · 50/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — falling back from og:image
  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

BLOOMBERRY.COM

Bloomberry - Real-Time Technographic Data & API

Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.

Preview quality · Facebook A · 85/100
  • og:title — Bloomberry - Real-Time Technographic Data & API
  • og:description — Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.
  • og:image — https://bloomberry.com/blog/wp-content/uploads/2025/10/bloomberry_logo.svg
  • og:type — website
  • og:url — https://bloomberry.com/
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

Bloomberry - Real-Time Technographic Data & API

bloomberry.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — Bloomberry - Real-Time Technographic Data & API
  • og:description — Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.
  • og:image — https://bloomberry.com/blog/wp-content/uploads/2025/10/bloomberry_logo.svg

bloomberry.com

Bloomberry - Real-Time Technographic Data & API

Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.

Preview quality · Slack A+ · 100/100
  • og:title — Bloomberry - Real-Time Technographic Data & API
  • og:description — Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products.
  • og:image — https://bloomberry.com/blog/wp-content/uploads/2025/10/bloomberry_logo.svg

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

B · 83/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
A+
Open Graph / Twitter Card Depth
OG image dimensions and Twitter card configuration look healthy
PASS
OG image dimensions and Twitter card configuration look healthy
Info::
OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid
A+
Structured Data
3 JSON-LD block(s) found — structured data is well configured.
PASS
3 JSON-LD block(s) found — structured data is well configured.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
Missing recommended property "potentialAction" for WebSite
Adding "potentialAction" can improve how search engines display your content.
Info::
3 JSON-LD blocks found

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "potentialAction" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : Organization
8 properties Valid
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Bloomberry",
  "url": "https://bloomberry.com",
  "logo": "https://bloomberry.com/blog/wp-content/uploads/2025/10/bloomberry_logo.svg",
  "description": "Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products. It reads infrastructure signals - what a company sets up when it buys software - rather than website tags or job postings.",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "New York",
    "addressRegion": "NY",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://x.com/bloomberry"
  ]
}
Block 2 : WebSite
4 properties Valid
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Bloomberry",
  "url": "https://bloomberry.com"
}
Block 3 : FAQPage
3 properties Valid
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Where does your data come from, and how is it different from BuiltWith, Wappalyzer or TheirStack?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Bloomberry tells you which companies just started or stopped paying for any of 1,700+ B2B products. It reads infrastructure signals - what a company sets up when it buys software - rather than website tags or job postings. Concretely, that means new subdomains, DNS records, certificate transparency logs, and signals specific to how each individual product gets deployed. We crawl websites too, but we go further than checking whether a tag exists - we read the configuration inside script files and check whether they still return a working response. We've built a separate detector for each of the 1,700+ products we cover, so we know what that particular product looks like when it's set up, and we can confirm when it's gone. That's why we can tell you when a company subscribed or churned, not just what's on their website today. Some of those signals only appear when a product is genuinely deployed. Rolling out an AI assistant or an ERP across an organization usually means verifying a domain for single sign-on or updating email records - public changes that a single seat or a free trial never produces. So when we report an adoption, it generally reflects a real organizational rollout. Website scanning tells you presence, not timing, and skews toward front-end technologies. Job postings tell you what a company wrote in a job ad, which is why TheirStack scores how likely it is that the company actually uses what it mentioned. We don't use job postings, vendor case studies or product reviews - they're indirect and they lag. Because we're not limited to website tags, we also cover backoffice products with no website footprint at all: AI products (ie ChatGPT, Claude, Cursor), CRMs (ie Salesforce and Hubspot), project management tools (Jira, Monday) and much more."
      }
    },
    {
      "@type": "Question",
      "name": "Why do you cover fewer products than BuiltWith or TheirStack?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Because we build a separate detection method for each product we cover. Depending on the vendor, that can mean watching for a new subdomain to resolve, reading DNS records, or checking a signal specific to how that one product works. Catalogs with tens of thousands of entries get there by running a single generic check across every JavaScript library, tag and framework on the internet - most of which nobody sells against. We cover the 1,700+ B2B products GTM teams actually build territory and displacement plays around, and for each one we tell you when a company started or stopped paying. We also don't call it churn just because a tag disappeared: we verify the endpoint is genuinely dead first, so a site redesign doesn't show up as a lost customer."
      }
    },
    {
      "@type": "Question",
      "name": "Can you tell me which companies just adopted AI tools?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We track adoption and churn for AI products the same way we track everything else, with dates attached - including ChatGPT, Claude, Cursor and others across our enterprise AI category. So you can ask questions like \"which companies rolled out an AI coding tool in the last 90 days\" rather than just \"who has an AI vendor somewhere in their stack\"."
      }
    },
    {
      "@type": "Question",
      "name": "Do you cover newer tools, or just established ones?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Both, and we add new products continuously. We already track adoption for tools that launched recently - RB2B, Unify, Warmly and similar - alongside established categories like CRM and ERP. Legacy technographic databases are built around one fixed detection method, so newer GTM and AI tools tend to arrive late or not at all. If there's a product you need covered that we don't have yet, tell us and we'll usually add it."
      }
    },
    {
      "@type": "Question",
      "name": "How many product categories does your data cover?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We cover 1,700+ products across 190 categories. We cover a broad range of categories from enterprise AI, CRMs, cybersecurity, learning management, sales intelligence, ERPs, and more. You can explore all our categories here."
      }
    },
    {
      "@type": "Question",
      "name": "How many of these subscribe/churn events do you uncover per month?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Our data consists of over 400,000 events every month."
      }
    },
    {
      "@type": "Question",
      "name": "What are the limitations of your data?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "While we cover a wide range of categories, there are a few niches where we're not as strong such as edtech. In addition, we do not provide data on the person who was in charge of the purchase/churn event. We only provide data on the companies, not contact information of individuals."
      }
    },
    {
      "@type": "Question",
      "name": "Do you have an UI/app or just an API?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Our data is available through both an UI and an API. You can sign up to browse our data or request an API key here. If you're a platform looking to integrate our signals into your own product, see our API documentation."
      }
    },
    {
      "@type": "Question",
      "name": "Can I get a free trial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, please fill out this form and we'll email you login details."
      }
    },
    {
      "@type": "Question",
      "name": "Are you a new company? How come I've never heard of you?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Our company Revealera has sold hiring and technology adoption data to some of the biggest hedge funds for the past 5 years, including 3 of the 20 largest funds in the world. We recently launched Bloomberry to bring that data to a different audience: sales, GTM and ABM teams and platforms."
      }
    }
  ]
}
A+
Rich Results Eligibility
3 JSON-LD block(s) declaring 3 schema type(s)
PASS
3 JSON-LD block(s) declaring 3 schema type(s)
Info::
3 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): FAQPage, Organization, WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback