Website review, no card needed
tarterusa.com website review
Visit site (opens in a new tab)Reviewed 30 October 202626 issues · 97 checks
This review found 26 issues worth fixing on tarterusa.com, 8 of them high impact, across 97 checks. The most urgent: fails Core Web Vitals for real visitors. 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
89B- #2,464 of 80,566 reviewed websitesbeats 95%
- #1,130 of 39,626 online storesbeats 95%
- #26 of 2,103 WooCommerce storesbeats 98%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 998 ms |
| May 23, 2026 | 957 ms |
| May 30, 2026 | 973 ms |
| Jun 6, 2026 | 939 ms |
| Jun 13, 2026 | 943 ms |
| Jun 20, 2026 | 974 ms |
| Jun 27, 2026 | 956 ms |
| Jul 4, 2026 | 943 ms |
| Jul 11, 2026 | 912 ms |
| Jul 18, 2026 | 900 ms |
| Jul 25, 2026 | 939 ms |
| Aug 1, 2026 | 975 ms |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 993 ms |
| Aug 22, 2026 | 958 ms |
| Aug 29, 2026 | 954 ms |
| Sep 5, 2026 | 939 ms |
| Sep 12, 2026 | 930 ms |
| Sep 19, 2026 | 910 ms |
| Sep 26, 2026 | 863 ms |
| Oct 3, 2026 | 823 ms |
| Oct 10, 2026 | 821 ms |
| Oct 17, 2026 | 862 ms |
| Oct 24, 2026 | 855 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 71 ms |
| May 16, 2026 | 71 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 75 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 71 ms |
| Aug 22, 2026 | 71 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 72 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 71 ms |
| Oct 17, 2026 | 71 ms |
| Oct 24, 2026 | 71 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
Improve image delivery
803 KiB6 images could be 803 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, YouTube and Google Analytics), adding 197 KiB and 124 ms of main-thread time.
Reduce unused JavaScript
99 KiBAbout 99 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.
Reduce unused CSS
47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page.
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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 348 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user TTFB: 945 ms
945 msReal visitors wait 945 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.185
0.185The layout shifts by 0.185 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 3.8 s
3.8 sThe page becomes fully interactive after 3.8 s. Good is under 3.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 71 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 73 ms
73 msReal visitors wait 73 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Tarter horse stall”.
Speed Index: 1.8 s
1.8 sVisually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
4 images far larger than shown
644 KiB4 images are downloaded at several times the size a phone draws them, for example Hero-2-Built-Proud-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 644 KiB.
1 image below the first screen load straight away
1 image further down the page (73 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 65.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 59 requests
1.9 MBYour homepage downloads 1.9 MB in 59 requests on a phone: images 1.2 MB (13), scripts 375 KiB (29) and fonts 238 KiB (9). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores 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.
Meta description is long (241 characters)
Your meta description is 241 characters; Google truncates after about 160, so the end of your pitch is cut.
159 internal links, 9 external
The homepage links to 159 pages on tarterusa.com and 9 external pages.
6 checks passed
Title: 48 characters
Your title is a healthy 48 characters: “Farm & Ranch Equipment Manufacturer | Tarter USA”.
Canonical URL set
The canonical URL is https://tarterusa.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person 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://tarterusa.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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (351 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (41 KiB, 189 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
/categories/categories declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and /categories/categories all use the title “Farm & Ranch Equipment Manufacturer | Tarter USA”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
/categories/categories/cattle/feeders-cattle/large-square-bale and /categories/categories/cattle/feeders-cattle/hay-grain have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
/categories/categories has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 133 found) and read each the way a search engine does.
3 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
http:// does not redirect
http://tarterusa.com does not redirect to https, so some visitors land on the insecure version.
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
1 link through redirect chains
1 link go through two or more redirects, for example https://tarterusa.com/categories/categories/.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
4 checks passed
Served over HTTPS
The homepage is served over HTTPS (tarterusa.com).
Valid certificate (38 days left)
The certificate from Let's Encrypt · YE1 verifies for tarterusa.com and is valid for another 38 days.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 47 links work
All 47 links checked from your homepage (40 internal, 7 external) answered without errors.
Domain and trust
No CAA record
tarterusa.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
tarterusa.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 13 years old
13 yearstarterusa.com was registered in Feb 2013 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.
Registered until Feb 2028
tarterusa.com is registered until Feb 2028.
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.
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.
Only about 173 words
The homepage has only about 173 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP PARTS”.
5 calls to action
The homepage has 5 calls to action, for example “Shop Parts”, “CONTACT US” and “SHOP LOCAL TO YOU”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
Email authentication score: 90/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:207.106.84.66 ip4:207.106.84.74 ip4:38.48.86.170 ip4:207.106.84.83 ip4:20.22.152.119 include:spf.protection.…”.
DKIM signing found
A DKIM key is published (selector “selector1”, “selector2” and “s1”), so receivers can verify mail really came from you.
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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
- The footer still says © 2025.
- It runs WordPress 7.1.3; the current release is 7.1.4.
Stack
- CMS
- WordPress 7.1.3
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- WP Engine
Company
- Employees
- 779
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on tarterusa.com, including 6 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.