What breaks and why it is expensive
Markup ages in silence: a CMS update shifts a grid, a new banner breaks the hero, someone edits a template and three pages drift. The visitor sees a button hiding text on an iPhone, a catalog overflowing on a tablet, a form whose send button vanished at 360 pixels. The cost is direct: 57% of users will not recommend — or even stay with — a business whose mobile site renders badly, and every broken screen on the checkout path is measurable in abandoned carts. Markup debt also compounds: each quick patch over a broken grid makes the next fix harder.
How we handle tasks
Every task goes through the same discipline: reproduce, localize, fix, verify. First we see the breakage on real devices and name the exact conditions — width, browser, state. Then we find the cause in the layout system, not the symptom: a broken card is often one wrong flex rule three levels up. The fix is made so it cannot break the neighbours, checked against the full resolution set and in Chrome, Safari and Firefox. Screenshots before and after are attached to every task, so you see what changed without opening a code editor. Batch tasks ship with a summary report.
Responsiveness as a system, not patches
If the mobile version is held together by media-query patches, every new block will break it again. Where the grid itself is sick, we repair the system: a consistent container and breakpoints, fluid images, spacing that scales, components tested at six control widths from 320 to 1920. The result is a layout where new pages and blocks inherit correctness instead of fighting it — future edits get cheaper, and "it looks fine on my laptop" stops being the QA process. Full-site responsive repair is quoted separately, since it touches every template.
Cross-browser and code quality
Safari alone can turn a working site into a puzzle: flex gaps, date inputs, 100vh — the classics. We verify the fixed pages in current Chrome, Firefox and Safari, desktop and mobile, and keep fixes modern where the audience allows and graceful where it does not. Along the way we clear what the fix touches: validation errors, deprecated tags, inline styles that sabotage the cascade. The rule is simple — the code after the fix is cleaner than before it, so each engagement reduces debt instead of stacking it.
Cost and timelines
A mini-package (up to 5 tasks) — from 10 000 RUB, 1–2 days. Standard (up to 15 tasks) — from 25 000 RUB, 3–4 days. Full responsive repair of a site (grid system plus all pages up to 30) — from 60 000 RUB, 1–2 weeks. A markup audit with a screenshot report — from 6 000 RUB, credited toward fixes. Rush work ("the expo is tomorrow") — a 30% surcharge, we start the day you write. Fixes for our own mistakes within 2 weeks — free.
Why ZXY markup developers
We fix markup on sites we built and on foreign ones — Bitrix, WordPress, pure HTML, constructors — and we localize causes instead of taping symptoms. Checks run on real devices, not just a resized browser window. Every task ships with before/after screenshots and a note on what was touched, so your developers stay in control. And we are fast where it matters: rush tasks start the same day, because a broken checkout the night before an expo is not a ticket — it is an emergency.
