Website review, no card needed
conmebol.com website review
Visit site (opens in a new tab)Reviewed 3 November 202652 issues · 90 checks
This review found 52 issues worth fixing on conmebol.com, 23 of them high impact, across 90 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 106 ms |
| Aug 15, 2026 | 108 ms |
| Aug 22, 2026 | 107 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 116 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 104 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.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Reduce unused JavaScript
4.1 s · 699 KiBAbout 699 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
3.5 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 2.2 MB11 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 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, userway.org and Amazon Web Services and others), adding 2.2 MB and 987 ms of main-thread time.
Use efficient cache lifetimes
350 ms · 829 KiB67 files are served with short cache lifetimes, so returning visitors download them again (829 KiB).
Google Tag Manager adds 779 ms
779 msGoogle Tag Manager costs a phone 779 ms of main-thread work and 1.1 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 257 ms. During a long task the page ignores taps.
1,978 HTML elements
The page has 1,978 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
fifprosudamerica.org adds 39 ms
39 msfifprosudamerica.org costs a phone 39 ms of main-thread work and 777 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
150 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 19.7 s
19.7 sYour largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Entradas CONMEBOL Sudamericana”.
Time to Interactive: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.453
0.453The layout shifts by 0.453 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 626 ms
626 msScripts block taps and scrolling for 626 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 796 ms
796 msReal visitors wait 796 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.8 MB in 131 requests
4.8 MBYour homepage downloads 4.8 MB in 131 requests on a phone: images 2.4 MB (26), scripts 1.5 MB (35) and fonts 620 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
banner_conmebol_corto.png weighs 722 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
667 KiB1 image is downloaded at several times the size a phone draws it, for example banner_conmebol_corto.png at 3,998 px wide, shown at 370 px. Resized copies would save about 667 KiB.
5 images in older formats
5 images (1.0 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.
1 image below the first screen load straight away
1 image further down the page (722 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.37 g of CO₂e: 164.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (11 elements)
ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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. (10 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Colombia será sede de la CONMEBOL Sub20 2027”, “Brasil remonta ante China y clasifica a Semifinal…” and “Cruzeiro remontó ante Corinthians y es campeón de…”). One clear main headline is easier for people and search engines.
No robots.txt
There is no robots.txt at conmebol.com/robots.txt, the first file search crawlers ask for.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
281 internal links, 36 external
The homepage links to 281 pages on conmebol.com and 36 external pages.
4 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “CONMEBOL – Sitio Oficial de la CONMEBOL”.
Canonical URL set
The canonical URL is https://www.conmebol.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.conmebol.com/sitemap.xml.
AI search readiness
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.conmebol.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,176 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.conmebol.com/noticias/cruzeiro-remonto-ante-corinthians-y-es-campeon-de-la-conmebol-libertadores-femenina has no <title>, so Google invents the link text in results.
15 pages without a meta description
https://www.conmebol.com/noticias/colombia-sera-sede-de-la-conmebol-sub20-2027, https://www.conmebol.com/noticias/brasil-remonta-ante-china-y-clasifica-a-semifinales-del-mundial-femenino-sub17, https://www.conmebol.com/noticias/cruzeiro-remonto-ante-corinthians-y-es-campeon-de-la-conmebol-libertadores-femenina, https://www.conmebol.com/museo-conmebol, https://www.conmebol.com/suma and https://www.conmebol.com/la-institucion and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.conmebol.com/noticias/cruzeiro-remonto-ante-corinthians-y-es-campeon-de-la-conmebol-libertadores-femenina has 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 73 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.
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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “wp is not defined”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
20 of 23 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 589 words of copy
The homepage carries about 589 words of visible text.
2 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
14 other companies contacted
Loading the homepage contacts 14 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 conmebol.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Company
- Founded
- 1916
- Headquarters
- Luque
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on conmebol.com, including 22 speed issues, 5 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.