How to partially repair the Wordpress/Joomla issues, if not migrating to a new platform. We strongly suggest migration to Webflow.
The issues with IANDS.org point to a critical combination of technical debt in our CMS structure and severe performance bottlenecks stemming from our server/hosting and code execution.
Our site is suffering from a fundamental technical breakdown that is destroying performance. The core problem is not just one metric, but the underlying server and CMS configuration.
Critical Technical Debt: The mixture of WordPress and Joomla 3, combined with many broken plugins, creates an unstable, insecure, and inefficient operating environment. This is the root cause of the slow server response.
Failing User Experience: The site has Failed the Core Web Vitals Assessment and earned a poor mobile Performance Score of 57 (out of 100).
Main Bottleneck: The single largest issue is the Time to First Byte (TTFB) at 2.6 seconds. This means it takes over two and a half seconds just for the server to start sending data, which is the longest step in the page load process and indicates a severe backend problem.
Assessment: Poor (Needs Improvement)
Root Cause: Slow server/TTFB and inefficient code.
Assessment: Critical
Root Cause: Slow LCP caused by server delay.
Assessment: Poor
Root Cause: Server-side code execution (CMS/broken plugins) and/or slow hosting.
Assessment: Needs Improvement (Target is < 2.5 s)
Root Cause: Direct result of the 2.6s TTFB and large image/asset sizes.
Assessment: Good (Target is < 200 ms)
Root Cause: Site is responsive once assets are loaded.
Assessment: Good (Target is < 0.1)
Root Cause: Content is visually stable during loading.
Conclusion: The site's stability and responsiveness are good (CLS, INP), but the fundamental problem is that the site takes too long to start loading and too long to display the main content (TTFB, LCP).
To achieve a significant performance improvement and fix our underlying issues, a multi-step approach is required.
1. Consolidate and Clean the CMS: The most urgent step is to decide on a single platform. We recommend:
Choose One CMS: Select a single platform (likely WordPress) and completely migrate or decommission the other (Joomla 3). Joomla 3 is also an outdated version (End of Life in 2023), which is a significant security risk.
Plugin Audit: Immediately remove or replace all broken plugins, and deactivate any plugins you are not actively using, as excess or bloated plugins dramatically slow down the server and database.
2. Upgrade Hosting to Reduce TTFB: To fix the 2.6 s TTFB, we must upgrade our hosting. Consider moving from shared hosting to a premium managed WordPress host, VPS, or cloud hosting.
3. Implement a CDN: Utilize a Content Delivery Network (CDN) to serve static files (images, CSS, JS) from servers closer to our users. This greatly reduces our server's load and lowers the TTFB.
1. Implement a Caching/Optimization Plugin: Install a reputable speed optimization plugin (e.g., WP Rocket, Autoptimize, WP Fastest Cache).
Minify/Defer Code: Use the plugin to minify CSS and JavaScript and defer the loading of non-critical JavaScript to eliminate render-blocking resources.
2. Optimize Images (LCP Element):
Compression and Format: Compress all images and convert them to next-gen formats like WebP.
Lazy Loading: Lazy load images that are "off-screen" or below the fold.
Preload Critical Image: Ensure the image causing the 3.5 s Largest Contentful Paint (LCP) is preloaded and properly sized to display as fast as possible.
Remediation or repair of the existing Wordpress/Joomla installation would be time consuming, expensive and ultimately futile. We recommend migration to a modern CMS system.