mcswainbuilders.com website review

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

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

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

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

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

Facebook costs a phone 254 ms of main-thread work and 282 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.

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

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

leadconnectorhq.com costs a phone 143 ms of main-thread work and 606 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.

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Remodeled kitchen and living room in an Old Snowmass home n…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.0 MB in 132 requests on a phone: scripts 1.6 MB (53), other files 1.4 MB (33) and images 395 KiB (27). Under 2 MB keeps phones on slow connections fast.

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

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

The homepage links to 50 pages on mcswainbuilders.com and 19 external pages.

There is no https://mcswainbuilders.com/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.

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

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

2 images are served at too low a resolution for sharp phone screens.

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

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

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