Website review, no card needed
caracol.com.co website review
Visit site (opens in a new tab)Reviewed 17 November 202646 issues · 91 checks
This review found 46 issues worth fixing on caracol.com.co, 18 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 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.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 164 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 165 ms |
| Jul 11, 2026 | 167 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 158 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 152 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 121 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 122 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
Reduce unused JavaScript
4.3 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
3.4 s · 2.0 MB163 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 3.2 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/Doubleclick Ads, YouTube and Rubicon Project and others), adding 2.8 MB and 1.8 s of main-thread time.
Improve image delivery
950 ms · 598 KiB18 images could be 598 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Google/Doubleclick Ads adds 500 ms
500 msGoogle/Doubleclick Ads costs a phone 500 ms of main-thread work and 771 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.
YouTube adds 392 ms
392 msYouTube costs a phone 392 ms of main-thread work and 998 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 420 ms. During a long task the page ignores taps.
2,257 HTML elements
The page has 2,257 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
listenlive.co adds 149 ms
149 mslistenlive.co costs a phone 149 ms of main-thread work and 363 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.
Reduce unused CSS
71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.5 s
19.5 sYour largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Petro respondió a Noboa, quien lo señaló de reunirse con po…”.
Time to Interactive: 46.3 s
46.3 sThe page becomes fully interactive after 46.3 s. Good is under 3.8 s.
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.0 s
6.0 sThe first text or image appears after 6.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 679 ms
679 msReal visitors wait 679 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 164 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 1,241 requests
5.9 MBYour homepage downloads 5.9 MB in 1,241 requests on a phone: scripts 3.1 MB (104), images 1.5 MB (399) and HTML 416 KiB (225). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
UYHUXSCQGJG3JFGTRU4ECYVH2Y.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).
3 images far larger than shown
111 KiB3 images are downloaded at several times the size a phone draws them, for example AIX4ZNQBZVBERDS7Z7DB5KRDZA.jpeg at 1,600 px wide, shown at 358 px. Resized copies would save about 111 KiB.
8 images in older formats
8 images (439 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.
3 images below the first screen load straight away
3 images further down the page (133 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 202.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
31 tap targets too small
31 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 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 (41 elements)
All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (18 elements)
Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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. (1 element).
2 checks passed
Every image has alt text
All 132 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Caracol Radio: Últimas noticias de Colombia, deportes y radio en vivo”.
Meta description is long (161 characters)
Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, 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.
268 internal links, 50 external
The homepage links to 268 pages on caracol.com.co and 50 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Caracol Radio”.
Canonical URL set
The canonical URL is https://caracol.com.co/.
Structured data in place
Structured data found: AudioObject, ItemList, NewsMediaOrganization, PodcastEpisode and PodcastSeries.
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://caracol.com.co/arc/outboundfeeds/googlenewssitemap/latest/?outputType=xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://caracol.com.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.
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 (2,647 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://caracol.com.co/2026/11/2026/11/16/si-tiene-mas-de-60-anos-estos-son-los-requisitos-para-renovar-la-licencia-de-conduccion/15/bid-aprueba-credito-de-us450-millones-para-impulsar-la-transicion-energetica-en-colombia, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page points its canonical at the homepage
https://caracol.com.co/deportes declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
https://caracol.com.co/deportes and https://caracol.com.co/especiales all use the title “Caracol Radio: Noticias y Radio Online”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://caracol.com.co/deportes, https://caracol.com.co/especiales and https://caracol.com.co/usuarios/perfil use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://caracol.com.co/programas, https://caracol.com.co/especiales and https://caracol.com.co/usuarios/perfil 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 143 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
30 third-party cookies
30 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
19 small tap targets
19 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 2,150 words of copy
The homepage carries about 2,150 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
1 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Taboola and The Trade Desk (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) loads with the page.
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 caracol.com.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Akamai
Company
- Founded
- 1948
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 caracol.com.co, including 17 speed issues, 3 SEO issues and 5 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.