Website review, no card needed

aprofe.org.ec logo

aprofe.org.ec website review

Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 80 checks

This review found 42 issues worth fixing on aprofe.org.ec, 19 of them high impact, across 80 checks. The most urgent: improve image delivery. 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.9 s2.1 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.6 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.2 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20262.7 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
147 ms130 msMay 2Oct 17140 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026140 ms
May 9, 2026141 ms
May 16, 2026144 ms
May 23, 2026145 ms
May 30, 2026144 ms
Jun 6, 2026145 ms
Jun 13, 2026144 ms
Jun 20, 2026143 ms
Jun 27, 2026143 ms
Jul 4, 2026142 ms
Jul 11, 2026139 ms
Jul 18, 2026139 ms
Jul 25, 2026140 ms
Aug 1, 2026142 ms
Aug 8, 2026141 ms
Aug 15, 2026139 ms
Aug 22, 2026138 ms
Aug 29, 2026132 ms
Sep 5, 2026138 ms
Sep 12, 2026138 ms
Sep 19, 2026139 ms
Sep 26, 2026140 ms
Oct 3, 2026138 ms
Oct 10, 2026139 ms
Oct 17, 2026140 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 aprofe.org.ec (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aprofe.org.ec at 0.4 s0.4 s
  2. aprofe.org.ec at 0.8 s0.8 s
  3. aprofe.org.ec at 1.1 s1.1 s
  4. aprofe.org.ec at 1.5 s1.5 s
  5. aprofe.org.ec at 1.9 s1.9 s
  6. aprofe.org.ec at 2.3 s2.3 s
  7. aprofe.org.ec at 2.6 s2.6 s
  8. aprofe.org.ec at 3.0 s3.0 s

Speed

7 to fix53
  • Improve image delivery

    6.0 s · 3.3 MB

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

  • Reduce unused JavaScript

    2.4 s · 445 KiB

    About 445 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 769 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 53

    53/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 883 KiB and 674 ms of main-thread time.

  • Google Tag Manager adds 546 ms

    546 ms

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

    150 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 19 KiB

    About 19 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.

  • Minify CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 661 ms of it running JavaScript. That is comfortably low.

  • Server response: 83 ms

    83 ms

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

Core Web Vitals

9 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 CLS: 0.37

    0.37

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

  • Largest Contentful Paint: 30.6 s

    30.6 s

    Your largest element takes 30.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “boton_de_pago_agendamiento.jpg”.

  • Time to Interactive: 31.5 s

    31.5 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • 38 images without width and height

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

  • Total Blocking Time: 305 ms

    305 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 92 ms

    92 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 782 ms

    782 ms

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

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

    -24%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.4 s to 2.7 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 fix33
  • Page weight: 7.0 MB in 103 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 103 requests on a phone: images 5.0 MB (43), scripts 1.8 MB (32) and fonts 149 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.00 g

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

Accessibility

5 to fixGoogle 8088
  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 6 tap targets too small

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

  • Headings skip levels

    Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 14 automated accessibility rules passed

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

SEO

8 to fixGoogle 6649
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (14 characters)

    Your title is only 14 characters: “Aprofe -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.

  • Meta description is short (59 characters)

    Your meta description is only 59 characters: “APROFE (Asociación Pro Bienestar De La Familia Ecuatoriana)”. 70 to 160 characters is enough to sell the click.

  • 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 X (Twitter) card tag

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

  • 60 internal links, 20 external

    The homepage links to 60 pages on aprofe.org.ec and 20 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://aprofe.org.ec/sitemap.xml.

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://aprofe.org.ec/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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-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.

Other pages

5 to fix50
  • 8 linked pages are broken

    Your homepage links to https://aprofe.org.ec/servicios, https://aprofe.org.ec/paginas/showAllServiciosDetalle/11/1, https://aprofe.org.ec/paginas/showAllServiciosDetalle/12/2, https://aprofe.org.ec/paginas/showAllServiciosDetalle/13/3, https://aprofe.org.ec/paginas/ver/15 and https://aprofe.org.ec/paginas/ver/16 and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a title

    https://aprofe.org.ec/paginas/ver/1 has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://aprofe.org.ec/paginas/ver/1 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://aprofe.org.ec/paginas/ver/2/0, https://aprofe.org.ec/paginas/ver/3/0, https://aprofe.org.ec/paginas/ver/7/0, https://aprofe.org.ec/paginas/ver/59/0, https://aprofe.org.ec/paginas/ver/69 and https://aprofe.org.ec/paginas/showAllServicios use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://aprofe.org.ec/paginas/ver/1, https://aprofe.org.ec/paginas/ver/2/0, https://aprofe.org.ec/paginas/ver/3/0, https://aprofe.org.ec/paginas/ver/7/0, https://aprofe.org.ec/paginas/ver/59/0 and https://aprofe.org.ec/paginas/ver/69 and 1 other 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 22 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: 23 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 16 words

    The homepage has only about 16 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

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

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 aprofe.org.ec, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Employees
140

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on aprofe.org.ec, including 16 speed issues, 8 SEO issues and 4 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