Website review, no card needed
bwtrailerhitches.com website review
Visit site (opens in a new tab)Reviewed 8 November 202639 issues · 78 checks
This review found 39 issues worth fixing on bwtrailerhitches.com, 13 of them high impact, across 78 checks. The most urgent: mobile performance score: 43. 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
76C- #75,296 of 124,051 reviewed websitesbeats 35%
- #48,232 of 69,757 online storesbeats 26%
- #45,685 of 63,448 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 166 ms |
| Oct 31, 2026 | 170 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
4.3 s
8.6 s
12.9 s
17.2 s
21.5 s
25.8 s
30.1 s
34.4 s
Speed
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and secureprivacy.ai and others), adding 1.7 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
450 ms · 429 KiB34 files are served with short cache lifetimes, so returning visitors download them again (429 KiB).
Improve image delivery
300 ms · 479 KiB13 images could be 479 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
300 ms · 448 KiBAbout 448 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.
Google Tag Manager adds 658 ms
658 msGoogle Tag Manager costs a phone 658 ms of main-thread work and 681 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.
Render-blocking requests
600 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Facebook adds 280 ms
280 msFacebook costs a phone 280 ms of main-thread work and 340 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 287 ms. During a long task the page ignores taps.
LiveChat adds 98 ms
98 msLiveChat costs a phone 98 ms of main-thread work and 364 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.
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A pickup truck towing a large white fifth wheel rv trailer …”.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
Total Blocking Time: 766 ms
766 msScripts block taps and scrolling for 766 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 100% slower for real visitors
+100%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
3 checks passed
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 443 requests
4.3 MBYour homepage downloads 4.3 MB in 443 requests on a phone: scripts 1.8 MB (88), other files 1.4 MB (287) and images 891 KiB (43). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
bwtrailerhitches-tongue-weight-scale-home-page-winter-2025-l 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).
1 image in older formats
1 image (450 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.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.6 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
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 31 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 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 (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
56 internal links, 14 external
The homepage links to 56 pages on bwtrailerhitches.com and 14 external pages.
6 checks passed
Title: 51 characters
Your title is a healthy 51 characters: “B&W Trailer Hitches | American Made Towing Products”.
Canonical URL set
The canonical URL is https://www.bwtrailerhitches.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.bwtrailerhitches.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 (473 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bwtrailerhitches.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a title
https://www.bwtrailerhitches.com/products/extend-a-goose-gooseneck-coupler, https://www.bwtrailerhitches.com/products/defender-locking-gooseneck-coupler, https://www.bwtrailerhitches.com/products/fifth-wheel-to-gooseneck-adapter, https://www.bwtrailerhitches.com/products/companion-fifth-wheel-hitch, https://www.bwtrailerhitches.com/products/companion-oem-fifth-wheel-hitch and https://www.bwtrailerhitches.com/products/rail-mounted-fifth-wheel-hitch and 3 others have no <title>, so Google invents the link text in results.
10 pages without a meta description
https://www.bwtrailerhitches.com/pages/turnoverball-accessories, https://www.bwtrailerhitches.com/products/extend-a-goose-gooseneck-coupler, https://www.bwtrailerhitches.com/products/defender-locking-gooseneck-coupler, https://www.bwtrailerhitches.com/products/fifth-wheel-to-gooseneck-adapter, https://www.bwtrailerhitches.com/products/companion-fifth-wheel-hitch and https://www.bwtrailerhitches.com/products/companion-oem-fifth-wheel-hitch and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.bwtrailerhitches.com/products/turnoverball-gooseneck-hitch, https://www.bwtrailerhitches.com/pages/turnoverball-accessories, https://www.bwtrailerhitches.com/products/oem-ball-safety-chain-kit, https://www.bwtrailerhitches.com/products/gooseneck-trailer-coupler-lock, https://www.bwtrailerhitches.com/products/extend-a-goose-gooseneck-coupler and https://www.bwtrailerhitches.com/products/defender-locking-gooseneck-coupler and 9 others have 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 40 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Best practices
6 small tap targets
6 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “gtag is not defined”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 10-field form
Your longest form asks for 10 fields (1 required). Every extra field lowers completion.
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 169 words
The homepage has only about 169 words of visible text; thin pages give Google and first-time buyers little to go on.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP TONGUE WEIGHT SCALE”.
6 calls to action
The homepage has 6 calls to action, for example “ShOP TONGUE WEIGHT SCALE”, “Shop Pin Lock” and “GET A COPY”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
44 other companies contacted
Loading the homepage contacts 44 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 bwtrailerhitches.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Drupal Commerce 1.x;Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Employees
- 542
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bwtrailerhitches.com, including 22 speed issues, 2 SEO issues and 4 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.