thegranitegroup.com website review

25 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.

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

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

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

5 third-party services load with your homepage (Google Maps, Google CDN and Amazon Web Services and others), adding 6.5 MB and 212 ms of main-thread time.

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

Amazon Web Services costs a phone 50 ms of main-thread work and 5.6 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.

Google Maps costs a phone 99 ms of main-thread work and 398 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.

Google CDN costs a phone 62 ms of main-thread work and 348 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.

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

25 KiB could be saved by minifying JavaScript.

18 KiB JavaScript is shipped twice across bundles.

Desktop scores 83 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 19.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “"Understanding our customers’ needs and building strong, lo…”.

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

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

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

Your homepage downloads 6.9 MB in 38 requests on a phone: images 4.6 MB (14), scripts 1.6 MB (11) and HTML 401 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.9 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 360016_sink_spout_image.jpg at 1,440 px wide, shown at 350 px. Resized copies would save about 1.4 MB.

7 images (4.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.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 16 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.

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

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

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.

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

There are 3 <h1> headlines (“On Call Emergency Service”, “Commercial Water Heaters” and “Become a Customer”). One clear main headline is easier for people and search engines.

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

Structured data found (Article) but with 1 problem, for example “Article: missing datePublished”.

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://www.thegranitegroup.com/sitemap.xml, so Google discovers your pages only by following links.

2 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 531 pages on thegranitegroup.com and 6 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://www.thegranitegroup.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://www.thegranitegroup.com/s/content/become-a-customer and https://www.thegranitegroup.com/content/become-a-customer all use the title “Become a Customer”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.thegranitegroup.com/s/content/contact-us, https://www.thegranitegroup.com/s/content/about-us, https://www.thegranitegroup.com/s/content/become-a-customer, https://www.thegranitegroup.com/s/content/join-our-team, https://www.thegranitegroup.com/content/become-a-customer and https://www.thegranitegroup.com/spcu/account-retrieval and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thegranitegroup.com/s/content/contact-us, https://www.thegranitegroup.com/s/content/about-us, https://www.thegranitegroup.com/s/content/become-a-customer, https://www.thegranitegroup.com/s/content/join-our-team, https://www.thegranitegroup.com/content/become-a-customer and https://www.thegranitegroup.com/spcu/account-retrieval and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 errors were logged to the browser console while the page loaded, for example “Error getting current location [object GeolocationPositionError]”.

Requests the geolocation permission on page load.

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

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 235 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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