woodmark.com website review

The page goes through 3 redirects before it starts loading, costing about 1.9 s. Link and advertise the final URL directly.

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

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

8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and ContentSquare and others), adding 1.1 MB and 988 ms of main-thread time.

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

About 539 KiB of JavaScript is downloaded but never used on this page.

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

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

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

The HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Adobe Tag Manager costs a phone 276 ms of main-thread work and 127 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.

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

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

Polyfills for old browsers add 21 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.

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

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “On 05/28/26, American Woodmark Corporation finalized its al…”.

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

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

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

4 buttons have no accessible name, so screen readers announce just “button”.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links do not have a discernible name (1 element).

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 17 characters: “American Woodmark”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

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

There is no robots.txt at woodmark.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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://woodmark.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.

No viewport meta tag, so phones render the desktop layout zoomed out.

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No character set is declared, so some characters can render as gibberish.

2 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 0 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.