valleyiron.com website review

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

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

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

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

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

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

24 KiB could be saved by minifying CSS.

7 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google CDN and others), adding 438 KiB and 267 ms of main-thread time.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 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.

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

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

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

Your largest element takes 50.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We maintain one of the most comprehensive and diverse inven…”.

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

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

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

3 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' largest content (lcp) went from 7.0 s to 6.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.5 MB in 35 requests on a phone: scripts 6.7 MB (10), images 2.5 MB (15) and stylesheets 110 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example ValleyIron_Selection_home.jpg at 1,512 px wide, shown at 390 px. Resized copies would save about 735 KiB.

10 images (2.5 MB) 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.

5 images further down the page (554 KiB) 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 2.68 g of CO₂e: 321.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

3 tap targets are too small or too close together to hit reliably with a finger.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 71 characters, so Google will cut it off around 60: “Valley Iron, Inc. Metal products since 1958 Fresno - Vacaville Oroville”.

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

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

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 65 pages on valleyiron.com and 4 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://valleyiron.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://valleyiron.com/credit-application, https://valleyiron.com/prepay-account-form and https://valleyiron.com/preliminary-notice-worksheet have no meta description, so Google writes the search snippet from whatever text it finds.

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

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 404 (Not Found)”.

Large scripts ship without source maps.

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 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

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