Website review, no card needed
rufflydog.com website review
Visit site (opens in a new tab)Reviewed 16 November 202634 issues · 58 checks
This review found 34 issues worth fixing on rufflydog.com, 9 of them high impact, across 58 checks. The most urgent: page weight: 20.8 MB in 345 requests. 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
68D- #103,446 of 117,615 reviewed websitesbeats 10%
- #62,424 of 66,923 online storesbeats 5%
- #57,571 of 61,018 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
100 ms · 7.1 MB37 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused JavaScript
860 ms · 322 KiBAbout 322 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 860 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, omnisnippet1.com and squarecdn.com and others), adding 1.4 MB and 747 ms of main-thread time.
Shopify adds 394 ms
394 msShopify costs a phone 394 ms of main-thread work and 804 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.
Use efficient cache lifetimes
50 ms · 329 KiB19 files are served with short cache lifetimes, so returning visitors download them again (329 KiB).
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 292 ms. During a long task the page ignores taps.
2,335 HTML elements
The page has 2,335 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Duplicated JavaScript
200 ms · 49 KiB49 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 51.5 s
51.5 sYour largest element takes 51.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 61.7 s
61.7 sThe page becomes fully interactive after 61.7 s. Good is under 3.8 s.
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 398 ms
398 msScripts block taps and scrolling for 398 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 20.8 MB in 345 requests
20.8 MBYour homepage downloads 20.8 MB in 345 requests on a phone: images 18.2 MB (66), scripts 1.2 MB (124) and other files 789 KiB (93). Under 2 MB keeps phones on slow connections fast.
About 5.9 g of CO₂ per visit
5.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.89 g of CO₂e: 706.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. 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.
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Waterproof collars, leads and harnesses Handmade in Australia – Ruffly Dog”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
5 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Durable dog gear, unique designs, all handcrafted for dogs that love to stand out. Waterproof dog collars, harnesses, l…”.
Canonical URL set
The canonical URL is https://www.rufflydog.com/.
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://www.rufflydog.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.rufflydog.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.
1 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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 rufflydog.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Terms Checkbox · Keepcart Coupon Protect · Ymq Product Options · Judge Me Reviews · Zepto Product Personalizer · Ta Labels Badges · Terms And Conditions In Cart · Announcement Bar Maker By Apphero · Easy Content Builder · cloudfront.net · nfcube.com · goaffpro.com · omnisnippet1.com
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on rufflydog.com, including 16 speed issues, 5 SEO issues and 6 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.