lowdesk.com website review

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

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (reamaze.com, Amazon Web Services and Klaviyo and others), adding 923 KiB and 874 ms of main-thread time.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

About 350 KiB of JavaScript is downloaded but never used on this page.

reamaze.com costs a phone 284 ms of main-thread work and 215 KiB 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.

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

The page has 2,740 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 115 ms of main-thread work and 420 KiB 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.

About 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

7 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need.

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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Alt text for video image 1”.

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

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

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

Your homepage downloads 3.0 MB in 305 requests on a phone: other files 1.0 MB (168), scripts 982 KiB (83) and images 494 KiB (33). Under 2 MB keeps phones on slow connections fast.

1 image (31 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 0.84 g of CO₂e: 100.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your meta description is only 54 characters: “Unique and Innovative Office Furniture and Accessories”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“Lowdesk”, “Move more while you work.” and “Try risk-free for 30 days”). One clear main headline is easier for people and search engines.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 88 pages on lowdesk.com and 19 external pages.

https://lowdesk.com/collections/pre-order-lowdesk-1-pro, https://lowdesk.com/collections/pre-orders-for-4-08-25-shipment, https://lowdesk.com/collections/coming-soon, https://lowdesk.com/collections/pre-order-lowdesk-open, https://lowdesk.com/collections/accessories and https://lowdesk.com/pages/why-lowdesk and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,182 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 22 cookies (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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.