Website review, no card needed

camaradirecta.com logo

camaradirecta.com website review

Visit site (opens in a new tab)Reviewed 29 October 202646 issues · 85 checks

This review found 46 issues worth fixing on camaradirecta.com, 23 of them high impact, across 85 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
4.7 s4.2 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.5 s
May 16, 20264.6 s
May 23, 20264.6 s
May 30, 20264.6 s
Jun 6, 20264.6 s
Jun 13, 20264.5 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.5 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.4 s
Aug 8, 20264.5 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.4 s
Sep 19, 20264.5 s
Sep 26, 20264.4 s
Oct 3, 20264.4 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
259 ms194 msMay 9Oct 24246 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026223 ms
May 16, 2026210 ms
May 23, 2026211 ms
May 30, 2026213 ms
Jun 6, 2026213 ms
Jun 13, 2026214 ms
Jun 20, 2026219 ms
Jun 27, 2026215 ms
Jul 4, 2026223 ms
Jul 11, 2026224 ms
Jul 18, 2026215 ms
Jul 25, 2026215 ms
Aug 1, 2026201 ms
Aug 8, 2026202 ms
Aug 15, 2026205 ms
Aug 22, 2026208 ms
Aug 29, 2026219 ms
Sep 5, 2026223 ms
Sep 12, 2026226 ms
Sep 19, 2026232 ms
Sep 26, 2026240 ms
Oct 3, 2026241 ms
Oct 10, 2026244 ms
Oct 17, 2026251 ms
Oct 24, 2026246 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 camaradirecta.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. camaradirecta.com at 0.7 s0.7 s
  2. camaradirecta.com at 1.4 s1.4 s
  3. camaradirecta.com at 2.2 s2.2 s
  4. camaradirecta.com at 2.9 s2.9 s
  5. camaradirecta.com at 3.6 s3.6 s
  6. camaradirecta.com at 4.3 s4.3 s
  7. camaradirecta.com at 5.0 s5.0 s
  8. camaradirecta.com at 5.8 s5.8 s

Speed

12 to fix18
  • Reduce unused JavaScript

    7.8 s · 2.6 MB

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

  • Improve image delivery

    4.2 s · 3.6 MB

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

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 1.2 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.

  • Use efficient cache lifetimes

    1.3 s · 241 KiB

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

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 4.8 s

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

  • 8 third-party services on the page

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

  • Render-blocking requests

    950 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 950 ms.

  • YouTube adds 613 ms

    613 ms

    YouTube costs a phone 613 ms of main-thread work and 977 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.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 110 KiB

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

  • Facebook adds 268 ms

    268 ms

    Facebook costs a phone 268 ms of main-thread work and 254 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.

  • Legacy JavaScript

    250 ms · 12 KiB

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

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

1 checks passed
  • Server response: 95 ms

    95 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 5.7 s

    5.7 s

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

  • Real-user FCP: 5.0 s

    5.0 s

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

  • Real-user TTFB: 3.7 s

    3.7 s

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

  • Largest Contentful Paint: 54.6 s

    54.6 s

    Your largest element takes 54.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cámaradirecta”.

  • Speed Index: 17.5 s

    17.5 s

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

  • Time to Interactive: 55.9 s

    55.9 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.398

    0.398

    The layout shifts by 0.398 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user INP: 260 ms

    260 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

1 checks passed
  • Real-user CLS: 0.05

    0.05

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

Images and page weight

5 to fix26
  • Page weight: 15.6 MB in 128 requests

    15.6 MB

    Your homepage downloads 15.6 MB in 128 requests on a phone: images 12.6 MB (78), scripts 2.6 MB (24) and stylesheets 243 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    4.3 MB

    9 images are downloaded at several times the size a phone draws them, for example bann_17bb14821537e03ad8857979fe06b2af7160622f.png at 1,254 px wide, shown at 342 px. Resized copies would save about 4.3 MB.

  • 11 images in older formats

    11 images (9.1 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.

  • An image on the first screen is lazy-loaded

    cabe_dbd537b3a92756e0816a1c9761a9ae4a38355b5f.png 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).

  • 2 images below the first screen load straight away

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

  • About 4.4 g of CO₂ per visit

    4.42 g

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

Accessibility

4 to fixGoogle 9594
  • 13 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (27 elements).

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://www.camaradirecta.com.co/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 134 internal links, 27 external

    The homepage links to 134 pages on camaradirecta.com and 27 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “La Cámara de Comercio de Bucaramanga trabaja por el desarrollo socioeconómico de la región mediante el fortalecimiento …”.

  • One H1 headline

    Your main headline reads: “Qué quiere hacer hoy?”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Cámara de Comercio de Bucaramanga”.

  • Canonical URL set

    The canonical URL is https://www.camaradirecta.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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.camaradirecta.com/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,201 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 3 pages share a title

    /, https://www.camaradirecta.com/pqrs and https://www.camaradirecta.com/sedevirtual all use the title “Cámara de Comercio de Bucaramanga”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.camaradirecta.com/clavesegura and https://www.camaradirecta.com/estadotramites have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://www.camaradirecta.com/conocer-la-region/sedes, https://www.camaradirecta.com/promotores, https://www.camaradirecta.com/documentos, https://www.camaradirecta.com/preguntas-frecuentes and https://www.camaradirecta.com/videos-ccb use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.camaradirecta.com/conocer-la-region/sedes, whose canonical is https://www.camaradirecta.com/sedes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.camaradirecta.com/conocer-la-region/sedes, https://www.camaradirecta.com/pqrs, https://www.camaradirecta.com/sedevirtual, https://www.camaradirecta.com/clavesegura, https://www.camaradirecta.com/preguntas-frecuentes and https://www.camaradirecta.com/estadotramites and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.camaradirecta.com/sedevirtual and https://www.camaradirecta.com/estadotramites have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 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

2 to fixGoogle 7391
  • 5 small tap targets

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

  • 5 third-party cookies

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

  • 1 low-resolution image

    1 image is 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

3 to fix50
  • 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 calls to action

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

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

    The homepage carries about 749 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager
Hosting
Commerce Partners S.A

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on camaradirecta.com, including 23 speed issues, 2 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

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