safway.com website review

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

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

8 third-party services load with your homepage (rlets.com, Google Tag Manager and Optanon and others), adding 1,004 KiB and 1.3 s of main-thread time.

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

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

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

rlets.com costs a phone 447 ms of main-thread work and 60 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 3.6 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

53 KiB could be saved by minifying JavaScript.

10 KiB could be saved by minifying CSS.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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.

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

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

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

12 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-17, real Chrome visitors' tap response (inp) went from 78 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.5 MB in 98 requests on a phone: images 3.4 MB (37), scripts 1,012 KiB (29) and stylesheets 62 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example brandsafway-sectional-scaffold_0_0.jpg at 1,920 px wide, shown at 360 px. Resized copies would save about 138 KiB.

2 images (236 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 further down the page (202 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.28 g of CO₂e: 153.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 94 characters, so Google will cut it off around 60: “BrandSafway Access & Specialty Services | Industrial, Commercial, and Infrastructure Solu…”.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

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

The homepage links to 111 pages on safway.com and 7 external pages.

There is no https://brandsafway.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://brandsafway.com/areas-of-expertise, https://brandsafway.com/who-we-are and https://brandsafway.com/products-and-services all use the title “BrandSafway Access & Specialty Services | Industrial, Commercial, and…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://brandsafway.com/literature, https://brandsafway.com/locations and https://brandsafway.com/rentals have no meta description, so Google writes the search snippet from whatever text it finds.

https://brandsafway.com/areas-of-expertise, https://brandsafway.com/who-we-are and https://brandsafway.com/products-and-services use the same meta description. A description written for each page earns more clicks.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Opening the homepage sets 19 cookies (measured from a US location before any click).

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