Website review, no card needed
csbp.com.bo website review
Visit site (opens in a new tab)Reviewed 26 October 202650 issues · 93 checks
This review found 50 issues worth fixing on csbp.com.bo, 19 of them high impact, across 93 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 118 ms |
| May 16, 2026 | 115 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 124 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 125 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
Speed
Render-blocking requests
4.7 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Reduce unused CSS
2.1 s · 373 KiBAbout 373 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 28). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
600 ms · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
1.9 MB5 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google CDN and Google Maps and others), adding 2.7 MB and 969 ms of main-thread time.
Use efficient cache lifetimes
600 ms · 512 KiB12 files are served with short cache lifetimes, so returning visitors download them again (512 KiB).
YouTube adds 755 ms
755 msYouTube costs a phone 755 ms of main-thread work and 1.9 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.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 102 ms
102 msGoogle CDN costs a phone 102 ms of main-thread work and 348 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 16 KiB16 KiB could be saved by minifying CSS.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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.
1 checks passed
Server response: 300 ms
300 msYour server sent the HTML in 300 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: 18.4 s
18.4 sVisually, the page fills in at 18.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.6 s
39.6 sThe page becomes fully interactive after 39.6 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Puedes agendar tu cita médica mediante la plataforma web”. Most of its time is element render delay (3.0 s).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 357 ms
357 msScripts block taps and scrolling for 357 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 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-24, real Chrome visitors' tap response (inp) went from 118 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 700 ms
700 msReal visitors wait 700 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 8.1 MB in 109 requests
8.1 MBYour homepage downloads 8.1 MB in 109 requests on a phone: images 3.6 MB (26), scripts 3.3 MB (36) and fonts 444 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mesa de trabajo [email protected] is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
45 KiB1 image is downloaded at several times the size a phone draws it, for example Mesa de trabajo [email protected] at 1,920 px wide, shown at 390 px. Resized copies would save about 45 KiB.
1 image in older formats
1 image (72 KiB) is 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 2.3 g of CO₂ per visit
2.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.30 g of CO₂e: 276.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Elements marked as presentational should be consistently ignored (15 elements)
Elements marked as presentational should be consistently ignored: 15 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
42 internal links, 82 external
The homepage links to 42 pages on csbp.com.bo and 82 external pages.
4 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “Home | Caja Salud Banca Privada”.
Canonical URL set
The canonical URL is https://csbp.com.bo/.
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://csbp.com.bo/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://csbp.com.bo/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 (899 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://csbp.com.bo/blog/medicamentos-79/medicamentos-reembolsos-2040 and https://csbp.com.bo/blog/medicamentos-79/medicamentos-reenbolsos-2040 all use the title “MEDICAMENTOS (DEVOLUCIÓN) | Caja Salud Banca Privada”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://csbp.com.bo/blog/direcciones-de-la-csbp-nacional-82/informacion-de-los-establecimientos-2153, https://csbp.com.bo/shop/wishlist, https://csbp.com.bo/service_desk_ata_form, https://csbp.com.bo/blog/portal-asegurado-y-empresas-70/portal-asegurado-y-empresas-1533, https://csbp.com.bo/blog/tutoriales-84/tutorial-de-uso-de-los-canales-digitales-2177 and https://csbp.com.bo/blog/comunicados-oficina-nacional-37/queremos-entregarte-una-experiencia-de-acceso-digital-renovada-1116 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://csbp.com.bo/shop/wishlist, whose canonical is https://csbp.com.bo/shop. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://csbp.com.bo/blog/direcciones-de-la-csbp-nacional-82/informacion-de-los-establecimientos-2153, https://csbp.com.bo/service_desk_ata_form, https://csbp.com.bo/blog/portal-asegurado-y-empresas-70/portal-asegurado-y-empresas-1533, https://csbp.com.bo/blog/tutoriales-84/tutorial-de-uso-de-los-canales-digitales-2177, https://csbp.com.bo/blog/comunicados-oficina-nacional-37/queremos-entregarte-una-experiencia-de-acceso-digital-renovada-1116 and https://csbp.com.bo/blog/formulario-de-asegurados-11/formulario-no-asegurados-en-la-csbp-43 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
5 third-party cookies
5 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.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 374 words of copy
The homepage carries about 374 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Reserve cita médica”.
Analytics in place
Analytics detected: Umami.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
12 other companies contacted
Loading the homepage contacts 12 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 csbp.com.bo, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on csbp.com.bo, including 19 speed issues, 4 SEO issues and 3 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.