LastingWeb

Free tool · No signup

Website modernization audit

Is your website built on technology that is holding it back? We look for outdated libraries, legacy setups and heavy assets, and tell you whether to patch or rebuild.

No signup · Results in ~40 seconds · Nothing stored except the shareable report

What we check and why

Signs of an ageing website

Websites age in ways visitors feel but rarely name: slowness, layouts that break on new phones, forms that fail without explanation. Underneath there are usually concrete technical causes. This audit combines our technology detector, a page-weight breakdown and a Lighthouse performance run to find them.

  • jQuery older than version 3, Bootstrap older than 4, AngularJS 1.x or Vue 2, which no longer receive regular updates.
  • Exposed PHP or web server versions, and many visible WordPress plugins.
  • HTTP/1.1 only, no CDN and no modern image formats.
  • Legacy Universal Analytics tags, table-based layouts and nomodule-only script bundles.
  • Large JavaScript downloads, unused code and slow Core Web Vitals.

Why it matters

Outdated components are a security issue first: end-of-life libraries and plugins stop receiving fixes, and automated scanners look for exactly those versions. They are also a performance issue, because older themes tend to load large frameworks on every page whether needed or not, and a maintenance issue, because fewer developers are willing to work on them.

For a firm, the practical question is cost. A site that needs repeated emergency fixes, cannot be edited without a developer and fails on mobile often costs more to keep than to replace.

Patch or rebuild?

The Modernization Score summarises the signals, with 100 meaning modern. A high score with a few warnings usually means patching: update libraries, remove unused plugins, enable HTTP/2 and a CDN, convert images. A low score combined with a poor performance score and an old CMS core often means the theme itself is the problem, and a rebuild on a lean, maintained stack is the more economical path.

Either way, start with the security-related findings, keep a backup before updating anything and test forms and key pages after each change.

If you rebuild, keep your URLs or redirect each old one to its new equivalent, carry over titles and descriptions, and run this audit again before launch so the new site starts with a clean report.

What the score is based on

The Modernization Score starts at 100 and deducts points for each outdated signal according to its impact, using the same scoring rules as the rest of the audit. It reflects what the site exposes publicly, so it can miss outdated components that leave no trace, and it does not judge visual design. Combine it with the performance and page-weight results to get a fuller picture.

Frequently asked questions

Is an old jQuery version dangerous?

Versions before 3.5 have publicly known cross-site scripting issues in some functions. The risk depends on how the site uses them, but updating or removing jQuery is the safer path.

Does modern mean using React or Next.js?

No. A well-maintained WordPress site or plain HTML can score very well. Modern here means maintained components, efficient delivery and good performance, not a particular framework.

Can you tell how old my site is?

Not exactly. We can see component versions and patterns that point to the era a site was built in, but not its launch date.

What does a rebuild typically involve?

Content review, a new design or theme, migration of pages with redirects for changed URLs, and testing. LastingWeb's website packages cover this for small firms.

Done for you

Want these fixed? We build it right.

LastingWeb builds fast, secure, compliant websites for professional firms — hosting, TLS, email authentication and GDPR-friendly analytics included.

See packages