thegrowthsmiths.com website review

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

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

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

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

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.0 MB and 319 ms of main-thread time.

YouTube costs a phone 312 ms of main-thread work and 991 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 111 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “images/growthsmiths-hero.png”.

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

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

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

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.

growthsmiths-hero.png weighs 544 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.4 MB in 46 requests on a phone: images 1.3 MB (8), scripts 919 KiB (11) and HTML 93 KiB (2). Under 2 MB keeps phones on slow connections fast.

growthsmiths-hero.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 image is downloaded at several times the size a phone draws it, for example service-marketing-strategy.png at 1,143 px wide, shown at 310 px. Resized copies would save about 25 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 82.1 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”.

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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 12 characters: “Growthsmiths”. 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 XML sitemap at https://thegrowthsmiths.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 22 pages on thegrowthsmiths.com and 3 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://thegrowthsmiths.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.

Your homepage links to https://thegrowthsmiths.com/apps/contact-form-plus, which answers with an error. Visitors hit a dead end and search engines drop it.

https://thegrowthsmiths.com/pages/businesses.html, https://thegrowthsmiths.com/pages/leads-generation.html, https://thegrowthsmiths.com/pages/lead-generation.html, https://thegrowthsmiths.com/pages/terms-of-service.html, https://thegrowthsmiths.com/pages/privacy-policy.html and https://thegrowthsmiths.com/pages/refund-policy.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://thegrowthsmiths.com/pages/about-us.html, https://thegrowthsmiths.com/pages/businesses.html, https://thegrowthsmiths.com/pages/success-stories.html, https://thegrowthsmiths.com/pages/leads-generation.html, https://thegrowthsmiths.com/pages/lead-generation.html and https://thegrowthsmiths.com/pages/refund-policy.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://thegrowthsmiths.com/pages/businesses.html, https://thegrowthsmiths.com/pages/success-stories.html, https://thegrowthsmiths.com/pages/leads-generation.html and https://thegrowthsmiths.com/pages/refund-policy.html 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 9 pages linked from your homepage and read each the way a search engine does.

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

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

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 232 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.

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