The site looks fine. That is exactly the problem.
Open ten engineering company websites and most will look competent, a clean template, decent photography, a homepage that does not embarrass anyone in a client meeting. Competent is not the bar. The bar is whether a procurement or technical buyer, who has never met your team and has ninety seconds to spare, can tell what you actually do and for whom.
A site can pass every design review internally and still fail that test, because staff already know the company’s capabilities and read gaps in the copy without noticing them. A first-time visitor has no such context. They either get an answer fast, or they open the next tab.
The list below is ordered roughly by how often it appears, not by severity, a few of these will cost you more RFQs than the others depending on your specific buyer. Read it against your own site with that ninety-second test in mind.
Which mistake to fix first: impact versus effort
| Mistake | Typical fix effort | Typical impact on RFQs |
|---|---|---|
| Contact buried, no qualification | An afternoon | High, often the fastest measurable win on this list |
| Tagline with no capability map | A day or two of content rewrite | High, this is what actually gets you past the first ninety seconds |
| Photos that prove nothing | A few days of writing project narratives | Medium-high, compounding over time as the proof library grows |
| Slow-loading galleries | A day of compression and testing | Medium, invisible until you test on a real mobile connection |
| No sector filtering | A few days of content restructuring | Medium, higher for firms serving genuinely distinct sectors |
| Certifications buried in a PDF | An hour | Medium, cheap to fix, easy to forget |
| Forms with no qualification | An afternoon | Medium, mostly saves internal time rather than winning new RFQs directly |
| Irrelevant blog content | Ongoing, no quick fix | Low to medium, and slow to compound |
The eight patterns, at a glance
- 1. Homepage slogan with no capability map underneath it
- 2. Project galleries without scope, context or outcome
- 3. Contact information buried in the footer only
- 4. No sector or industry filtering to help buyers self-identify
- 5. Uncompressed, slow-loading image and video galleries
- 6. No differentiating certification or HSEQ signals visible
- 7. Enquiry forms that ask nothing useful for qualification
- 8. Blog or news content unrelated to real buyer questions
1. A tagline where a capability map should be
"Engineering excellence since 1998" tells a buyer nothing they did not already assume you would claim. A procurement officer scanning several firms in one sitting moves fastest toward whichever site answers "what do you actually do" without requiring a scroll and a guess.
Underneath any brand line, add a plain capability map, grouped, buyer-recognisable categories of what you design, fabricate, install or maintain. This single addition, on its own, tends to move more RFQs than any visual refresh.
2. Photos that prove nothing
A gallery of finished-project photography with zero accompanying detail asks a technical reader to take your competence on trust. What actually convinces them is scope, a real constraint that made the job non-trivial, and an outcome, even phrased generally where confidentiality requires it.
If a client contract restricts naming the project, write an approved general narrative rather than dropping proof from the site altogether. A described-but-unnamed project still demonstrates how you think through a problem; an unexplained photo demonstrates nothing beyond "we own a camera."
3. Contact buried, no qualification
| Pattern | Why it hurts | The fix |
|---|---|---|
| Contact link only in the footer | Buyers give up before finding a way to reach out | A visible RFQ/contact CTA on every capability and project page |
| Generic "message us" box | Forces manual back-and-forth to understand the enquiry | Ask for application, timeline, location and documents upfront |
| No response-time expectation stated | Buyers assume a slow reply and move on | State a realistic response commitment near the form |
4. One undifferentiated list for every sector
A firm serving mining, energy, FMCG and infrastructure clients with a single flat services list forces every visitor to guess whether their sector counts as relevant experience. Sector pages or filters let a buyer confirm fit fast and see proof specific to their world, rather than a generic capability list that could belong to any firm in any industry.
This does not require rebuilding the whole site into a sector-first structure overnight. A simple filter on the existing project gallery, or a short "who we work with" line added to each service page, often does most of the job. Reserve full dedicated sector pages for the two or three industries that actually generate most of your enquiries.
5. Galleries that take four seconds to load, on a good connection
Engineering sites are naturally image and video heavy (machinery, facilities, finished projects) which makes them especially exposed when media is not compressed or sized properly. A buyer researching on a mobile connection between meetings will not wait through a slow gallery to reach your proof; they will simply not see it.
This gets missed internally because the team that built the site almost always tests it on a fast office connection, where the problem is invisible. Test on a mid-range Android phone using mobile data before deciding the gallery is fine.
6. Certifications that exist only in a PDF nobody opens
HSEQ standards, quality systems and relevant compliance are exactly the kind of signal that reduces a procurement buyer’s perceived risk, but only if they are visible on the page, not buried in a downloadable document three clicks away.
The fix is genuinely small: a certification strip near the top of the homepage and on every capability page, each certification named and dated, with the full document linked for anyone who wants to verify it. A buyer scanning quickly should see that you are certified before they have to go looking for proof of it.
7. Forms built for volume, not for fit
A generic contact form treats a serious RFQ and a casual question as the same thing, which means your team has to manually sort them. A form that asks for application, timeline, location and documents does that sorting automatically, and tends to discourage enquiries that were never a realistic fit in the first place.
Be careful not to overcorrect into a form so long that a genuinely qualified buyer abandons it halfway through. Four or five well-chosen fields (application, rough timeline, location, and a file upload) usually capture what sales actually needs without turning the enquiry into a job application.
8. A blog full of things no buyer is searching for
Company announcements and generic industry commentary rarely rank and rarely get read by anyone actually evaluating your firm. Content earns its place either by answering a specific application or specification question, or it should not exist, see our companion piece on digital marketing for mechanical engineering companies for the content approach that actually pairs with a fix like this.
Fixing this in order: rewrite before redesign
- Run the eight-item list against your own siteScore honestly, most sites hit at least three or four.
- Fix copy and structure firstCapability map, project context, visible contact, usually possible inside your current template.
- Fix technical performance nextCompress media, test on mobile networks, confirm forms actually reach a person.
- Redesign only if the template genuinely cannot hold the fixA rebuild is justified by broken information architecture, not by aesthetic fatigue.
If procurement cannot tell what you do in ten seconds, the site is failing, no matter how premium it looks in a screenshot.
Nexus industrial web principle
The twenty-minute self-audit before you call anyone
Open your site on a mid-range phone on mobile data and try to identify your own capabilities, relevant proof and a contact path within ten seconds, without using any prior knowledge of the company. Note every point where you hesitated or had to think about where to click, that hesitation is the same friction a real buyer feels, just easier to spot once you deliberately look for it.
This exercise alone usually surfaces two or three items from the list above, and it gives you a specific brief if you eventually bring in outside help rather than a vague "make it better."
The Nexus take: a rewrite audit before you commission anything bigger
- Homepage answers "what do you do and for whom" without a scroll
- Every project or gallery entry has at least one line of scope, constraint or outcome
- A contact or RFQ path is visible on every capability and project page, not only the footer
- Certifications are named and dated on the page itself, not only in a downloadable PDF
- The site loads acceptably on a mid-range phone using mobile data, tested directly rather than assumed
A redesign fixes a template that cannot hold your proof. A rewrite fixes proof that was never actually written down.
Nexus industrial web principle
A worked scenario: the fix that took an afternoon
A structural steel fabricator’s homepage read "Delivering engineering excellence across Southern Africa" above a hero image of a factory floor, with a contact link only in the footer. The team assumed a full redesign was the only way forward, and had been putting off the budget for it for over a year.
Instead, they replaced the tagline with a plain capability line ("structural steel fabrication for mining, energy and infrastructure projects, 5 to 500 tonnes") added a visible "Request a quote" button to the header, and moved three certification badges from a buried PDF onto the homepage itself. Nothing about the visual design changed. The change was entirely content and structure, completed inside an existing template in an afternoon.
This is the pattern worth internalising: most of the eight mistakes on this list are writing and structure problems wearing a design complaint’s clothing. Fix the words and the information architecture first, and you will often discover the "outdated" design was never really the problem.
What to do next
This week: run your homepage and top project page through the list above and fix the single biggest gap, usually the capability map or contact visibility.
This month: test your load speed on a mid-range phone and compress your heaviest galleries.
See our engineering and industrial website design guide for the fuller build, and how engineering firms generate B2B leads online for the demand side of this system.
