43. SPSS AMOS - How to Improve Model Fit using CB-SEM (Confirmatory Factor Analysis)
Based on Research With Fawad's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Start by cleaning the dataset: correct inconsistent values, assess missingness, and apply imputation before running CFA.
Briefing
Improving a weak confirmatory factor analysis (CFA) model fit in AMOS hinges on a disciplined loop: clean the data, then adjust the measurement model using only defensible changes, and finally re-check fit indices after each modification. The workflow starts with data quality—screening for incorrect or inconsistent values, assessing missingness, and applying data imputation—because poor data can masquerade as model problems.
Once the dataset is ready, the process shifts to AMOS model diagnostics. The first pass checks whether the measurement model is structurally sound: low factor loadings (with a practical cutoff around standardized regression weights below 0.5) and problematic residuals or modification indices. If fit is poor—often signaled by a significant chi-square and weak comparative/absolute fit statistics such as CMIN above 5, GFI/AGFI below .90, CFI/TLI below .90, and RMSEA far above .08—the modeler then targets specific, localized issues rather than making broad changes.
The transcript’s core method is iterative model refinement using modification indices and residual diagnostics. Large modification indices (the example uses a threshold around 4, with the option to raise it) guide where correlated error terms might be added. In the walkthrough, adding a covariance between error terms E11 and E12 produces only limited improvement, but subsequent targeted covariances—such as between E10 and E11 (when allowed), E4 and E5, and E1 and E2 (and E1 and E5 when feasible)—gradually push fit closer to acceptable ranges. Even when fit indices improve, the transcript stresses that changes should be constrained: covariances are drawn only between error terms of indicators belonging to the same construct.
After modification indices are exhausted, the next diagnostic layer is standardized residual covariances. Values exceeding about 2 flag indicators that still misbehave. In the example, the indicator sl3 within “servant leadership” is identified as problematic and removed, which improves several fit measures. A second pass checks standardized regression weights again; a low-loading indicator is removed if needed. However, removing an indicator can break the model’s reference scaling, which is why the transcript highlights a critical fix: after deleting an indicator, the remaining factor must be re-referenced by fixing a parameter to 1 (so the model has a stable metric).
The final stage compares fit indices holistically. After the last adjustments, the model fit becomes “very good” on most metrics—close to the desired threshold for chi-square/CMIN and improved SRMR after running the standardized RMR plugin (the example reports SRMR around 0.3, described as very good). RMSEA remains poor in the example, but with SRMR and other fit indicators acceptable, the model is treated as having a reasonable overall fit for reporting. The takeaway is that model fit improvement in AMOS is less about chasing a single statistic and more about a controlled sequence of data checks, targeted error covariances, and indicator removal guided by residuals—while maintaining proper factor scaling.
Cornell Notes
The transcript lays out a step-by-step AMOS (CB-SEM/CFA) process for improving model fit when initial fit indices are weak. It begins with data preparation: remove inconsistent values, handle missing data via imputation, and then run the CFA with standardized estimates, modification indices, and residual moments enabled. Model refinement proceeds iteratively: check standardized regression weights (e.g., below 0.5), add only same-construct error covariances suggested by large modification indices, and then inspect standardized residual covariances for values above about 2. If a problematic indicator is removed, factor scaling must be restored by fixing a parameter to 1. The final decision weighs multiple fit measures, with SRMR (via a plugin) and other indices used to judge whether the model is reasonably acceptable even if RMSEA stays high.
Why does the workflow start with data checks before touching the AMOS model?
What are the first diagnostic signals of poor CFA fit in the AMOS output?
How does the refinement process decide what to change first: factor loadings, modification indices, or residual covariances?
What constraint governs adding covariances based on modification indices?
Why must the model be re-scaled after deleting an indicator?
How does the transcript handle conflicting fit indices, especially when RMSEA stays poor?
Review Questions
- What specific AMOS outputs and thresholds are used to judge whether the initial CFA fit is unacceptable?
- When adding covariances from modification indices, what rule limits which error terms can be correlated?
- After removing an indicator, what parameter-fixing step restores factor scaling, and why is it necessary?
Key Points
- 1
Start by cleaning the dataset: correct inconsistent values, assess missingness, and apply imputation before running CFA.
- 2
Enable standardized estimates, squared multiple correlations, residual moments, and modification indices in AMOS to support targeted diagnostics.
- 3
Use standardized regression weights as an early screen; consider deleting indicators with loadings below about 0.5 if they remain problematic.
- 4
Add covariances only between error terms of indicators belonging to the same construct, guided by large modification indices (e.g., far above the default threshold).
- 5
Iterate: rerun the model after each set of changes and re-check fit indices (CMIN, GFI/AGFI, CFI/TLI, RMSEA).
- 6
After modification-index adjustments, inspect standardized residual covariances; remove indicators tied to residual covariance values above about 2.
- 7
If an indicator deletion removes the factor reference point, fix a parameter to 1 to re-establish scaling, then rerun and re-check fit (including SRMR via the standardized RMR plugin).