rolledalloys.com website review

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

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

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

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

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

LiveChat costs a phone 66 ms of main-thread work and 363 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.

8 third-party services load with your homepage (Google Tag Manager, Clarity and LiveChat and others), adding 799 KiB and 345 ms of main-thread time.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE LEADER IN SPECIALTY METALS Heat & Corrosion Resistant A…”.

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

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

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

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

ARIA role should be appropriate for the element: 4 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.

Elements with visible text labels do not have matching accessible names. (4 elements).

There are 2 <h1> headlines (“The Leaderin Specialty Metals” and “The Leaderin Specialty Metals”). One clear main headline is easier for people and search engines.

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

The homepage links to 223 pages on rolledalloys.com and 12 external pages.

https://www.rolledalloys.com/locations, https://www.rolledalloys.com/contact, https://www.rolledalloys.com/products, https://www.rolledalloys.com/products/nickel, https://www.rolledalloys.com/products/nickel/ra330 and https://www.rolledalloys.com/products/nickel/ra333 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rolledalloys.com/products/nickel, https://www.rolledalloys.com/products/nickel/alloy-601 and https://www.rolledalloys.com/products/nickel/alloy-625 took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'controller')”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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