stwcorp.com website review

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

34 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Google Maps and others), adding 1.9 MB and 1.3 s of main-thread time.

6 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

YouTube costs a phone 682 ms of main-thread work and 1.0 MB 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 358 ms of main-thread work and 419 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.

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

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

About 126 KiB of CSS is downloaded but never applied on this page.

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

4 KiB could be saved by minifying CSS.

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 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Trusted People and Results, Driven from the Ground Up”. Most of its time is element render delay (2.7 s).

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 85 requests on a phone: images 2.2 MB (22), scripts 1.7 MB (25) and fonts 133 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 12 <h1> headlines (“Trusted People and Results, Driven from the Groun…”, “HeavyHighway” and “Commercial & Residential Site Work”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 60 pages on stwcorp.com and 6 external pages.

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.stwcorp.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.stwcorp.com/heavy-highway, https://www.stwcorp.com/commercial-and-residential, https://www.stwcorp.com/engineering-and-design-build, https://www.stwcorp.com/ready-mix-concrete, https://www.stwcorp.com/hot-mix-asphalt and https://www.stwcorp.com/ez-street-ambient-asphalt and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.stwcorp.com/projects took over 3 s to send its HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.stwcorp.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http…”.

Chrome logged issues while loading the page (“Mixed content”).

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: 3 testimonial or review blocks. 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.

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

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

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