Website review, no card needed

haulaway.com logo

haulaway.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 77 checks

This review found 32 issues worth fixing on haulaway.com, 13 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
1.5 s1.1 sMay 2Sep 121.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Aug 15, 20261.3 s
Aug 29, 20261.2 s
Sep 12, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
83 ms49 msMay 2Jun 2073 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202653 ms
May 23, 202670 ms
May 30, 202670 ms
Jun 6, 202679 ms
Jun 13, 202678 ms
Jun 20, 202673 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 haulaway.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. haulaway.com at 0.6 s0.6 s
  2. haulaway.com at 1.1 s1.1 s
  3. haulaway.com at 1.7 s1.7 s
  4. haulaway.com at 2.3 s2.3 s
  5. haulaway.com at 2.8 s2.8 s
  6. haulaway.com at 3.4 s3.4 s
  7. haulaway.com at 4.0 s4.0 s
  8. haulaway.com at 4.5 s4.5 s

Speed

8 to fix47
  • Improve image delivery

    18.6 s · 3.5 MB

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

  • Reduce unused JavaScript

    6.7 s · 737 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 55). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 906 ms of main-thread time.

  • Google CDN adds 627 ms

    627 ms

    Google CDN costs a phone 627 ms of main-thread work and 1.1 MB 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

    450 ms

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 216 ms

    216 ms

    Google Tag Manager costs a phone 216 ms of main-thread work and 324 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.

  • Main-thread work: 2.3 s

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

7 to fix57
  • First Contentful Paint: 8.9 s

    8.9 s

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

  • Largest Contentful Paint: 29.2 s

    29.2 s

    Your largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 29.3 s

    29.3 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Total Blocking Time: 363 ms

    363 ms

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.028

    0.028

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

Images and page weight

3 to fix35
  • Page weight: 5.7 MB in 54 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 54 requests on a phone: images 3.6 MB (11), scripts 1.5 MB (22) and other files 352 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.0 MB

    1 image is downloaded at several times the size a phone draws it, for example rental-storage-containers.png at 2,048 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

  • 4 images in older formats

    4 images (412 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (176 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.61 g

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

Accessibility

6 to fixGoogle 9193
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

2 to fixGoogle 10086
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 48 internal links, 5 external

    The homepage links to 48 pages on haulaway.com and 5 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Storage containers, shipping containers, portable storage for rent. All container sizes. 56 years in business. We deliv…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Haulaway Storage Containers For Rent | Portable Storage Rental”.

  • Canonical URL set

    The canonical URL is https://haulaway.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://haulaway.com/sitemap_index.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://haulaway.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 (548 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://haulaway.com/leads, https://haulaway.com/industries-2, https://haulaway.com/all-containers, https://haulaway.com/arizona, https://haulaway.com/california and https://haulaway.com/colorado and 3 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://haulaway.com/leads, whose canonical is https://haulaway.com/?page_id=411. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://haulaway.com/leads has 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 21 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 3 small tap targets

    3 of 6 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

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 481 words of copy

    The homepage carries about 481 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us Now”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “GET QUOTE”, “Get A Quote” and “Call Us Now”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 haulaway.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on haulaway.com, including 15 speed issues, 2 SEO issues and 1 conversion gap. 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