Built for Internet Explorer
Your site still carries workarounds for Internet Explorer. It has not been touched in a decade.
How to see it yourself, in a minute
- View the page source and search for “lt IE”, “html5shiv” or “respond.js”.
- Any of them means the site was built to keep Internet Explorer happy, which dates it to before 2015.
Or paste your address into the free audit, which checks this and seventeen other faults in ten seconds.
Why it matters
Code written to keep Internet Explorer happy dates a site to before 2015. It slows every page for the browsers people actually use and almost always travels with the other faults on this list.
Code written for a browser that no longer exists slows every page for the browsers people actually use, and it almost always travels with the other faults on this list: not mobile, insecure, no analytics. It is less a fault than a diagnosis.
How we fix it
We strip the dead code, modernise the templates, and retest on current browsers and phones. Usually this is the moment to rebuild rather than patch.
- Strip the dead code and modernise the templates.
- Retest on current browsers and phones.
- Usually this is the moment to rebuild rather than patch; we say which after looking.
How long: A day, or part of a rebuild.
Questions people ask about this
- Is a site from 2014 really that bad?
- It was fine in 2014. Phones, browsers, Google and your customers have all changed since, and the site has not.
People usually find this page by searching
- “old website needs updating”
- “website built years ago modernise”
- “website redesign cost”
Has your site got it?
Paste your address. This and seventeen other faults, checked in seconds.
Free, on screen in about ten seconds, no call. We fetch your homepage once, the way a visitor's browser does, and nothing else.
Or fix the lot at once
If the audit finds five or more, a rebuild is usually cheaper than five fixes. Prices are on the page.