Website review, no card needed
dbsupply.com website review
Visit site (opens in a new tab)Reviewed 31 October 202634 issues · 76 checks
This review found 34 issues worth fixing on dbsupply.com, 8 of them high impact, across 76 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 144 ms |
| May 16, 2026 | 143 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 167 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 183 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 188 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.5 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
620 ms · 806 KiBAbout 806 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.
Render-blocking requests
950 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Google Tag Manager adds 862 ms
862 msGoogle Tag Manager costs a phone 862 ms of main-thread work and 825 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.
Facebook adds 488 ms
488 msFacebook costs a phone 488 ms of main-thread work and 369 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
451 KiB10 files are served with short cache lifetimes, so returning visitors download them again (451 KiB).
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
Reduce unused CSS
260 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.
Improve image delivery
99 KiB4 images could be 99 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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 CLS: 0.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Time to Interactive: 18.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carhartt Days October 28-November 1”.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 144 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.144
0.144The layout shifts by 0.144 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 752 ms
752 msReal visitors wait 752 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.7 MB in 110 requests
2.7 MBYour homepage downloads 2.7 MB in 110 requests on a phone: scripts 2.1 MB (50), images 455 KiB (17) and fonts 81 KiB (3). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MainHeroBanner-Mobile320x446-CarharttDays26.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).
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
167 form fields without a label
167 form fields have no label, so screen readers announce an empty box and autofill guesses.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization) but with 2 problems, for example “Organization: url is not an absolute URL ("www.dbsupply.com")”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
28 internal links, 6 external
The homepage links to 28 pages on dbsupply.com and 6 external pages.
7 checks passed
Meta description: 71 characters
Your meta description is 71 characters: “Everything you need for a life in the west you can get it at D&B Supply”.
One H1 headline
Your main headline reads: “D&B Supply”.
Title: 62 characters
Your title is a healthy 62 characters: “D&B Supply | Farm, Ranch, Home & Pet Supplies | Idaho & Oregon”.
Canonical URL set
The canonical URL is https://www.dbsupply.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.dbsupply.com/appsitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.dbsupply.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.
Other pages
1 page without a title
https://www.dbsupply.com/service-pellet-stoves has no <title>, so Google invents the link text in results.
3 pages without a meta description
https://www.dbsupply.com/sezzle_about, https://www.dbsupply.com/carhartt and https://www.dbsupply.com/service-pellet-stoves have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.dbsupply.com/sezzle_about, https://www.dbsupply.com/carhartt and https://www.dbsupply.com/hills_sd have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://www.dbsupply.com/rv-antifreeze-1gl-164150.html, https://www.dbsupply.com/brands/noble-outfitters.html, https://www.dbsupply.com/shop/stoves-fireplaces/stoves-inserts.html, https://www.dbsupply.com/sezzle_about, https://www.dbsupply.com/carhartt and https://www.dbsupply.com/brands/stihl.html and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 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 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Geolocation error: [object GeolocationPositionError]”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 85 words
The homepage has only about 85 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.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Request Service”.
Analytics in place
Analytics detected: Google Tag Manager.
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 The Trade Desk (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
17 other companies contacted
Loading the homepage contacts 17 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 dbsupply.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Fastly
Company
- Employees
- 651
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 dbsupply.com, including 17 speed issues, 1 SEO issue 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.