alliedalloys.com website review

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

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

5 third-party services load with your homepage (Wix, digitaloceanspaces.com and Sentry and others), adding 2.2 MB and 1.1 s of main-thread time.

Wix costs a phone 901 ms of main-thread work and 1.9 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.

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

7 images could be 565 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

31 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

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.

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Yard Drone Shot 3.png”.

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

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

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

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 3.3 MB in 217 requests on a phone: scripts 1.2 MB (100), other files 1.0 MB (94) and images 861 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 8f9cd4_a0e7c7d5f334453194be0c81770f2ae5~mv2.jpg at 960 px wide, shown at 287 px. Resized copies would save about 29 KiB.

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

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

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.

Your title is only 20 characters: “Home | Allied Alloys”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (LocalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 31 pages on alliedalloys.com and 1 external page.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/contact, /people, /process, /products, /heritage and /compliance and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/contact and /joinourteam have no <h1> headline, so visitors and search engines get no clear main topic.

/process and /joinourteam 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 8 pages linked from your homepage and read each the way a search engine does.

6 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

alliedalloys.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

alliedalloys.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 125 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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.

alliedalloys.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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