Website review, no card needed
tuckerandtodd.com website review
Visit site (opens in a new tab)Reviewed 13 November 202633 issues · 82 checks
This review found 33 issues worth fixing on tuckerandtodd.com, 8 of them high impact, across 82 checks. The most urgent: render-blocking 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
80B- #43,283 of 109,350 reviewed websitesbeats 55%
- #28,717 of 61,859 online storesbeats 47%
- #27,632 of 56,401 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 972 ms |
| Aug 15, 2026 | 986 ms |
| Aug 22, 2026 | 988 ms |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 90 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 87 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 90 ms |
| Aug 1, 2026 | 76 ms |
| Aug 8, 2026 | 81 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 81 ms |
| Sep 5, 2026 | 82 ms |
| Sep 12, 2026 | 83 ms |
| Sep 19, 2026 | 82 ms |
| Sep 26, 2026 | 82 ms |
| Oct 3, 2026 | 83 ms |
| Oct 10, 2026 | 81 ms |
| Oct 17, 2026 | 85 ms |
| Oct 24, 2026 | 84 ms |
| Oct 31, 2026 | 86 ms |
| Nov 7, 2026 | 86 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
How it loaded on a phone
0.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.1 s
5.8 s
Speed
Render-blocking requests
1.2 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Accessibe Accessibility Overlay and avada.io and others), adding 1.1 MB and 1.0 s of main-thread time.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 540 KiBAbout 540 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 640 ms
640 msShopify costs a phone 640 ms of main-thread work and 526 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,553 HTML elements
The page has 1,553 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 128 KiB128 KiB could be saved by minifying JavaScript.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Improve image delivery
164 KiB10 images could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
127 KiB8 files are served with short cache lifetimes, so returning visitors download them again (127 KiB).
Reduce unused CSS
71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.0 s
11.0 sThe page becomes fully interactive after 11.0 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FALL ESSENTIALS”. Most of its time is element render delay (2.4 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 90 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 88 ms
88 msReal visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 137 ms
137 msScripts block the page for only 137 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 236 requests
3.0 MBYour homepage downloads 3.0 MB in 236 requests on a phone: scripts 1.3 MB (61), other files 856 KiB (136) and images 697 KiB (22). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (314 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (33 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 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 103.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Tucker & Todd Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (37 characters)
Your meta description is only 37 characters: “Tucker & Todd Budzyn's Official Store”. 70 to 160 characters is enough to sell the click.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
74 internal links, 21 external
The homepage links to 74 pages on tuckerandtodd.com and 21 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Tucker & Todd Co.”.
Canonical URL set
The canonical URL is https://www.tuckerandtodd.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.tuckerandtodd.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.
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 (340 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.tuckerandtodd.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.tuckerandtodd.com/products/woven-fringe-blanket, which answers with an error. Visitors hit a dead end and search engines drop it.
11 pages without a meta description
https://www.tuckerandtodd.com/collections/doggo-products, https://www.tuckerandtodd.com/collections/collars, https://www.tuckerandtodd.com/collections/leashes, https://www.tuckerandtodd.com/collections/lick-mats, https://www.tuckerandtodd.com/collections/bandanas and https://www.tuckerandtodd.com/collections/grooming-collection and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.tuckerandtodd.com/collections/fall-essentials/products/tucker-todd-collar-mint, whose canonical is https://www.tuckerandtodd.com/products/tucker-todd-collar-mint. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
4 checks passed
Titles are unique
Every page we checked has its own title.
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 broken images
2 images failed to load on a phone, for example https://www.tuckerandtodd.com/.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://emailnoticeapi.sealapps.com/api/v1/collect/config' from origin 'https://www.tucker…”.
2 checks passed
Tap targets are thumb-sized
19 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 211 words
The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
10 calls to action
The homepage has 10 calls to action, for example “SHOP ALL”, “TRACK MY ORDER” and “Shop now”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) 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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 2 of them by other companies (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.
30 other companies contacted
Loading the homepage contacts 30 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 tuckerandtodd.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Timesact Pre Order · Klaviyo Email Marketing Sms · Wj Toolbox · Beast Currency Converter · Back In Stock · Avada Cookie Bar · Free Contact Form · Instagram Story App · cart-bot.net · hextom.com · useifsapp.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 33 issues on tuckerandtodd.com, including 12 speed issues, 4 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.