Website review, no card needed

cens.com.co logo

cens.com.co website review

Visit site (opens in a new tab)Reviewed 26 October 202658 issues · 91 checks

This review found 58 issues worth fixing on cens.com.co, 22 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.

  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
3.3 s3.0 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
201 ms181 msMay 2Oct 17198 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026183 ms
May 9, 2026184 ms
May 16, 2026185 ms
May 23, 2026188 ms
May 30, 2026187 ms
Jun 6, 2026187 ms
Jun 13, 2026187 ms
Jun 20, 2026185 ms
Jun 27, 2026187 ms
Jul 4, 2026186 ms
Jul 11, 2026186 ms
Jul 18, 2026186 ms
Jul 25, 2026186 ms
Aug 1, 2026189 ms
Aug 8, 2026188 ms
Aug 15, 2026191 ms
Aug 22, 2026191 ms
Aug 29, 2026191 ms
Sep 5, 2026193 ms
Sep 12, 2026194 ms
Sep 19, 2026197 ms
Sep 26, 2026198 ms
Oct 3, 2026199 ms
Oct 10, 2026198 ms
Oct 17, 2026198 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 cens.com.co (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cens.com.co at 0.5 s0.5 s
  2. cens.com.co at 0.9 s0.9 s
  3. cens.com.co at 1.4 s1.4 s
  4. cens.com.co at 1.9 s1.9 s
  5. cens.com.co at 2.3 s2.3 s
  6. cens.com.co at 2.8 s2.8 s
  7. cens.com.co at 3.3 s3.3 s
  8. cens.com.co at 3.7 s3.7 s

Speed

15 to fix23
  • Reduce unused JavaScript

    3.7 s · 1.3 MB

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

  • Render-blocking requests

    4.7 s

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

  • Improve image delivery

    1.8 s · 2.1 MB

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

  • Use efficient cache lifetimes

    1.8 s · 401 KiB

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

  • Mobile performance score: 23

    23/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 1.6 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 (mypurecloud.com, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.8 MB and 1.7 s of main-thread time.

  • mypurecloud.com adds 939 ms

    939 ms

    mypurecloud.com costs a phone 939 ms of main-thread work and 1.0 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.

  • Reduce initial server response time

    907 ms

    Reduce initial server response time. Google estimates savings of 907 ms on a phone.

  • Document request latency

    900 ms

    The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused CSS

    600 ms · 55 KiB

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

  • Google Tag Manager adds 498 ms

    498 ms

    Google Tag Manager costs a phone 498 ms of main-thread work and 477 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.

  • Minify JavaScript

    390 ms · 83 KiB

    83 KiB could be saved by minifying JavaScript.

  • Minify CSS

    450 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • Server response: 1.0 s

    1.0 s

    Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Duplicated JavaScript

    100 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

13 to fix0
  • 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 CLS: 0.57

    0.57

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

  • Largest Contentful Paint: 32.7 s

    32.7 s

    Your largest element takes 32.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Resolución CREG 101 120 del 2026”.

  • Speed Index: 17.7 s

    17.7 s

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

  • Time to Interactive: 45.0 s

    45.0 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Cumulative Layout Shift: 0.494

    0.494

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 210 ms

    210 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 836 ms

    836 ms

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

  • Total Blocking Time: 469 ms

    469 ms

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

Images and page weight

5 to fix28
  • Page weight: 17.5 MB in 231 requests

    17.5 MB

    Your homepage downloads 17.5 MB in 231 requests on a phone: images 12.0 MB (81), scripts 2.8 MB (77) and other files 2.2 MB (22). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 26 images in older formats

    26 images (7.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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    371 KiB

    1 image is downloaded at several times the size a phone draws it, for example images.jpg at 2,088 px wide, shown at 48 px. Resized copies would save about 371 KiB.

  • About 5.0 g of CO₂ per visit

    4.95 g

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

Accessibility

7 to fixGoogle 8388
  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • 2 tap targets too small

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

  • 14 images without alt text

    14 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

7 to fixGoogle 8367
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (6 characters)

    Your title is only 6 characters: “Inicio”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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 XML sitemap

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

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 84 internal links, 13 external

    The homepage links to 84 pages on cens.com.co and 13 external pages.

2 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “CENS Grupo EPM presta el servicio de energía eléctrica en Norte de Santander, sur del Cesar y sur de Bolívar. Conoce nu…”.

  • robots.txt in place

    robots.txt is in place.

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.cens.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 (666 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.cens.com.co/tramites-y-servicios, https://www.cens.com.co/institucional/sala-de-prensa/grupo-epm-impulsa-la-innovacion-colaborativa-con-estudiantes-universitarios-a-traves-de-innovate-emprendiendo-2026 and https://www.cens.com.co/institucional/normas-y-especificaciones-tecnicas have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.cens.com.co/transparencia-y-acceso-a-la-informacion-publica, https://www.cens.com.co/tramites-y-servicios, https://www.cens.com.co/participa, https://www.cens.com.co/institucional, https://www.cens.com.co/institucional/reconocimientos-y-certificaciones and https://www.cens.com.co/institucional/trabaja-con-nosotros and 8 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 65 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

4 to fixGoogle 6570
  • 10 broken images

    10 images failed to load on a phone, for example https://www.cens.com.co/.

  • 7 small tap targets

    7 of 20 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 (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://stats.g.doubleclick.net/g/collect?v=2&tid=G-D779P0RKYM&cid=1664919980.1792974429&gtm=45je6am0h2v…”.

  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 492 words of copy

    The homepage carries about 492 words of visible text.

3 checks passed
  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 13 cookies set on arrival

    13

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

  • 22 other companies contacted

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

Upkeep, stack and company

Company

Founded
1955
Headquarters
Q216847

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on cens.com.co, including 28 speed issues, 7 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