jbb.gov.co website review

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.3 s faster on a phone.

35 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.

About 344 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

YouTube costs a phone 1.1 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

167 KiB could be saved by minifying JavaScript.

Your mobile performance score is 33 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.7 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

12 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

17 long tasks block the main thread while loading, the longest for 1.9 s. During a long task the page ignores taps.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Hotjar and others), adding 4.3 MB and 1.4 s of main-thread time.

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

40 KiB could be saved by minifying CSS.

The page has 1,514 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

bogota.gov.co costs a phone 40 ms of main-thread work and 755 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

Your largest element takes 34.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Llega una nueva edición de la fascinante exposición de Brom…”.

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

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

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 14.8 MB in 184 requests on a phone: images 9.5 MB (36), scripts 4.0 MB (69) and fonts 605 KiB (12). Under 2 MB keeps phones on slow connections fast.

6 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example IMG_6217-1.png at 2,560 px wide, shown at 390 px. Resized copies would save about 4.0 MB.

13 images (6.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.

FotoJet1-1-768x768.jpg 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).

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

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

2 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: 2 elements on the page fail this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

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

Your title is 449 characters, so Google will cut it off around 60: “Jardín Botánico de Bogotá – El Jardín botánico funciona como centro de investigación sobr…”.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 96 pages on jbb.gov.co and 33 external pages.

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.

There is no https://jbb.gov.co/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.

https://jbb.gov.co/nosotros/politica-del-sig, https://jbb.gov.co/nosotros/objetivos-del-sig, https://jbb.gov.co/mapa, https://jbb.gov.co/eventos/agenda-cultural-academica, https://jbb.gov.co/eventos-2/eventos and https://jbb.gov.co/codigos-de-conducta and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://jbb.gov.co/eventos/agenda-cultural-academica, whose canonical is https://jbb.gov.co/eventos-2/eventos/agenda-cultural-academica. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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

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

Large scripts ship without source maps.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 841 words of visible text.

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

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

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.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.