Article hero image 1600 × 900px (16:9) Photo or render representative of this article’s topic. Grayscale-until-hover treatment applied automatically once added.

A construction or BIM consultancy website's biggest marketing asset - high-resolution project photography and 3D model viewers - is also its most common technical liability, and Google's Core Web Vitals now measure that liability directly as a genuine ranking factor rather than a purely cosmetic performance concern.

AssetTypical impact on Largest Contentful Paint (LCP)Typical fix
Uncompressed 4MB JPEG hero imagePushes LCP past the 4-second "poor" threshold on typical connectionsConvert to WebP/AVIF, target under 200-300KB for hero images
Embedded BIM model viewer / 3D visualisationCan significantly delay page interactivity if loaded immediately on page loadLazy-load below the fold, or load on user interaction rather than automatically
Portfolio image carouselsCommon source of Cumulative Layout Shift (CLS) if dimensions aren't reserved in advanceSet explicit width/height or aspect-ratio CSS before images load
In-article image 1200 × 675px (16:9) Supporting diagram, photo, or screenshot placed mid-article to break up long text.

Why This Matters More for BIM/Construction Sites Specifically

Portfolio-heavy sites are structurally more exposed to Core Web Vitals problems than text-heavy sites, simply because the entire value proposition - visual proof of project quality - depends on heavy media by its nature. A slow-loading portfolio page doesn't just affect search ranking directly; it undermines the credibility pitch the page is actually trying to make, since a prospective client evaluating a firm's technical competence is put off by a technically poor browsing experience regardless of how good the underlying project work actually was.

A Scenario Showing Why Lazy-Loading Is the Right Fix, Not Removal

Picture a firm considering removing an embedded BIM model viewer from its site entirely, believing that's the only way to avoid its Core Web Vitals penalty. The genuine fix is lazy-loading the viewer specifically - so it only loads when a visitor actually scrolls to it or clicks to activate it - rather than removing a genuinely valuable feature that showcases the firm's capability, avoiding the performance penalty while keeping the feature intact for visitors who actually want to engage with it.