Website review, no card needed
apap.com.do website review
Visit site (opens in a new tab)Reviewed 17 November 202653 issues · 91 checks
This review found 53 issues worth fixing on apap.com.do, 18 of them high impact, across 91 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.2 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.5 s |
| Oct 31, 2026 | 4.5 s |
| Nov 7, 2026 | 4.6 s |
| Nov 14, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 277 ms |
| Jun 6, 2026 | 280 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 284 ms |
| Jun 27, 2026 | 282 ms |
| Jul 4, 2026 | 286 ms |
| Jul 11, 2026 | 288 ms |
| Jul 18, 2026 | 282 ms |
| Jul 25, 2026 | 281 ms |
| Aug 1, 2026 | 282 ms |
| Aug 8, 2026 | 280 ms |
| Aug 15, 2026 | 281 ms |
| Aug 22, 2026 | 281 ms |
| Aug 29, 2026 | 281 ms |
| Sep 5, 2026 | 287 ms |
| Sep 12, 2026 | 294 ms |
| Sep 19, 2026 | 308 ms |
| Sep 26, 2026 | 315 ms |
| Oct 3, 2026 | 320 ms |
| Oct 10, 2026 | 319 ms |
| Oct 17, 2026 | 310 ms |
| Oct 24, 2026 | 307 ms |
| Oct 31, 2026 | 304 ms |
| Nov 7, 2026 | 299 ms |
| Nov 14, 2026 | 300 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
Speed
Use efficient cache lifetimes
2.9 s · 6.3 MB351 files are served with short cache lifetimes, so returning visitors download them again (6.3 MB).
Reduce unused JavaScript
4.3 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Google Tag Manager adds 5.0 s
5.0 sGoogle Tag Manager costs a phone 5.0 s of main-thread work and 4.8 MB 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.
Render-blocking requests
2.7 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.
Main-thread work: 15.2 s
A phone's processor spends 15.2 s on main-thread work while loading, 9.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 26
26/100Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, imi.chat and Facebook and others), adding 6.8 MB and 6.5 s of main-thread time.
Improve image delivery
2.3 MB68 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
1.7 MBAbout 1.7 MB of CSS is downloaded but never applied on this page.
Minify JavaScript
150 ms · 744 KiB744 KiB could be saved by minifying JavaScript.
imi.chat adds 777 ms
777 msimi.chat costs a phone 777 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 646 ms. During a long task the page ignores taps.
Facebook adds 336 ms
336 msFacebook costs a phone 336 ms of main-thread work and 479 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
2,103 HTML elements
The page has 2,103 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 27 KiB27 KiB could be saved by minifying CSS.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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: 22 ms
22 msYour server sent the HTML in 22 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 LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 14.3 s
14.3 sYour largest element takes 14.3 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: 68.7 s
68.7 sThe page becomes fully interactive after 68.7 s. Good is under 3.8 s.
Total Blocking Time: 4.3 s
4.3 sScripts block taps and scrolling for 4.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 310 ms
310 msReal visitors wait 310 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 277 ms to 300 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.1 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.0 MB in 697 requests
14.0 MBYour homepage downloads 14.0 MB in 697 requests on a phone: scripts 7.6 MB (222), images 4.6 MB (223) and stylesheets 719 KiB (111). Under 2 MB keeps phones on slow connections fast.
About 4.0 g of CO₂ per visit
3.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.97 g of CO₂e: 476.0 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
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.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 78 images in the HTML carry an alt attribute.
39 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: 39 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
Title is long (92 characters)
Your title is 92 characters, so Google will cut it off around 60: “Asociación Popular de Ahorros y Préstamos - APAP - Asociación Popular de Ahorros y Présta…”.
Meta description is short (41 characters)
Your meta description is only 41 characters: “Asociación Popular de Ahorros y Préstamos”. 70 to 160 characters is enough to sell the click.
24 H1 headlines
There are 24 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, CollectionPage, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://apap.com.do/wp-content/uploads/2019/06/favicon.jpg")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
146 internal links, 20 external
The homepage links to 146 pages on apap.com.do and 20 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://apap.com.do/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://apap.com.do/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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://apap.com.do/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 (1,743 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share 4 titles
https://apap.com.do/pyme/cuenta-flex-empresarial and https://apap.com.do/empresas/cuenta-flex-empresarial all use the title “Asociación Popular de Ahorros y Préstamos - Cuentas - APAP”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://apap.com.do/citas-apap, https://apap.com.do/canales, https://apap.com.do/sucursales-y-cajeros, https://apap.com.do/productos, https://apap.com.do/productos/remesas and https://apap.com.do/pyme/cuenta-flex-empresarial and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://apap.com.do/guia-autoayuda, whose canonical is https://apap.com.do/guia-autoayuda-preguntas-frecuentes-apapenline-apapmovilapap-com-do. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://apap.com.do/sucursales-y-cajeros, https://apap.com.do/guia-autoayuda and https://apap.com.do/productos have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://apap.com.do/canales, https://apap.com.do/productos/remesas, https://apap.com.do/pyme/certificados-financieros, https://apap.com.do/pyme/tarjetas, https://apap.com.do/pyme/servicios and https://apap.com.do/empresas/cuenta-flex-empresarial and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 64 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
14 small tap targets
14 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
14 distorted images
14 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
A 20-field form
Your longest form asks for 20 fields (0 required). Every extra field lowers completion.
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 337 words of copy
The homepage carries about 337 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Start search”.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 10 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
28 other companies contacted
Loading the homepage contacts 28 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 apap.com.do, 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
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on apap.com.do, including 27 speed issues, 6 SEO issues and 2 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.