greenknight.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and apex.live and others), adding 1.5 MB and 1.1 s of main-thread time.

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

Google Tag Manager costs a phone 691 ms of main-thread work and 854 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 150 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Facebook costs a phone 202 ms of main-thread work and 294 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.

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

22 KiB could be saved by minifying JavaScript.

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

7 KiB JavaScript is shipped twice across bundles.

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “High-Quality Metal Roofing Solutions in Central Texas Armor…”.

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

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

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

The first text or image appears after 2.8 s on a phone. Good is under 1.8 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 17.0 MB in 164 requests on a phone: media 13.7 MB (2), scripts 1.9 MB (62) and images 993 KiB (32). Under 2 MB keeps phones on slow connections fast.

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

1 link inside paragraphs relies on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 68 characters, so Google will cut it off around 60: “Austin's Durable Metal Roofing Options | Green Knight® Metal Roofing”.

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

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

The homepage links to 109 pages on greenknight.com and 9 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://greenknight.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://greenknight.com/media-room has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 969 words of visible text.

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