Catalog / bumble.com
65

SEO audit for bumble.com

Bumble | Date, Chat & Meet New People

other

Health 65/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Bumble has changed the way people date, create meaningful relationships & network with women making the first move. Meet new people & download Bumble.

Screenshot of bumble.com
50
pages crawled
44
indexable pages
0
errors
370
warnings
466
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Links 2 0 164 1
Hreflang 45 0 91 0
Performance 80 0 33 123
Canonical 82 0 30 29
Budget 90 0 16 0
Duplicate 92 0 13 2
Meta Description 97 0 5 1
Headings 98 0 4 2
Content 98 0 3 51
Crawlability 98 0 3 6
Rendering 98 0 3 0
Agent Readiness 99 0 2 8
Images 99 0 2 80
Security 99 0 1 50
Amp 100 0 0 1
Cache 100 0 0 41
Sitemap 100 0 0 10
Social 100 0 0 5
Structured Data 100 0 0 44
Titles 100 0 0 6
URL 100 0 0 6
Findings

Warnings (19 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 2 occurrence(s)

warning robots.txt-disallowed URL receives internal links (crawl-budget leak)

Rule budget.disallow_linked · Budget · 16 occurrence(s)

  • https://bumble.com/es-ar/about — internal links point to https://bumble.com/es-ar/about, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/bff — internal links point to https://bumble.com/es-ar/bff, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/date — internal links point to https://bumble.com/es-ar/date, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/eaa-accessibility-statement — internal links point to https://bumble.com/es-ar/eaa-accessibility-statement, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/guidelines — internal links point to https://bumble.com/es-ar/guidelines, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/help/cancelation-flow — internal links point to https://bumble.com/es-ar/help/cancelation-flow, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-ar/terms — internal links point to https://bumble.com/es-ar/terms, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-ar.
  • https://bumble.com/es-co/about — internal links point to https://bumble.com/es-co/about, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/bff — internal links point to https://bumble.com/es-co/bff, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/date — internal links point to https://bumble.com/es-co/date, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/eaa-accessibility-statement — internal links point to https://bumble.com/es-co/eaa-accessibility-statement, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/guidelines — internal links point to https://bumble.com/es-co/guidelines, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/help/cancelation-flow — internal links point to https://bumble.com/es-co/help/cancelation-flow, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/es-co/terms — internal links point to https://bumble.com/es-co/terms, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/es-co.
  • https://bumble.com/id/help/cancelation-flow — internal links point to https://bumble.com/id/help/cancelation-flow, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/en/help/cancelation-flow, https://bumble.com/en-us/help/cancelation-flow.
  • https://bumble.com/id/terms — internal links point to https://bumble.com/id/terms, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://bumble.com/en-us/terms.

warning Missing canonical tag

Rule canonical.missing · Canonical · 1 occurrence(s)

warning Interior page canonicalizes to the homepage

Rule canonical.points_to_homepage · Canonical · 28 occurrence(s)

  • https://bumble.com/da — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/de — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/en-au — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/en-ca — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/en-in — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/en-us — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/en/ — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/es — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/es-ar — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/es-co — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/es-mx — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/fi — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/fr — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/fr-ca — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/hi — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/id — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/it — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/nb — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/nl — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/pl — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/pt — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/pt-pt — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/ru — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/sv — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://bumble.com/zh — this interior page canonicalizes to the homepage (https://bumble.com/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.

warning Canonical target redirects to another URL

Rule canonical.to_redirect · Canonical · 1 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 3 occurrence(s)

warning Near-duplicate page content

Rule duplicate.near · Duplicate · 10 occurrence(s)

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 1 occurrence(s)

  • https://bumble.com/ — https://www.bumble.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 2 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 4 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 1 occurrence(s)

  • https://bumble.com/privacy-policy/en — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning hreflang set has no self-reference

Rule hreflang.missing_self · Hreflang · 9 occurrence(s)

warning hreflang has no return link (not reciprocal)

Rule hreflang.no_return · Hreflang · 82 occurrence(s)

warning Images missing alt text

Rule images.missing_alt · Images · 2 occurrence(s)

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 33 occurrence(s)

  • https://bumble.com/ — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/da — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/de — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en-au — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en-ca — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en-in — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en-us — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en/ — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/en/about — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fproject-love%2Fassets%2Fabout-hero-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/es — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/es-ar — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/es-co — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/es-mx — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/fi — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/fr — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/fr-ca — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/id — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/it — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/nb — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/nl — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/pl — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/pt — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/pt-pt — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/ru — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://bumble.com/zh — the likely hero/LCP image (https://bumble.com/_next/image/?url=%2Fbumble-brand-assets%2Fhero%2Fanimation-card-1.jpg&w=2560&q=75) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Internal link points to a redirect

Rule links.redirect_target · Links · 164 occurrence(s)

  • https://bumble.com/ — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/ — https://bumble.com/en/about → https://bumble.com/en-gb/about/
  • https://bumble.com/ — https://bumble.com/love-stories → https://bumble.com/love-stories/
  • https://bumble.com/ — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/ — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)
  • https://bumble.com/en-us — https://bumble.com/love-stories → https://bumble.com/love-stories/
  • https://bumble.com/en/ — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/en/ — https://bumble.com/en/about → https://bumble.com/en-gb/about/
  • https://bumble.com/en/ — https://bumble.com/love-stories → https://bumble.com/love-stories/
  • https://bumble.com/en/ — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/en/ — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)
  • https://bumble.com/en/about — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/en/about — https://bumble.com/en/about → https://bumble.com/en-gb/about/
  • https://bumble.com/en/about — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/en/about — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)
  • https://bumble.com/help-search — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/help-search — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/help-search — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)
  • https://bumble.com/help/IRL — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/help/IRL — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/help/IRL — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)
  • https://bumble.com/the-buzz/values-in-a-relationship — https://bumble.com/about → https://bumble.com/en-gb/about/
  • https://bumble.com/unsupported-browser — https://bumble.com/bumble-washington-consumer-health-data-privacy-policy → https://eu1.ecdn2.bumbcdn.com/i/big/documents/consumer-health/bumble_washington_consumer_health_data_privacy_policy_2024.pdf (off-site)
  • https://bumble.com/unsupported-browser — https://bumble.com/modern-slavery-act-statement → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2023/statement-on-modern-slavery-act.pdf (off-site)
  • https://bumble.com/unsupported-browser — https://bumble.com/notice-at-collection → https://eu1.ecdn2.bumbcdn.com/i/big/documents/bumble/2024/bumble_california_notice_at_collection.pdf (off-site)

warning Missing meta description

Rule meta_desc.missing · Meta Description · 5 occurrence(s)

warning Redirect chain (multiple hops)

Rule redirect.chain · Crawlability · 3 occurrence(s)

warning Content only rendered by JavaScript (invisible to non-JS crawlers & AI)

Rule rendering.js_shell · Rendering · 3 occurrence(s)

Notices (32 rules)

notice Invalid ARIA role

Rule agent.aria_invalid_role · Agent Readiness · 4 occurrence(s)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 2 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://bumble.com/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 1 occurrence(s)

notice AMP markup present (no Google Search benefit since Jul 2026)

Rule amp.deprecated · Amp · 1 occurrence(s)

  • https://bumble.com/the-buzz/values-in-a-relationship — this page advertises an AMP variant via <link rel="amphtml"> — Google removed AMP from Search on 1 Jul 2026, so the AMP page earns no ranking or feature benefit. Consider removing the link and 301-redirecting /amp/ URLs to their canonical equivalents.

notice Page served uncached (no-store/private or CDN bypass)

Rule cache.not_cacheable · Cache · 41 occurrence(s)

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 29 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 36 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 15 occurrence(s)

  • https://bumble.com/ — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/?utm_source=bumble-the-buzz-page&utm_medium=web&utm_campaign=bumble_the-buzz_download-cta&utm_id=bumble-the-buzz-download-cta&utm_content=header — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/about — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en-au — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en-ca — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en-in — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en-us — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en-us/help/cancelation-flow — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en/ — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en/about — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/en/help/cancelation-flow — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/id — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/love-stories — this page reads as difficult (Flesch Reading Ease 40, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/the-buzz/tag/relationships — this page reads as very difficult (Flesch Reading Ease 22, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://bumble.com/the-buzz/values-in-a-relationship — this page reads as difficult (Flesch Reading Ease 46, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 2 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 2 occurrence(s)

notice Image alt text is keyword-stuffed (repetition / low variety)

Rule images.alt_stuffed · Images · 11 occurrence(s)

  • https://bumble.com/es-ar — 1 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/es-co — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/es-mx — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/fr — 1 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/fr-ca — 1 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/it — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/nl — 5 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/pl — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/pt — 1 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/pt-pt — 5 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.
  • https://bumble.com/ru — 2 image(s) have keyword-stuffed alt text — the same word repeated several times, or a long low-variety keyword list. Google's image guidance asks for short, descriptive alt text, not keyword lists; rewrite it to describe the image.

notice Image alt text is very long (possible keyword stuffing)

Rule images.alt_too_long · Images · 31 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 7 occurrence(s)

  • https://bumble.com/bumble-honey-ambassadors — the likely hero/LCP image (yh5baeaaaaalaaaaaabaaeaaaibraa7) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/en-us/help/cancelation-flow — the likely hero/LCP image (reg_code.phtml) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/en/help/cancelation-flow — the likely hero/LCP image (reg_code.phtml) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/love-stories — the likely hero/LCP image (svg+xml;base64,phn2zyb4bwxucz0iahr0cdovl3d3dy53my5vcmcvmjawmc9zdmciihdpzhropsiyodgwiibozwlnahq9ije0odaipjwvc3znpg==) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/the-buzz — the likely hero/LCP image (bumble-site-logo.svg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/the-buzz/tag/relationships — the likely hero/LCP image (bumble-site-logo.svg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://bumble.com/the-buzz/values-in-a-relationship — the likely hero/LCP image (bumble-site-logo.svg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 38 occurrence(s)

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 1 occurrence(s)

  • https://bumble.com/love-stories — 1 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 1 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 5 occurrence(s)

notice Large DOM (over 1500 elements) slows rendering & interaction

Rule perf.dom_size_large · Performance · 32 occurrence(s)

  • https://bumble.com/ — the page has 1592 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/da — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/de — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/en-au — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/en-ca — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/en-in — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/en-us — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/en/ — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/es — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/es-ar — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/es-co — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/es-mx — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/fi — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/fr — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/fr-ca — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/id — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/it — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/nb — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/nl — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/pl — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/pt — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/pt-pt — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/ru — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/sv — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://bumble.com/zh — the page has 1595 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 35 occurrence(s)

  • https://bumble.com/ — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/da — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/de — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/en-au — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/en-ca — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/en-in — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/en-us — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/en/ — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/es — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/es-ar — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/es-co — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/es-mx — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/fi — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/fr — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/fr-ca — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/id — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/it — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/nb — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/nl — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/pl — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/pt — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/pt-pt — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/ru — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/the-buzz/values-in-a-relationship — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://bumble.com/zh — 1 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice No ETag header (no conditional GET for unchanged pages)

Rule perf.no_etag · Performance · 6 occurrence(s)

  • https://bumble.com/en-us/help/cancelation-flow — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://bumble.com/en-us/terms — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://bumble.com/en/help/cancelation-flow — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://bumble.com/get-started — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://bumble.com/get-started/?utm_source=bumble-the-buzz-page&utm_medium=web&utm_campaign=bumble_the-buzz_sign_in&utm_id=bumble-the-buzz-sign-in&utm_content=header — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
  • https://bumble.com/get-started?pid=bumble-new-buzz — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 43 occurrence(s)

  • https://bumble.com/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/da — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/de — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en-au — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en-ca — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en-in — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en-us — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/en/about — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/es — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/es-ar — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/es-co — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/es-mx — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/fr — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/fr-ca — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/get-started — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/id — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/it — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/nb — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/nl — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/pl — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/pt — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/ru — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/the-buzz/values-in-a-relationship — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://bumble.com/zh — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice URL redirects to another URL

Rule redirect.single · Crawlability · 6 occurrence(s)

notice No structured data detected

Rule schema.none · Structured Data · 44 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 41 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 9 occurrence(s)

  • https://bumble.com/bumble-honey-ambassadors — 5 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/en-us/help/cancelation-flow — 2 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/en-us/terms — 2 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/en/help/cancelation-flow — 2 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/love-stories — 4 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/privacy-policy/en — 3 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/the-buzz — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/the-buzz/tag/relationships — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://bumble.com/the-buzz/values-in-a-relationship — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 10 occurrence(s)

notice Title tag is identical to the H1 (missed keyword variation)

Rule title.same_as_h1 · Titles · 2 occurrence(s)

notice Title is very short

Rule title.too_short · Titles · 4 occurrence(s)

notice Many query parameters

Rule url.many_params · URL · 2 occurrence(s)

notice URL is very long

Rule url.too_long · URL · 2 occurrence(s)

notice Uppercase letters in URL path

Rule url.uppercase · URL · 2 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://bumble.com/
Bumble | Date, Chat & Meet New People		 200 yes 410 38
https://bumble.com/get-started
Bumble | Date, Chat, Meet New People & Network Better		 200 yes 0 37
https://bumble.com/en-us
Bumble | Date, Chat & Meet New People		 200 yes 413 34
https://bumble.com/the-buzz
Bumble Buzz		 200 yes 1911 36
https://bumble.com/en/
Bumble | Date, Chat & Meet New People		 200 yes 413 34
https://bumble.com/hi
Bumble | Date, Chat & Meet New People		 200 yes 476 33
https://bumble.com/da
Bumble | Date, Chat & Meet New People		 200 yes 423 32
https://bumble.com/de
Bumble | Date, Chat & Meet New People		 200 yes 405 32
https://bumble.com/en-au
Bumble | Date, Chat & Meet New People		 200 yes 413 32
https://bumble.com/en-ca
Bumble | Date, Chat & Meet New People		 200 yes 413 32
https://bumble.com/en-in
Bumble | Date, Chat & Meet New People		 200 yes 413 32
https://bumble.com/es
Bumble | Date, Chat & Meet New People		 200 yes 454 32
https://bumble.com/es-ar
Bumble | Date, Chat & Meet New People		 200 yes 443 32
https://bumble.com/es-co
Bumble | Date, Chat & Meet New People		 200 yes 453 32
https://bumble.com/es-mx
Bumble | Date, Chat & Meet New People		 200 yes 453 32
https://bumble.com/fi
Bumble | Date, Chat & Meet New People		 200 yes 353 32
https://bumble.com/fr
Bumble | Date, Chat & Meet New People		 200 yes 457 32
https://bumble.com/fr-ca
Bumble | Date, Chat & Meet New People		 200 yes 449 32
https://bumble.com/id
Bumble | Date, Chat & Meet New People		 200 yes 413 32
https://bumble.com/it
Bumble | Date, Chat & Meet New People		 200 yes 425 32
https://bumble.com/ja
Bumble | Date, Chat & Meet New People		 200 yes 201 32
https://bumble.com/ko
Bumble | Date, Chat & Meet New People		 200 yes 365 32
https://bumble.com/nb
Bumble | Date, Chat & Meet New People		 200 yes 416 32
https://bumble.com/nl
Bumble | Date, Chat & Meet New People		 200 yes 410 32
https://bumble.com/pl
Bumble | Date, Chat & Meet New People		 200 yes 426 32
https://bumble.com/pt
Bumble | Date, Chat & Meet New People		 200 yes 432 32
https://bumble.com/pt-pt
Bumble | Date, Chat & Meet New People		 200 yes 448 32
https://bumble.com/ru
Bumble | Date, Chat & Meet New People		 200 yes 401 32
https://bumble.com/sv
Bumble | Date, Chat & Meet New People		 200 yes 415 32
https://bumble.com/zh
Bumble | Date, Chat & Meet New People		 200 yes 209 32
https://bumble.com/zh-Hant
Bumble | Date, Chat & Meet New People		 200 yes 235 32
https://bumble.com/love-stories
Bumble Love Stories: Real Couples Who Matched | Bumble		 200 yes 354 30
https://bumble.com/en-us/terms
Bumble - terms		 200 yes 14419 9
https://bumble.com/bumble-honey-ambassadors
Bumble | BFF Ambassadors		 200 yes 272 7
https://bumble.com/en/about
About - Bumble | Date, Chat & Meet New People		 200 yes 550 11
https://bumble.com/privacy-policy/en
Bumble Privacy Policy		 200 yes 12018 10
https://bumble.com/en/help/cancelation-flow
Help		 200 yes 895 8
https://bumble.com/?utm_source=bumble-the-buzz-page&utm_medium=web&utm_campaign=bumble_the-buzz_download-cta&utm_id=bumble-the-buzz-download-cta&utm_content=header
Bumble | Date, Chat & Meet New People		 200 yes 410 3
https://bumble.com/about
About - Bumble | Date, Chat & Meet New People		 200 yes 550 3
https://bumble.com/get-started/?utm_source=bumble-the-buzz-page&utm_medium=web&utm_campaign=bumble_the-buzz_sign_in&utm_id=bumble-the-buzz-sign-in&utm_content=header
Bumble | Date, Chat, Meet New People & Network Better		 200 yes 0 3
https://bumble.com/get-started?pid=bumble-new-buzz
Bumble | Date, Chat, Meet New People & Network Better		 200 yes 0 3
https://bumble.com/the-buzz/tag/relationships
Relationships Archives - Bumble Buzz		 200 yes 384 3
https://bumble.com/en-us/help/cancelation-flow
Help		 200 yes 899 3
https://bumble.com/the-buzz/values-in-a-relationship
How to Figure Out Your Values in a Relationship | Bumble		 200 yes 1165 2
https://bumble.com/help-search
Bumble Support		 200 yes 180 0
https://bumble.com/help/IRL
Meeting a match in person – Bumble Support		 200 yes 386 0
https://bumble.com/unsupported-browser
Bumble Support		 200 yes 180 0
https://bumble.com/bumble-washington-consumer-health-data-privacy-policy 200 no 0 40
https://bumble.com/modern-slavery-act-statement 200 no 0 40
https://bumble.com/notice-at-collection 200 no 0 40

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →