Website review, no card needed
tuffgrowth.com website review
Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 78 checks
This review found 33 issues worth fixing on tuffgrowth.com, 11 of them high impact, across 78 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
4.3 s · 789 KiB1 image could be 789 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.
Render-blocking requests
4.0 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Reduce unused JavaScript
1.5 s · 307 KiBAbout 307 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Convert Insights and Adobe TypeKit and others), adding 1.1 MB and 251 ms of main-thread time.
Google Tag Manager adds 250 ms
250 msGoogle Tag Manager costs a phone 250 ms of main-thread work and 509 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.
1,510 HTML elements
The page has 1,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
WP Engine adds 0 ms
0 msWP Engine costs a phone 0 ms of main-thread work and 476 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 508 ms of it running JavaScript. That is comfortably low.
Server response: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’ve been around the block. And, the most important lesson…”.
Time to Interactive: 15.8 s
15.8 sThe page becomes fully interactive after 15.8 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
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.
2 checks passed
Cumulative Layout Shift: 0.084
0.084The layout barely moves while loading (CLS 0.084, good is under 0.1).
Total Blocking Time: 152 ms
152 msScripts block the page for only 152 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
tuff-2p0-2023-home-hero-670x705.png weighs 638 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.4 MB in 79 requests
3.4 MBYour homepage downloads 3.4 MB in 79 requests on a phone: images 2.2 MB (16), scripts 779 KiB (41) and fonts 217 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (638 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.
About 1.0 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 114.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
39 images without alt text
39 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (129 elements)
All page content should be contained by landmarks: 129 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
ARIA role should be appropriate for the element (38 elements)
ARIA role should be appropriate for the element: 38 elements on the page fail this check, rated minor by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Find traction and growth with an expert-led, on-d…” and “A proven growth methodology + whip-smart executors”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
79 internal links, 8 external
The homepage links to 79 pages on tuffgrowth.com and 8 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Tuff is a plug-in growth marketing team. We team up with startups & established players alike to accelerate growth with…”.
Title: 61 characters
Your title is a healthy 61 characters: “Your Growth Marketing Agency | Attract More Engaged Customers”.
Canonical URL set
The canonical URL is https://tuffgrowth.com/home/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://tuffgrowth.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,432 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://tuffgrowth.com/llms.txt (2 KiB, 13 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://tuffgrowth.com/creative, which answers with an error. Visitors hit a dead end and search engines drop it.
11 pages share 2 titles
https://tuffgrowth.com/services, https://tuffgrowth.com/video-marketing, https://tuffgrowth.com/seo, https://tuffgrowth.com/generative-engine-optimization, https://tuffgrowth.com/cro and https://tuffgrowth.com/growth-marketing-agency all use the title “Capabilities”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages share a meta description
https://tuffgrowth.com/services, https://tuffgrowth.com/video-marketing, https://tuffgrowth.com/seo, https://tuffgrowth.com/generative-engine-optimization, https://tuffgrowth.com/cro and https://tuffgrowth.com/growth-marketing-agency use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,236 words of copy
The homepage carries about 1,236 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a strategy call”.
7 calls to action
The homepage has 7 calls to action, for example “Book a Strategy Call”, “Book an intro call” and “Book a strategy call”.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks and 36 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
No consent tool detected
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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tuffgrowth.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Hiring
- Hiring
- 3 open roles
- Teams
- Engineering (1), Media Activation (1)
- Job board
- greenhouse
- Careers page
- goodwaygroup.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on tuffgrowth.com, including 13 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.