lw.co website review

About 841 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

52 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.

About 216 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

13 images could be 870 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

16 files are served with short cache lifetimes, so returning visitors download them again (104 KiB).

7 third-party services load with your homepage (Vimeo, Google Tag Manager and WordPress Site Stats and others), adding 1.3 MB and 328 ms of main-thread time.

A phone's processor spends 3.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Vimeo costs a phone 182 ms of main-thread work and 1.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

26 KiB could be saved by minifying CSS.

13 long tasks block the main thread while loading, the longest for 172 ms. During a long task the page ignores taps.

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

9 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

The page becomes fully interactive after 26.4 s. Good is under 3.8 s.

Visually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 5.1 s on a phone. Good is under 1.8 s.

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

Scripts block taps and scrolling for 379 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 151 requests on a phone: images 2.8 MB (34), scripts 1.5 MB (54) and stylesheets 365 KiB (46). Under 2 MB keeps phones on slow connections fast.

LWDesignGroupNoepe070318_NateleeCocks_0108-1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (308 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (236 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 174.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 buttons have no accessible name, so screen readers announce just “button”.

4 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No XML sitemap at https://lw.co/sitemap_index.x, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 28 pages on lw.co and 6 external pages.

There is no https://lw.co/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://lw.co/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://lw.co/home all use the title “LW Design Group - Architecture & Interior Design Services”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lw.co/our-clients, https://lw.co/awards, https://lw.co/media and https://lw.co/careers have no meta description, so Google writes the search snippet from whatever text it finds.

https://lw.co/about-us, https://lw.co/brands, https://lw.co/our-clients, https://lw.co/awards, https://lw.co/interior-design and https://lw.co/architecture and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://lw.co/magazines has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://lw.co/interior-design took over 3 s to send its HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “no element is specified to initialize PerfectScrollbar”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,040 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 6 cookies, 2 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.