Website review, no card needed

warehouserack.com logo

warehouserack.com website review

Visit site (opens in a new tab)Reviewed 4 November 202649 issues · 96 checks

This review found 49 issues worth fixing on warehouserack.com, 16 of them high impact, across 96 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.0 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.6 s
Aug 15, 20262.9 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
83 ms70 msMay 16Oct 3176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202671 ms
May 23, 202671 ms
May 30, 202672 ms
Jun 6, 202672 ms
Jun 13, 202678 ms
Jun 20, 202679 ms
Jun 27, 202678 ms
Jul 4, 202678 ms
Jul 11, 202677 ms
Jul 18, 202675 ms
Jul 25, 202677 ms
Aug 1, 202677 ms
Aug 8, 202679 ms
Aug 15, 202681 ms
Aug 22, 202681 ms
Aug 29, 202680 ms
Sep 5, 202674 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202677 ms
Oct 10, 202678 ms
Oct 17, 202678 ms
Oct 24, 202678 ms
Oct 31, 202676 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

Full-page screenshot of warehouserack.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. warehouserack.com at 1.4 s1.4 s
  2. warehouserack.com at 2.7 s2.7 s
  3. warehouserack.com at 4.1 s4.1 s
  4. warehouserack.com at 5.5 s5.5 s
  5. warehouserack.com at 6.9 s6.9 s
  6. warehouserack.com at 8.2 s8.2 s
  7. warehouserack.com at 9.6 s9.6 s
  8. warehouserack.com at 11.0 s11.0 s

Speed

11 to fix50
  • Use efficient cache lifetimes

    5.8 s · 13.7 MB

    111 files are served with short cache lifetimes, so returning visitors download them again (13.7 MB).

  • Improve image delivery

    4.2 s · 6.4 MB

    43 images could be 6.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.

  • Reduce unused JavaScript

    5.7 s · 1,021 KiB

    About 1,021 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

  • Render-blocking requests

    1.4 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • 5,493 HTML elements

    The page has 5,493 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and Google Tag Manager and others), adding 2.2 MB and 1.0 s of main-thread time.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • YouTube adds 527 ms

    527 ms

    YouTube costs a phone 527 ms of main-thread work and 990 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.

  • Reduce unused CSS

    300 ms · 126 KiB

    About 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • LiveChat adds 49 ms

    49 ms

    LiveChat costs a phone 49 ms of main-thread work and 669 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.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 216 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 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.

1 checks passed
  • Server response: 574 ms

    574 ms

    Your server sent the HTML in 574 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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: 57.6 s

    57.6 s

    Your largest element takes 57.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “50 Acres of Used & New Warehouse Equipment In Stock! catego…”.

  • Time to Interactive: 61.1 s

    61.1 s

    The page becomes fully interactive after 61.1 s. Good is under 3.8 s.

  • Speed Index: 11.8 s

    11.8 s

    Visually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.3 s

    2.3 s

    Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 822 ms

    822 ms

    Real visitors wait 822 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 518 ms

    518 ms

    Scripts block taps and scrolling for 518 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 71 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 76 ms

    76 ms

    Real visitors wait 76 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

4 to fix33
  • Page weight: 16.0 MB in 177 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 177 requests on a phone: images 13.5 MB (107), scripts 2.1 MB (41) and HTML 191 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    3.3 MB

    14 images are downloaded at several times the size a phone draws them, for example fhdfthuredt5ue5u3e5.jpg at 698 px wide, shown at 111 px. Resized copies would save about 3.3 MB.

  • 40 images in older formats

    40 images (11.5 MB) are 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.

  • 14 images below the first screen load straight away

    14 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.54 g of CO₂e: 544.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

10 to fixGoogle 7485
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 36 text elements with low contrast

    36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 28 tap targets too small

    28 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (31 elements)

    All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 44 links without text

    44 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

2 checks passed
  • Every image has alt text

    All 124 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9266
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (94 characters)

    Your title is 94 characters, so Google will cut it off around 60: “Warehouse Racking Systems | Material Handling Equipment | Used Pallet Rack | WarehouseRac…”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (175 characters)

    Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 2,077 internal links, 26 external

    The homepage links to 2,077 pages on warehouserack.com and 26 external pages.

2 checks passed
  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.warehouserack.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.warehouserack.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.

2 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 (4,983 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

7 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6288
  • 102 small tap targets

    102 of 166 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 9 low-resolution images

    9 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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

2 to fix81
  • 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.

  • 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.

  • 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.

  • About 394 words of copy

    The homepage carries about 394 words of visible text.

6 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “We Buy”, “Quote Genie” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 5 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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 warehouserack.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on warehouserack.com, including 21 speed issues, 7 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25