Working with jQuery?

jQuery site breaking or outdated? We fix it.

Most jQuery code that reaches us was written years ago, by someone who has long since moved on, and now it is wedged between a modern browser and a WordPress update that keeps breaking it. We work out which version is actually running, what is calling it, and what can safely change.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

console.log

still failing

What it is

jQuery at a glance

jQuery is a JavaScript library that was created by John Resig in 2006 to make cross-browser JavaScript tolerable. It wrapped DOM traversal, events, Ajax and animation behind a short, forgiving syntax at a time when every browser disagreed on the details.

It became ubiquitous through the late 2000s and the early 2010s, and it is still bundled by default with WordPress. The latest major line is 3.x, with 3.7.1 as a recent release, and jQuery Migrate exists to help old code run on newer versions. Modern browsers now cover most of what it was built to paper over, and a lot of its API is built into the standard DOM through querySelector, fetch and classList.

Type
JavaScript DOM and animation library
First released
2006
License
MIT
Maintained by
jQuery Foundation, now part of the OpenJS Foundation
Typically used for
Legacy sites, WordPress themes and plugins, enterprise intranets, dated admin UIs

The honest version

jQuery pros and cons

No technology is all upside. This is where jQuery earns its place and where it tends to cause trouble.

Where jQuery is strong

  • It once hid the browser warsBack when every browser read the DOM slightly differently, jQuery smoothed it over and let one piece of code work everywhere. That is the reason it spread so far so fast.
  • It is still everywhereW3Techs puts jQuery on roughly 70 to 80 percent of all websites, largely because WordPress still ships it. If you work on the open web, you will touch it eventually.
  • The selector syntax is simpleGrabbing elements with a CSS selector and chaining a few calls is still a quick way to get something working, especially inside an existing jQuery codebase.
  • Plenty of plugins still aroundDate pickers, carousels, sliders, modals and form helpers were written as jQuery plugins for years, and many of them continue to do the job on established sites.
  • Developers everywhere have seen itAlmost anyone who has done front-end work has touched jQuery at some point, which keeps the cost of handing a project over reasonable.

Where jQuery bites

  • Modern browsers no longer need itThe cross-browser shims jQuery was built to provide are largely baked into the platform now. Loading it just to run a handful of selectors is weight without a matching benefit.
  • It is a performance taxPulling jQuery and often jQuery UI onto every page can add well over a hundred kilobytes of script before any of your own code runs. On slow networks that shows up clearly in real page load times.
  • Old versions carry known CVEsThe 1.x and 2.x lines and everything up to 3.4.0 have documented XSS issues. Sites pinned to code.jquery.com at version 1.7.2 are still common, and every visitor runs that code.
  • jQuery UI has been coasting since 2016The last stable jQuery UI release landed in 2016 and the project has been in long-term maintenance mode ever since. New browsers keep moving while it does not.
  • Plugins get abandonedMost plugins were written by one person in their spare time, and many have not been updated for the current jQuery or the current WordPress. They work until a dependency shifts, and then they do not.
  • Inherited sites load several versionsIt is routine to open an old site and find jQuery loaded three times, once by the theme, once by a plugin, and once by a widget. The conflicts are subtle and the bug reports are maddening.

Sound familiar?

Common jQuery problems we fix

The jQuery problems that bring people to us, and what you have once each one is fixed.

$(...).live is not a function

Scripts stopped working after a WordPress update

A WordPress core update swapped the bundled jQuery and old plugin code was calling methods that were removed years ago, such as .live or .size.

Code brought up to modern jQuery

jQuery.XSS: known vulnerability

The site is running a vulnerable jQuery

An old theme or CDN link pins the site to a jQuery version with published XSS issues, and every visitor loads that script.

Pinned to a patched release

multiple jQuery versions loaded

Two or three jQuery versions on the same page

Theme, plugin and a third-party widget each load their own copy of jQuery, and they quietly overwrite each other until something breaks.

One version, loaded once

slim build missing: jQuery.ajax

Ajax calls fail after a theme refresh

A new theme shipped the slim build, which drops Ajax and effects, and existing plugin code expects the full build to be there.

Right build loaded for the site

110KB of unused JS from jQuery UI

Lighthouse scores dropped and will not recover

jQuery and jQuery UI are loaded on every page, including ones that never use them, dragging Core Web Vitals down.

Only loaded where it is actually used

JQMIGRATE warnings in console

jQuery Migrate is papering over old code

The console fills with deprecation warnings every page load, which means the next upgrade will remove something the site still depends on.

Deprecations resolved, Migrate retired

last plugin update: 2017

The slider or date picker plugin is abandoned

A jQuery plugin that has not seen a release in years is now the reason the site cannot move forward on anything else.

Replaced with something maintained

legacy jQuery front end

The whole front end is dated jQuery

Years of accumulated jQuery across a site that would be smaller, faster and easier to hire for as vanilla JavaScript or a modern framework.

Modernised in stages, nothing broken

What we do

jQuery help, from one broken script to a full modernisation

Call us for one failing plugin, or hand us the whole legacy front end.

Rescue
Front end broken after an update, errors across the console, pages not working. We get it functional first and find the cause second.
Upgrades
Moving from jQuery 1.x or 2.x to 3.x, retiring jQuery Migrate, and replacing abandoned plugins with maintained alternatives.
Security
Patching known CVEs, removing vulnerable CDN pins, and auditing third-party scripts that ride in on the same page.
Performance
Trimming unused jQuery UI, deduplicating multiple jQuery copies, and loading only what each page actually needs.
Modernisation
Rewriting jQuery front ends as vanilla JavaScript or React, in stages, so the site keeps working the whole way through.
Managed Tech
Ongoing updates, monitoring and a team to call when the next WordPress release ships a newer jQuery.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running jQuery alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

jQuery questions

Something else? Call+1 737 727 7327

Should we remove jQuery from our WordPress site?

Not always, and not in a hurry. If the theme and the plugins depend on it, removing it breaks the site. The useful first step is usually to make sure only one modern version loads, that it is a patched release, and that jQuery UI is only pulled in where it is actually used.

Can you upgrade an old jQuery 1.x or 2.x codebase to 3.x safely?

Yes. We run jQuery Migrate against the existing code to list every deprecated call, fix those in place, and then retire Migrate. The upgrade is tested on a copy of the site before anything changes on the live one.

Can you take over a legacy jQuery site from a previous developer?

Routinely. We work out which jQuery is really loading, which plugins are in play, and which code is still in use. From there you get a plain list of what is safe to keep, what should be patched, and what is worth replacing.

Our jQuery plugin stopped working after a WordPress update, can you fix it?

Usually yes. WordPress periodically bumps the bundled jQuery, most recently from 1.12 to 3.5 in WordPress 5.6, and plugins written against the older API often call methods that no longer exist. We patch the plugin or swap it for a maintained equivalent.

Can you modernise a jQuery front end to vanilla JS or React?

Yes, and we do it in stages. The site keeps working while the jQuery layer is peeled back page by page, so there is no big-bang rewrite and no window where the site is down.

How much does jQuery help cost?

Estimates are free. Describe what is breaking or what you want to modernise and you get a price before any work starts.

Free estimate

jQuery giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.