Website review, no card needed

tronwell.com logo

tronwell.com website review

Visit site (opens in a new tab)Reviewed 3 November 202639 issues · 83 checks

This review found 39 issues worth fixing on tronwell.com, 15 of them high impact, across 83 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
6.7 s4.3 sMay 16Oct 314.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.8 s
May 23, 20266.1 s
May 30, 20266.3 s
Jun 6, 20265.9 s
Jun 13, 20266.0 s
Jun 20, 20266.4 s
Jun 27, 20266.2 s
Jul 4, 20266.4 s
Jul 11, 20266.1 s
Jul 18, 20265.1 s
Jul 25, 20264.8 s
Aug 1, 20265.3 s
Aug 8, 20265.3 s
Aug 15, 20265.2 s
Aug 22, 20265.3 s
Aug 29, 20265.0 s
Sep 5, 20265.0 s
Sep 12, 20264.9 s
Sep 19, 20264.9 s
Sep 26, 20264.8 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.7 s
Oct 31, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
282 ms137 msMay 16Oct 31212 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026167 ms
May 30, 2026175 ms
Jun 6, 2026172 ms
Jun 13, 2026172 ms
Jun 20, 2026170 ms
Jun 27, 2026165 ms
Jul 4, 2026163 ms
Jul 11, 2026163 ms
Jul 18, 2026164 ms
Jul 25, 2026168 ms
Aug 1, 2026189 ms
Aug 8, 2026189 ms
Aug 15, 2026193 ms
Aug 22, 2026203 ms
Aug 29, 2026205 ms
Sep 5, 2026231 ms
Sep 12, 2026254 ms
Sep 19, 2026265 ms
Sep 26, 2026259 ms
Oct 3, 2026248 ms
Oct 10, 2026231 ms
Oct 17, 2026226 ms
Oct 24, 2026228 ms
Oct 31, 2026212 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 tronwell.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tronwell.com at 0.6 s0.6 s
  2. tronwell.com at 1.3 s1.3 s
  3. tronwell.com at 1.9 s1.9 s
  4. tronwell.com at 2.5 s2.5 s
  5. tronwell.com at 3.2 s3.2 s
  6. tronwell.com at 3.8 s3.8 s
  7. tronwell.com at 4.4 s4.4 s
  8. tronwell.com at 5.1 s5.1 s

Speed

9 to fix53
  • Reduce unused JavaScript

    6.1 s · 1.2 MB

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

  • Render-blocking requests

    3.2 s

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

  • Main-thread work: 4.0 s

    A phone's processor spends 4.0 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Use efficient cache lifetimes

    950 ms · 234 KiB

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

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    800 ms · 68 KiB

    2 images could be 68 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, ContentSquare and Facebook and others), adding 1.7 MB and 635 ms of main-thread time.

  • Google CDN adds 227 ms

    227 ms

    Google CDN costs a phone 227 ms of main-thread work and 736 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.

  • Google Tag Manager adds 98 ms

    98 ms

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

    290 ms · 81 KiB

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

  • Minify JavaScript

    210 ms · 31 KiB

    31 KiB could be saved by minifying JavaScript.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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 LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.2 s

    4.2 s

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

  • Real-user TTFB: 3.3 s

    3.3 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aprende inglés con resultados garantizados Completa el form…”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Real-user INP: 230 ms

    230 ms

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

  • Tap response (INP) got 37% slower for real visitors

    +37%

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

  • Total Blocking Time: 261 ms

    261 ms

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

  • 14 images without width and height

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 175 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 175 requests on a phone: scripts 2.8 MB (75), images 636 KiB (23) and other files 358 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 9 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.18 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9294
  • 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.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Aprende inglés con resultados garantizados” and “Aprende inglés con resultados garantizados”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 68 internal links, 18 external

    The homepage links to 68 pages on tronwell.com and 18 external pages.

5 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Aprende inglés en Tronwell Chile. Clases online y presenciales con metodología dual. Descubre el Tutor IA y domina un n…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Tronwell | Cursos de Inglés e Idiomas en Chile”.

  • Canonical URL set

    The canonical URL is https://tronwell.com/.

  • 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://tronwell.com/sitemap_index.xml.

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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,149 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tronwell.com/llms.txt (10 KiB, 36 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 pages without an H1

    https://tronwell.com/cursos-de-idiomas, https://tronwell.com/autoevaluacion and https://tronwell.com/programas-de-ingles have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • 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 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

    4 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

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.

  • Thin social proof

    Social proof on the homepage: 31 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 325 words of copy

    The homepage carries about 325 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 17 cookies set on arrival

    17

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 tronwell.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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on tronwell.com, including 21 speed issues, 3 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