withbureau.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Facebook and others), adding 1.8 MB and 1.2 s of main-thread time.

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

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

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

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

hsappstatic.net costs a phone 289 ms of main-thread work and 810 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.

Google Tag Manager costs a phone 307 ms of main-thread work and 342 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.

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.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bureau designs soundproof office booths for focus, privacy,…”.

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

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

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

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

Real visitors wait 3.5 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.

12 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 5.5 MB in 214 requests on a phone: scripts 3.3 MB (95), media 967 KiB (3) and images 462 KiB (44). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example One_Meet-1.webp at 1,000 px wide, shown at 326 px. Resized copies would save about 105 KiB.

1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The homepage links to 145 pages on withbureau.com and 2 external pages.

https://withbureau.com/us/shop, https://withbureau.com/us/tuesday-series, https://withbureau.com/us/signature-series and https://withbureau.com/us/compare-office-booths have no meta description, so Google writes the search snippet from whatever text it finds.

https://withbureau.com/us/compare-office-booths has no <h1> headline, so visitors and search engines get no clear main topic.

https://withbureau.com/us/products/quad-plus, https://withbureau.com/us/products/focus-accessible and https://withbureau.com/us/focus-pods took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343147426&tm=gtm002&Ver=2&mid=7c10cae4-e87d-4886-b985-144f70d12ebb&bo=4&sid=1fe31460d98811f19ec1d5e51f806d46&vid=1fe33e70d98811f1a59eed991be02ab1&vids=1&msclkid=N&pi=9.

2 of 8 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.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 795 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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