Website review, no card needed
ruffgreens.com website review
Visit site (opens in a new tab)Reviewed 4 November 202624 issues · 63 checks
This review found 24 issues worth fixing on ruffgreens.com, 7 of them high impact, across 63 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 197 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 201 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 204 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 208 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 229 ms |
| Oct 10, 2026 | 226 ms |
| Oct 17, 2026 | 221 ms |
| Oct 24, 2026 | 213 ms |
| Oct 31, 2026 | 213 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 213 ms
213 msReal visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 197 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 690 ms
690 msReal visitors wait 690 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.7 MB
3.7 MBYour homepage downloads 3.7 MB on a phone, 702 KiB of it images (18%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Ruff-Greens-VitaSmart-Front.jpg 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).
3 images far larger than shown
327 KiB3 images are downloaded at several times the size a phone draws them, for example ruff-greens-box.jpg at 1,756 px wide, shown at 350 px. Resized copies would save about 327 KiB.
4 images below the first screen load straight away
4 images further down the page (590 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (10 elements)
Elements must only use permitted ARIA attributes: 10 elements on the page fail this check, rated serious by axe-core.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
76 internal links, 3 external
The homepage links to 76 pages on ruffgreens.com and 3 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Support your pet's digestion, skin, and coat with Ruff Greens VitaSmart, a daily food supplement with probiotics, vitam…”.
Title: 53 characters
Your title is a healthy 53 characters: “Healthy Daily Dog & Cat Food Supplement | Ruff Greens”.
Canonical URL set
The canonical URL is https://ruffgreens.com/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, ImageObject, Organization and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://ruffgreens.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,429 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ruffgreens.com/llms.txt (3 KiB, 22 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://ruffgreens.com/products/ruff-h2o-k9-hydration and https://ruffgreens.com/pages/who-we-are have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://ruffgreens.com/products/meow-greens-risk-free-jumpstart-vita-smart and https://ruffgreens.com/pages/who-we-are have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://ruffgreens.com/products/meow-greens-vitasmart, https://ruffgreens.com/products/ruff-tidbits-7-75-oz and https://ruffgreens.com/pages/who-we-are took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 1,412 words of copy
The homepage carries about 1,412 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “START YOUR JUMPSTART TRIAL”.
16 calls to action
The homepage has 16 calls to action, for example “JumpStart Trial | Start Here”, “Learn More” and “Call Us: 214.783.3364”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and PostHog.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
50 cookies set on arrival
50Opening the homepage sets 50 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.
67 other companies contacted
Loading the homepage contacts 67 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 ruffgreens.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Hulk Form Builder · Abconvert · Triplewhale · Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Yoast Seo · Applovin Shop Integration · nfcube.com · gorgias.chat · amazonaws.com · retention.com · shareasale.com · rebuyengine.com · goaffpro.com · 9gtb.com · skynettechnologies.com · moshi.ai
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | PostHog | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Carrollton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on ruffgreens.com, including 5 speed issues and 1 SEO issue. 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.