weoneil.com website review

6 images could be 1,013 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

About 207 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cloudflare.com and userway.org and others), adding 604 KiB and 288 ms of main-thread time.

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.131 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 111 ms to 104 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 2.5 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.7 MB in 122 requests on a phone: media 8.5 MB (1), images 2.4 MB (54) and other files 1.3 MB (27). Under 2 MB keeps phones on slow connections fast.

pic-1-1-new3-512x404.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).

5 images (924 KiB) are 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.

1 image is downloaded at several times the size a phone draws it, for example Super-nav_opt-1-2-scaled.jpg at 1,828 px wide, shown at 330 px. Resized copies would save about 300 KiB.

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

5 elements hidden from screen readers can still receive keyboard focus.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 261 pages on weoneil.com and 9 external pages.

https://www.weoneil.com/diversity-equity-inclusion-belonging, https://www.weoneil.com/contact, https://www.weoneil.com/company, https://www.weoneil.com/company/leadership, https://www.weoneil.com/company/employee-owned and https://www.weoneil.com/company/sustainable-building and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.weoneil.com/history, https://www.weoneil.com/company/news-insights and https://www.weoneil.com/projects have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.weoneil.com/company/employee-owned, https://www.weoneil.com/company/clients-partners and https://www.weoneil.com/company/sustainable-building took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://pixel.visitiq.io/dot/5f6f929c-7d80-4dd3-b1c0-f3ebbef8e385?cbust=2842930364676859.5&url_path=https%3A%2F%2Fwww.weoneil.com%2F.

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

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 longest form asks for 20 fields (3 required). Every extra field lowers completion.

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

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