Website review, no card needed

responsiblebusiness.org logo

responsiblebusiness.org website review

Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 86 checks

This review found 36 issues worth fixing on responsiblebusiness.org, 10 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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.6 s2.1 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
120 ms96 msMay 2Oct 17105 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026113 ms
May 9, 2026110 ms
May 16, 2026112 ms
May 23, 2026110 ms
May 30, 2026111 ms
Jun 6, 2026107 ms
Jun 13, 2026110 ms
Jun 20, 2026110 ms
Jun 27, 2026108 ms
Jul 4, 2026117 ms
Jul 11, 2026113 ms
Jul 18, 2026110 ms
Jul 25, 2026109 ms
Aug 1, 2026107 ms
Aug 8, 2026105 ms
Aug 15, 2026101 ms
Aug 22, 2026101 ms
Aug 29, 202699 ms
Sep 5, 2026103 ms
Sep 12, 2026107 ms
Sep 19, 2026106 ms
Sep 26, 2026104 ms
Oct 3, 202699 ms
Oct 10, 2026103 ms
Oct 17, 2026105 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 responsiblebusiness.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. responsiblebusiness.org at 0.6 s0.6 s
  2. responsiblebusiness.org at 1.2 s1.2 s
  3. responsiblebusiness.org at 1.8 s1.8 s
  4. responsiblebusiness.org at 2.3 s2.3 s
  5. responsiblebusiness.org at 2.9 s2.9 s
  6. responsiblebusiness.org at 3.5 s3.5 s
  7. responsiblebusiness.org at 4.1 s4.1 s
  8. responsiblebusiness.org at 4.7 s4.7 s

Speed

8 to fix59
  • Reduce unused JavaScript

    2.9 s · 529 KiB

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

  • Mobile performance score: 59

    59/100

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

  • Render-blocking requests

    600 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Vimeo and Other Google APIs/SDKs and others), adding 2.3 MB and 277 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 61 KiB

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

  • Improve image delivery

    150 ms · 258 KiB

    5 images could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Vimeo adds 66 ms

    66 ms

    Vimeo costs a phone 66 ms of main-thread work and 1.8 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 149 ms

    149 ms

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

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix67
  • 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: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RBA Annual Report 2025 RBA Announces New and Improved Onsit…”.

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 31 ms

    31 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 61 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 61 requests on a phone: other files 1.3 MB (17), scripts 992 KiB (12) and images 621 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (136 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.9 g of CO₂ per visit

    0.86 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8890
  • 19 tap targets too small

    19 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10084
  • Title is short (29 characters)

    Your title is only 29 characters: “Responsible Business Alliance”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • 148 internal links, 24 external

    The homepage links to 148 pages on responsiblebusiness.org and 24 external pages.

5 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “The Responsible Business Alliance (RBA) is an industry coalition dedicated to responsible business conduct in global su…”.

  • One H1 headline

    Your main headline reads: “The Responsible Business Alliance (RBA) is an industry coalition dedicated to responsible business conduct in global su…”.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.responsiblebusiness.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.responsiblebusiness.org/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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.responsiblebusiness.org/vap/vap-validation-tool has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 5086
  • 4 small tap targets

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

  • 3 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 542 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join the RBA” and “Contact”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Join the RBA”, “Contact” and “JOIN RBA”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 responsiblebusiness.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on responsiblebusiness.org, including 17 speed issues, 4 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