Website review, no card needed

bog.gov.gh logo

bog.gov.gh website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 65 checks

This review found 31 issues worth fixing on bog.gov.gh, 13 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
13.2 s6.1 sMay 30Nov 1412.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20267.9 s
Jun 6, 20267.8 s
Jun 13, 20267.6 s
Jun 20, 20267.5 s
Jun 27, 20267.6 s
Jul 4, 20267.7 s
Jul 11, 20267.8 s
Jul 18, 20267.8 s
Jul 25, 20267.6 s
Aug 1, 20267.6 s
Aug 8, 20267.5 s
Aug 15, 20267.5 s
Aug 22, 20267.4 s
Aug 29, 20267.3 s
Sep 5, 20267.2 s
Sep 12, 20267.0 s
Sep 19, 20266.9 s
Sep 26, 20266.9 s
Oct 3, 20266.9 s
Oct 10, 20267.0 s
Oct 17, 20267.2 s
Oct 24, 20267.5 s
Oct 31, 20268.4 s
Nov 7, 20269.7 s
Nov 14, 202612.4 s
Real-visitor tap response (INP)75th percentile, phones
186 ms157 msMay 30Nov 14176 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026181 ms
Jun 6, 2026183 ms
Jun 13, 2026180 ms
Jun 20, 2026176 ms
Jun 27, 2026167 ms
Jul 4, 2026162 ms
Jul 11, 2026161 ms
Jul 18, 2026160 ms
Jul 25, 2026162 ms
Aug 1, 2026167 ms
Aug 8, 2026170 ms
Aug 15, 2026170 ms
Aug 22, 2026167 ms
Aug 29, 2026166 ms
Sep 5, 2026164 ms
Sep 12, 2026165 ms
Sep 19, 2026168 ms
Sep 26, 2026169 ms
Oct 3, 2026165 ms
Oct 10, 2026161 ms
Oct 17, 2026161 ms
Oct 24, 2026160 ms
Oct 31, 2026167 ms
Nov 7, 2026175 ms
Nov 14, 2026176 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

6 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 12.4 s

    12.4 s

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

  • Real-user FCP: 11.3 s

    11.3 s

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

  • Real-user TTFB: 5.5 s

    5.5 s

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

  • Real-user CLS: 0.18

    0.18

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

  • Largest content (LCP) got 41% slower for real visitors

    +41%

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

  • Tap response (INP) held steady for real visitors

    -4%

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

1 checks passed
  • Real-user INP: 176 ms

    176 ms

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

Images and page weight

5 to fix18
  • Page weight: 6.4 MB

    6.4 MB

    Your homepage downloads 6.4 MB on a phone, 1.7 MB of it images (26%). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    BOG-Database.png weighs 594 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    863 KiB

    5 images are downloaded at several times the size a phone draws them, for example BOG-Database.png at 10,417 px wide, shown at 390 px. Resized copies would save about 863 KiB.

  • 4 images in older formats

    4 images (920 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.

  • 2 images below the first screen load straight away

    2 images further down the page (436 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.82 g

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

Accessibility

6 to fix90
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 12 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 35 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: 35 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fix62
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (28 characters)

    Your title is only 28 characters: “Bank of Ghana – Central Bank”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at bog.gov.gh/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 170 internal links, 18 external

    The homepage links to 170 pages on bog.gov.gh and 18 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.bog.gov.gh/.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.bog.gov.gh/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.bog.gov.gh/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://www.bog.gov.gh/bank-notes-coins, https://www.bog.gov.gh/monetary-policy, https://www.bog.gov.gh/supervision-regulation, https://www.bog.gov.gh/economic-data, https://www.bog.gov.gh/downloads and https://www.bog.gov.gh/resolution and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.bog.gov.gh/bank-notes-coins, https://www.bog.gov.gh/monetary-policy, https://www.bog.gov.gh/supervision-regulation, https://www.bog.gov.gh/economic-data, https://www.bog.gov.gh/downloads and https://www.bog.gov.gh/resolution and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.bog.gov.gh/monetary-policy, https://www.bog.gov.gh/economic-data, https://www.bog.gov.gh/downloads, https://www.bog.gov.gh/resolution, https://www.bog.gov.gh/ghana-petroleum-funds and https://www.bog.gov.gh/fintech-innovation and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

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

  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 417 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Start License Application Here” and “Book a Virtual Appointment”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • No consent tool detected

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

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Bank Of Ghana

Company

Founded
1957
Headquarters
Accra

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on bog.gov.gh, including 6 speed issues, 6 SEO issues and 4 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