Website review, no card needed
warehousedirect.com website review
Visit site (opens in a new tab)Reviewed 30 October 202625 issues · 79 checks
This review found 25 issues worth fixing on warehousedirect.com, 2 of them high impact, across 79 checks. The most urgent: largest Contentful Paint: 6.6 s. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 938 ms |
| May 16, 2026 | 994 ms |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 999 ms |
| Aug 8, 2026 | 961 ms |
| Aug 15, 2026 | 902 ms |
| Aug 22, 2026 | 930 ms |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 934 ms |
| Oct 10, 2026 | 932 ms |
| Oct 17, 2026 | 880 ms |
| Oct 24, 2026 | 746 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 80 ms |
| May 16, 2026 | 83 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 85 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 91 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 93 ms |
| Aug 8, 2026 | 92 ms |
| Aug 15, 2026 | 92 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 101 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 76 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 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.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: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 196 KiB40 files are served with short cache lifetimes, so returning visitors download them again (196 KiB).
Render-blocking requests
600 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
hubspotusercontent-na1.net adds 5 ms
5 mshubspotusercontent-na1.net costs a phone 5 ms of main-thread work and 334 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.
5 third-party services on the page
5 third-party services load with your homepage (Hubspot, JSDelivr CDN and hubspotusercontent-na1.net and others), adding 528 KiB and 133 ms of main-thread time.
Improve image delivery
180 KiB7 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.
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
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 297 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Warehouse Direct”.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 80 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 81 ms
81 msReal visitors wait 81 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 361 ms
361 msReal visitors wait 361 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
3 images far larger than shown
73 KiB3 images are downloaded at several times the size a phone draws them, for example 1-1.png at 1,200 px wide, shown at 350 px. Resized copies would save about 73 KiB.
3 images below the first screen load straight away
3 images further down the page (310 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.26 g of CO₂e: 31.1 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: 935 KiB in 59 requests
935 KiBYour homepage downloads 935 KiB in 59 requests on a phone: images 534 KiB (21), scripts 180 KiB (17) and fonts 162 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 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 (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 20 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 1 more 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.
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
53 internal links, 24 external
The homepage links to 53 pages on warehousedirect.com and 24 external pages.
5 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Your One-Stop Workplace Solution | Warehouse Direct Top-notch supplies, IT, and more. 40+ years serving Chicago-land bu…”.
Canonical URL set
The canonical URL is https://warehousedirect.com/.
Structured data in place
Structured data found: BreadcrumbList, ItemList, LocalBusiness and Organization.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://warehousedirect.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://warehousedirect.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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (245 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://warehousedirect.com/contact-us, https://warehousedirect.com/careers, https://warehousedirect.com/returns-policy, https://warehousedirect.com/privacy-policy, https://warehousedirect.com/faqs and https://warehousedirect.com/groups and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://warehousedirect.com/coffee-and-breakroom, whose canonical is https://warehousedirect.com/coffee. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://warehousedirect.com/contact-us, https://warehousedirect.com/careers and https://warehousedirect.com/products-and-expertise 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 28 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 45 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.
Content and conversion
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
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 222 words
The homepage has only about 222 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Buy Now” and “Schedule Equipment Demonstration”.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 warehousedirect.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2019.
Stack
- CMS
- HubSpot CMS
- Hosting
- HubSpot
Company
- Employees
- 317
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on warehousedirect.com, including 9 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.