Website review, no card needed
cbsi.com.sb website review
Visit site (opens in a new tab)Reviewed 19 October 202631 issues · 78 checks
This review found 31 issues worth fixing on cbsi.com.sb, 11 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 261 ms |
| May 9, 2026 | 251 ms |
| May 16, 2026 | 221 ms |
| May 23, 2026 | 221 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 305 ms |
| Jun 20, 2026 | 282 ms |
| Jun 27, 2026 | 267 ms |
| Jul 4, 2026 | 254 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 133 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
2.5 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Improve image delivery
14.6 MB8 images could be 14.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 83
83/100Your mobile performance score is 83 (desktop: 72). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
304 KiBAbout 304 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 211 ms
211 msGoogle Tag Manager costs a phone 211 ms of main-thread work and 301 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Adobe TypeKit and others), adding 485 KiB and 264 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
24 KiB24 KiB could be saved by minifying JavaScript.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 229 ms of it running JavaScript. That is comfortably low.
Server response: 196 ms
196 msYour server sent the HTML in 196 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 804 ms
804 msReal visitors wait 804 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 s.
Largest Contentful Paint: 3.1 s
3.1 sYour largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Tap response (INP) got 50% faster for real visitors
-50%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 261 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 69 ms
69 msScripts block the page for only 69 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 16.6 MB in 91 requests
16.6 MBYour homepage downloads 16.6 MB in 91 requests on a phone: images 15.8 MB (24), scripts 589 KiB (24) and fonts 127 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 13.3 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
12.8 MB4 images are downloaded at several times the size a phone draws them, for example IMG_1062.JPG at 5,184 px wide, shown at 353 px. Resized copies would save about 12.8 MB.
5 images in older formats
5 images (13.4 MB) 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.
5 images below the first screen load straight away
5 images further down the page (13.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.7 g of CO₂ per visit
4.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.71 g of CO₂e: 565.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
221 internal links, 9 external
The homepage links to 221 pages on cbsi.com.sb and 9 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Discover the Central Bank of Solomon Islands for official information on monetary policy, financial stability, economic…”.
One H1 headline
Your main headline reads: “50 Years of Resilience and Progressive Development.”.
Title: 35 characters
Your title is a healthy 35 characters: “Home | Central Bank Solomon Islands”.
Canonical URL set
The canonical URL is https://www.cbsi.com.sb/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.cbsi.com.sb/sitemap.xml.
AI search readiness
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.cbsi.com.sb/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,626 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
19 small tap targets
19 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Identifier 'dl' has already been declared”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 699 words of copy
The homepage carries about 699 words of visible text.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Download centre” and “Forms Download Centre”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before 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.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
5 other companies contacted
Loading the homepage contacts 5 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 cbsi.com.sb, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
Company
- Founded
- 1983
- Headquarters
- Honiara
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 cbsi.com.sb, including 14 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.