Website review, no card needed
woden.com.co website review
Visit site (opens in a new tab)Reviewed 30 October 202638 issues · 79 checks
This review found 38 issues worth fixing on woden.com.co, 11 of them high impact, across 79 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 129 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 134 ms |
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 135 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.1 s · 367 KiBAbout 367 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 213 KiB4 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 1.2 MB and 667 ms of main-thread time.
Reduce unused CSS
520 ms · 71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 520 ms faster on a phone.
Google Tag Manager adds 401 ms
401 msGoogle Tag Manager costs a phone 401 ms of main-thread work and 491 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.
zohocdn.com adds 0 ms
0 mszohocdn.com costs a phone 0 ms of main-thread work and 490 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
150 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Improve image delivery
5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 615 ms of it running JavaScript. That is comfortably low.
Server response: 52 ms
52 msYour server sent the HTML in 52 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.
Largest Contentful Paint: 14.1 s
14.1 sYour largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 14.1 s
14.1 sThe page becomes fully interactive after 14.1 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 941 ms
941 msReal visitors wait 941 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 410 ms
410 msScripts block taps and scrolling for 410 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 129 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 167 ms
167 msReal visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.2 MB in 54 requests
8.2 MBYour homepage downloads 8.2 MB in 54 requests on a phone: media 5.8 MB (4), images 1.0 MB (11) and scripts 828 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 2.3 g of CO₂ per visit
2.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.34 g of CO₂e: 280.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Woden Colombia - Empresa de Economía circular. Servicio Técnico y Logística Inversa”.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
90 internal links, 8 external
The homepage links to 90 pages on woden.com.co and 8 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.woden.com.co/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.woden.com.co/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), 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://www.woden.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 (911 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://www.woden.com.co/nosotros/sostenibilidad, https://www.woden.com.co/nosotros/oficinas-globales and https://www.woden.com.co/nosotros/nuestros-clientes all use the title “Sostenibilidad y cuidado del medio ambiente - Woden”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://www.woden.com.co/nosotros/sostenibilidad, https://www.woden.com.co/nosotros/oficinas-globales, https://www.woden.com.co/nosotros/nuestros-clientes, https://www.woden.com.co/trabaje-con-nosotros/enviar-hoja-de-vida, https://www.woden.com.co/blogs and https://www.woden.com.co/empresas/Soluciones%20Universales/contact-center-new and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.woden.com.co/empresas/soluciones-para-empresas and https://www.woden.com.co/empresas/Soluciones%20Universales/soluciones-universales use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://www.woden.com.co/nosotros/oficinas-globales, https://www.woden.com.co/nosotros/nuestros-clientes, https://www.woden.com.co/trabaje-con-nosotros, https://www.woden.com.co/trabaje-con-nosotros/ofertas-laborales, https://www.woden.com.co/trabaje-con-nosotros/enviar-hoja-de-vida and https://www.woden.com.co/empresas/soluciones-para-empresas and 4 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 60 found) and read each the way a search engine does.
4 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.
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 small tap targets
2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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 538 words of copy
The homepage carries about 538 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Center” and “Ver Contact Center”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before 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
10Opening the homepage sets 10 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.
10 other companies contacted
Loading the homepage contacts 10 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 woden.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
- Zoho
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on woden.com.co, including 16 speed issues, 6 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.