Website review, no card needed
ulaidiomas.edu.co website review
Visit site (opens in a new tab)Reviewed 25 October 202645 issues · 88 checks
This review found 45 issues worth fixing on ulaidiomas.edu.co, 19 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
54FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 247 ms |
| May 9, 2026 | 245 ms |
| May 16, 2026 | 244 ms |
| May 23, 2026 | 248 ms |
| May 30, 2026 | 256 ms |
| Jun 6, 2026 | 263 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 274 ms |
| Jun 27, 2026 | 276 ms |
| Jul 4, 2026 | 281 ms |
| Jul 11, 2026 | 285 ms |
| Jul 18, 2026 | 286 ms |
| Jul 25, 2026 | 286 ms |
| Aug 1, 2026 | 287 ms |
| Aug 8, 2026 | 299 ms |
| Aug 15, 2026 | 321 ms |
| Aug 22, 2026 | 346 ms |
| Aug 29, 2026 | 353 ms |
| Sep 5, 2026 | 350 ms |
| Sep 12, 2026 | 339 ms |
| Sep 19, 2026 | 325 ms |
| Sep 26, 2026 | 323 ms |
| Oct 3, 2026 | 322 ms |
| Oct 10, 2026 | 332 ms |
| Oct 17, 2026 | 350 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
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Use efficient cache lifetimes
4.7 s · 2.0 MB133 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
Reduce unused JavaScript
2.7 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
1.9 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 852 KiB 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.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 8
8/100Your mobile performance score is 8 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 4.7 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, Google CDN and Hubspot and others), adding 3.8 MB and 3.3 s of main-thread time.
Google CDN adds 961 ms
961 msGoogle CDN costs a phone 961 ms of main-thread work and 1.8 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.
Hubspot adds 505 ms
505 msHubspot costs a phone 505 ms of main-thread work and 409 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.
Facebook adds 314 ms
314 msFacebook costs a phone 314 ms of main-thread work and 345 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 319 ms. During a long task the page ignores taps.
TikTok adds 251 ms
251 msTikTok costs a phone 251 ms of main-thread work and 168 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.
1,573 HTML elements
The page has 1,573 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 207 KiB12 images could be 207 KiB 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.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 44 but mobile only 8. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 58 ms
58 msYour server sent the HTML in 58 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.97
0.97For real visitors the layout shifts by 0.97 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.9 s
17.9 sVisually, the page fills in at 17.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.983
0.983The layout shifts by 0.983 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 375 ms
375 msReal visitors wait 375 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 247 ms to 350 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Images and page weight
Page weight: 6.2 MB in 226 requests
6.2 MBYour homepage downloads 6.2 MB in 226 requests on a phone: scripts 3.8 MB (69), other files 812 KiB (37) and images 682 KiB (59). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (284 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.
5 images below the first screen load straight away
5 images further down the page (139 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.75 g of CO₂e: 210.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
2 checks passed
Every image has alt text
All 111 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
48 internal links, 16 external
The homepage links to 48 pages on ulaidiomas.edu.co and 16 external pages.
7 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “ULA es tu academia de inglés y francés en Colombia con más de 13 años de experiencia y 45.000 estudiantes formados. Cla…”.
One H1 headline
Your main headline reads: “Curso de inglés y francés en Colombia Online y Presencial”.
Title: 54 characters
Your title is a healthy 54 characters: “Academia de inglés y francés en Colombia | ULA Idiomas”.
Canonical URL set
The canonical URL is https://ulaidiomas.edu.co/.
Structured data in place
Structured data found: EducationalOrganization, ImageObject, Organization, Person and WebPage.
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://ulaidiomas.edu.co/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://ulaidiomas.edu.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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,224 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://ulaidiomas.edu.co/sedes/bogota, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a meta description
https://ulaidiomas.edu.co/contactos has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://ulaidiomas.edu.co/professional-communication, https://ulaidiomas.edu.co/blog and https://ulaidiomas.edu.co/sedes/medellin have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://ulaidiomas.edu.co/sedes took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
4 checks passed
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
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
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 723 words of copy
The homepage carries about 723 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks and 56 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and HubSpot.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
24 other companies contacted
Loading the homepage contacts 24 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 ulaidiomas.edu.co, 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 Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on ulaidiomas.edu.co, including 29 speed issues, 1 SEO issue 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.