Skip to content
WorkMeridian Sensing Co.Reference build

A site an engineer can qualify you from.

A complete instrumentation site built to demonstrate a standard rather than describe one. Five product lines, full specifications as HTML, and a quote path that captures enough to be answered. Every figure on this page is measured from the build itself.

Sector
Pressure & flow instrumentation
Engagement
Reference build
Stack
Astro · Tailwind v4 · TS strict
Status
Complete
The problem

Industrial sites are built as brochures for buyers who read datasheets.

A technical buyer arrives at an instrumentation site already knowing roughly what they need. They are looking for a reason to disqualify you: a pressure range that stops short, an output signal that does not match the loop, a process connection that would need an adapter. That decision takes under a minute and it happens before anyone fills in a form.

Almost every site in this sector makes that minute harder. Specifications live in PDFs, so neither a search engine nor a person in a hurry can read them. Distributor information is missing entirely, which strands exactly the export enquiries worth the most. And the contact form asks for a name and a message — nothing an applications engineer could actually quote from, so the first reply is always a request for the information the form should have collected.

The result is a site that filters out qualified buyers and lets unqualified ones through, which is precisely backwards.

The approach

Publish the specification. Everything else follows from that.

The build treats the specification table as the primary content of the site rather than an attachment to it. Five product lines are documented across eighteen orderable SKUs, and every specification renders as HTML on the page — readable by a buyer, by a search engine, and by a procurement system scraping for a part number.

The quote request asks for process conditions instead of a message: range, output signal, process connection, wetted materials. That is enough for an applications engineer to answer in one reply rather than three, which is the difference between a lead and a conversation.

A distributor path exists because export enquiries are the ones a contact form loses most often. And no product photograph appears anywhere — every instrument is drawn as inline vector line-art, which is both lighter than a photograph and more accurate than a stock image of somebody else’s hardware.

Captured from the running site. The dark teal identity is Meridian’s own — a portfolio piece should not look like the studio that made it.

01 · HomepageThe specification argument starts immediately: certifications, lead time, and accuracy are above the fold rather than on an About page.
Meridian Sensing Co. — Homepage
02 · Product line — pressure transmittersFull specification tables as HTML. Five models, each with its own range, output and connection.
Meridian Sensing Co. — Product line — pressure transmitters
03 · Quote requestAsks for process conditions instead of a message, so the first reply can be an answer.
Meridian Sensing Co. — Quote request

Pressure transmitter series

Pressure range
0–100 to 0–5,000 psi
Accuracy
±0.25% FS
Output signal
4–20 mA, 2-wire
Process connection
1/4-18 NPT male
Wetted materials
316L stainless steel

One block from one product page, copied exactly as it ships. On most sites in this sector this table is a PDF, which means it is invisible to search and unreadable on a phone in a plant.

Measured from the build
Total page weight
76KB
Homepage, gzipped, every asset included. The median B2B page is roughly 2 MB.
Product lines documented
5
Eighteen orderable SKUs, every specification rendered as HTML. No PDF-only specs.
Stock photographs
0
Every instrument drawn as inline vector line-art.
What we would do differently

Meridian ships a 176 KB React runtime — 62 KB gzipped — to power two interactive pieces: a mobile navigation menu and the quote form. Page weight is still 76 KB gzipped against a roughly 2 MB median, which is why the headline figure is good.

It is the wrong trade anyway. Two small islands do not justify a framework runtime, and the technical buyer this site is built for is exactly the person who will open the network tab and find it. revostudios.co ships no framework at all for the same interactions — that is the standard we settled on after this build, and it came from this build.

This is published because both numbers are measured and only one of them flatters us. A studio that quietly reports the convenient figure has no business auditing anyone else’s site.

Your site should survive the same read.

Thirty minutes. We look at your current site first and arrive with the specifics — what a buyer hits, what they cannot find, and what it is costing you.