macarthurco.com website review

15 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

Your mobile performance score is 50 (desktop: 26). Pages that score under 90 lose visitors before the first paint.

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

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

About 42 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.

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.

1 third-party service load with your homepage (Google Fonts), adding 10 KiB and 0 ms of main-thread time.

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 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 32 requests on a phone: images 4.5 MB (24), fonts 354 KiB (4) and scripts 211 KiB (1). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example Building.jpg at 4,000 px wide, shown at 370 px. Resized copies would save about 2.6 MB.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), 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 structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No XML sitemap at https://www.macarthurco.com/sitemap.xml, so Google discovers your pages only by following links.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 16 pages on macarthurco.com and 11 external pages.

A phone browser shows 3,522 words, but the HTML your server sends has only 105. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.macarthurco.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.

https://www.macarthurco.com/locations/mac-el-paso-tx, https://www.macarthurco.com/locations/reno-nv, https://www.macarthurco.com/mechanical-insulation, https://www.macarthurco.com/hvac-fire-protection, https://www.macarthurco.com/commercial-roofing and https://www.macarthurco.com/residential-roofing and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.macarthurco.com/locations/mac-el-paso-tx, https://www.macarthurco.com/locations/reno-nv, https://www.macarthurco.com/mechanical-insulation, https://www.macarthurco.com/hvac-fire-protection, https://www.macarthurco.com/commercial-roofing and https://www.macarthurco.com/residential-roofing and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.macarthurco.com/locations/mac-el-paso-tx, https://www.macarthurco.com/locations/reno-nv, https://www.macarthurco.com/mechanical-insulation, https://www.macarthurco.com/hvac-fire-protection, https://www.macarthurco.com/commercial-roofing and https://www.macarthurco.com/residential-roofing and 4 others have 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.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 3,522 words of visible text.

Opening the homepage sets 2 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.