Fix guides · UX & conversion
How to fix “Uses deprecated APIs”
Code that relies on browser features scheduled for removal. It works today and breaks later. How to find it and who needs to update it.
- Time to fix
- 15–60 minutes
- Skill needed
- Developer
- Who notices
- Visitors, once browsers remove the feature
Why it matters
Browsers retire old features over time. Chrome warns in the console when a page uses one that's on its way out, such as unload event handlers or synchronous requests on the main thread.
Nothing breaks yet, but when the feature is removed, whatever relies on it stops working, often without anyone noticing at first.
“Deprecated APIs are scheduled to be removed from Chrome. Calling these APIs after they're removed causes errors on your site.”
Before you start
- Your report names each deprecated feature and the file that uses it. Most come from old third-party scripts: analytics, chat, ads and outdated libraries such as old jQuery plugins.
- Update the script to its latest version first; vendors usually fix these. If it's your own code, Chrome Platform Status explains what to use instead.
Fix it on your platform
Shopify
- Check which app or theme file is listed. Update the app or theme, or contact its developer.
WordPress
- Update WordPress, your theme and plugins. If a plugin is no longer maintained, replace it.
Webflow
- Update or replace third-party scripts in your custom code and embeds. Webflow's own scripts are managed by Webflow.
Wix Managed by the platform
- Wix updates its own scripts. If an app or your custom code is listed, update or remove it.
Squarespace Managed by the platform
- Squarespace updates its own scripts. If code injection or an extension is listed, update or remove it.
Next.js
- Update dependencies (npm outdated shows which are behind), and replace deprecated APIs in your own code, such as unload listeners with pagehide.
Any other site
- Look up each warning on Chrome Platform Status, replace the API in your code, and update third-party libraries.
Check that it's fixed
- Reload with DevTools → Console open and look for deprecation warnings.
- Re-run your StudioLNC audit: the issue should be gone.
Find every issue like this on your site
Free audit of performance, accessibility, SEO and security, with fixes for your platform.