Responsive design bet at Marble.com (ahead of the mobile shift)

Work at All Granite & Marble Corp (Marble.com). Numbers are approximate. Internal details omitted out of respect for the company.

TL;DR

In 2013 I noticed mobile traffic on Marble.com was already 20–30% — and growing. The site was desktop-only. I pushed for a responsive redesign before mobile became the majority, using Bootstrap and LESS CSS when both were just becoming standards. By the time mobile overtook desktop across the industry, the site was ready.

Context

• Marble.com is the largest countertop fabricator on the East Coast, operating since 1996
• The site served thousands of customers daily — materials catalog, portfolio galleries, an online estimate tool, and 1,200+ stone colors
• In 2013, the site was a fixed-width, desktop-first build — no responsive breakpoints, no mobile considerations
• Analytics showed 20–30% of sessions already coming from mobile devices, and the trend was accelerating

What I observed

I was watching the analytics closely. The mobile share wasn’t a footnote — it was a clear, growing signal. Users on phones and tablets were hitting the same desktop layout that assumed a wide screen. Navigation was hard, images didn’t scale, and the estimate tool was unusable on small screens.

At that point, most sites in the industry (countertops, home services) hadn’t moved to responsive design either. There was no internal pressure to change — desktop was still the majority. The argument for waiting was easy to make.

Decision

I made the case to start adapting the site for mobile proactively — not as a reaction, but as preparation. The technical approach:

• Bootstrap as the responsive grid framework (it was becoming the industry standard but wasn’t yet universal)
• LESS CSS for maintainable, modular stylesheets (variables, mixins, nesting — before preprocessors were mainstream)
• Progressive adaptation: started with the most-visited pages and worked outward, so the transition was gradual and testable
• Media queries and flexible images to handle the range of screen sizes visitors were already using

This wasn’t a “redesign everything at once” project. It was a deliberate, page-by-page migration that kept the site stable for desktop users while making it usable for the growing mobile audience.

What I avoided

When mobile eventually became the majority of web traffic across the industry, many companies had to scramble — late migrations under pressure, broken layouts, rushed projects. Marble.com didn’t have that problem. The work was already done.

Google’s mobile-first indexing changes (which penalized non-responsive sites in search rankings) also landed without incident. The site was compliant well before it mattered for SEO.

What happened

• The site was responsive and functional on mobile before mobile became the dominant traffic source
• No late-stage migration panic, no rushed project, no SEO penalty
• The responsive foundation supported everything that came after — the estimate tool redesign, the materials catalog, the portfolio galleries, and the expansion into new product lines
• The approach I used (progressive adaptation, not full redesign) became the pattern for future technical migrations at the company, including the Flash-to-Angular estimate tool transition

What I took from it

Data tells you what’s coming if you look at it honestly. The mobile trend wasn’t a surprise — it was visible in the analytics months before it became urgent. The hard part wasn’t the technical work. The hard part was making the case to invest in something that wasn’t broken yet.

Early bets cost less. A responsive migration done gradually, on your own timeline, is dramatically cheaper and less risky than one done under pressure when traffic has already shifted and rankings are dropping. Some technical decisions are about removing future migration debt — and those are worth making even when the payoff isn’t immediate.