Sirius Semiconductors is a Vietnamese microelectronics technological hub. The site's job is to make an unfamiliar supplier legible to international buyers evaluating it against established competitors.
A component supplier is assessed on capability and trust, usually by someone comparing several vendors in a single session. The site had to state what Sirius does and why it wins on the first screen, in a second language, without the vagueness that corporate manufacturing sites default to.
The headline states the category in three words — microelectronics technological hub — and the sentence under it names the two competitive claims plainly: time to market and price to quality. One action follows, contact sales, because that is the only thing a qualified visitor wants.
The first line is what the company is, set in a monospaced display face that reads as technical without resorting to circuit-board decoration. Underneath, one sentence carries the two claims a buyer is actually comparing: speed to market and the price-to-quality ratio.
Everything a manufacturing site is tempted to lead with — history, facility photography, mission language — sits further down where it supports a decision already forming.
There is a single button: contact sales. A buyer at this stage does not want a newsletter, a whitepaper or a demo request, and offering them dilutes the one thing that matters.
The audience is international and mostly reading in a second language. Sentences are short, claims are literal, and the language switcher sits in the header rather than buried in a footer.
The palette — deep blue to black with a single light accent — keeps long stretches of text legible on the large monitors this audience uses, and holds up on a phone for the buyer checking a supplier between meetings.
Procurement search is specific and unbranded: capability plus region. Page titles and descriptions are written around those pairings rather than the company name, so the site is findable by buyers who have never heard of it.
Next.js, served behind nginx, with the multilingual routing handled at the framework level so each language has its own indexable URL rather than a client-side toggle.
Because a qualified buyer at this stage wants a conversation with sales. Newsletters and whitepaper downloads dilute that without adding a route anyone in the funnel is asking for.
Routing is handled at the framework level so each language has its own indexable URL, rather than a client-side toggle that search engines cannot follow.
Most of the audience is reading in a second language and comparing several suppliers in one session. Short, literal claims survive that; marketing language does not.
