Avada icons that turn into empty squares usually need a font, CSS or icon-family check, not a theme rollback. Inspect one broken icon and its font request before changing the entire site. A square in the mobile menu can hide an important navigation control even when the surrounding header looks normal.
Start with one broken and one working icon
Record the affected page, whether you are logged in, and the installed Avada, Core and Builder versions. Choose a working icon if one exists. Compare both in the same browser session. If only a custom icon set fails, investigate that set before treating every Font Awesome asset as broken.
In developer tools, inspect the broken element and its pseudo-element. Note the computed font family, weight and content value. Then open Network, filter for fonts, and reload. A missing request suggests that the expected stylesheet or font declaration never applied. A request returning an error points to delivery instead.
| What you observe |
What to investigate |
| Font request returns 404 |
Generated CSS references a missing or old path |
| HTTPS page requests an HTTP font |
Mixed-content URL left after migration |
| Font loads but one family is missing |
Enabled subset, icon style or custom set |
| Font loads but computed family is ordinary text |
Broad custom CSS overriding icon styles |
Repair the demonstrated cause
Avada's missing-icons guidance recommends checking site protocols and resetting Avada caches after updates. Confirm the site's intended HTTPS configuration before changing URLs. On a live site, an incorrect WordPress Address change can lock you out.
Use Avada's supported cache reset, then clear the affected public page and CDN assets if they still reference the old files. Repeat the same font request. Repeatedly clearing unrelated caches without comparing the URL makes it difficult to tell whether regeneration did anything.
For a family-specific problem, check the enabled Font Awesome subsets and the icon's selected style. Avada's official icon troubleshooting walkthrough also covers broad CSS overrides and custom-set naming. Do not paste a new Font Awesome CDN snippet into the header as a first repair. Two different versions can leave the editor and frontend using different glyph mappings.
Asset: Expected font loads. Style: Correct family and weight. Control: Menu still opens. Access: Useful accessible name. Explanatory checklist, not a customer test result.
Test the control, not only the glyph
Recheck the mobile menu, search button and any icon-only contact link. Confirm that each has a meaningful accessible name, can receive keyboard focus and still performs its intended action. A visible symbol is not enough if a CSS repair also hides its label or removes its click target.
If the font is served from a separate asset hostname and the browser reports a CORS error, ask the host to review that font response. Do not relax unrelated security headers or change every site's CORS policy.
Keep the failed URL, response status, overridden selector and corrected version in the handoff. If sections or headers are also displaced, use the broader Avada layout recovery guide. HandL WP can repair the affected Avada assets while preserving the supported security-update state.
References reviewed October 12, 2026. Examples are explanatory, not customer test results.