Company
How this site is built
We do not publish client logos, project counts or certifications without documentation. We publish this instead: what this site does, measured, and how to check it without taking our word for it.
Why this page exists
The rule that governs this site is simple and expensive: nothing that cannot be evidenced gets published. That removes everything an institutional site normally uses to persuade — client logos, counts of delivered work, certification badges, promised response times.
What is left is the work itself. This page describes how the site you are reading was built, because that is the only engineering evidence we can offer without asking you to take our word for it: it is open in front of you, and you can check every claim right now.
If Noryvex treats an institutional website with this much care, it is reasonable to infer what it does with a network that cannot go down. That is the entire argument, and it is verifiable.
Measured at every publish
These numbers are not written into the text: the site counts them during compilation. If a new page is created tomorrow, they change on their own — which is what stops this page from ageing into a claim that is no longer true.
- 121
- pages with no JavaScript
- 6
- pages that ship code
- 0
- requests outside this domain
- 2
- languages with their own addresses
out of 127 published — error screens excluded
form and search, in both languages
no analytics, pixel or chat
a missing translation breaks the build
What that means in practice
Each decision below cost work, and each is checkable from where you are sitting.
- Almost no page uses JavaScript
- Only the screens that genuinely need it — the form and the search — ship code. On every other page the runtime is stripped after compilation by our own script, which aborts the publish if the count does not match. How to check: turn JavaScript off in your browser and navigate. The whole site keeps working, except the form and the search.
- No third-party tracking
- There is no analytics, ad pixel, heatmap or chat widget. How to check: open the network tab in developer tools and reload. Every request goes to this domain — there is not a single outbound call.
- Contrast calculated, not eyeballed
- The brand blue fails WCAG AA as text on white, so it is never used as text — there is a separate tone for that, with verified contrast. The text over the opening photograph was measured pixel by pixel, at three screen widths, against the real image rather than an approximation.
- Accessibility checked by machine and by keyboard
- Before every publish, a real browser walks the main pages running an automated WCAG 2.2 AA audit, and a second test navigates the whole site with no mouse and no JavaScript. A publish with a violation does not go out.
- Two languages, with their own addresses
- This is not a Portuguese site with a language switcher bolted on: every page has a translated address, and the code’s type system requires both versions. If a translation is missing, compilation stops — half a page cannot be published.
- The fonts carry only the letters the site draws
- The font files are subset to contain only the characters that appear in the content. If new copy introduces a character outside the subset, the publish fails instead of showing an empty box on a reader’s screen.
What is not finished yet
A product catalog with manufacturer data, a document center searchable by equipment, and the first technical articles do not exist yet. The corresponding pages say so plainly, rather than simulating content.
It is the same rule applied to ourselves: we prefer a section that declares what is missing over a section that fills space.