Website review, no card needed

guardianstorage.com logo

guardianstorage.com website review

Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 90 checks

This review found 39 issues worth fixing on guardianstorage.com, 14 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
5.9 s2.3 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20263.5 s
May 16, 20264.1 s
May 23, 20264.4 s
May 30, 20264.7 s
Jun 6, 20265.2 s
Jun 13, 20265.5 s
Jun 20, 20265.5 s
Jun 27, 20265.4 s
Jul 4, 20264.8 s
Jul 11, 20263.8 s
Jul 18, 20263.4 s
Jul 25, 20263.1 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
221 ms154 msMay 2Oct 17208 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026162 ms
May 9, 2026169 ms
May 16, 2026172 ms
May 23, 2026179 ms
May 30, 2026192 ms
Jun 6, 2026206 ms
Jun 13, 2026213 ms
Jun 20, 2026210 ms
Jun 27, 2026212 ms
Jul 4, 2026202 ms
Jul 11, 2026194 ms
Jul 18, 2026188 ms
Jul 25, 2026187 ms
Aug 1, 2026185 ms
Aug 8, 2026183 ms
Aug 15, 2026185 ms
Aug 22, 2026187 ms
Aug 29, 2026187 ms
Sep 5, 2026191 ms
Sep 12, 2026198 ms
Sep 19, 2026201 ms
Sep 26, 2026202 ms
Oct 3, 2026205 ms
Oct 10, 2026205 ms
Oct 17, 2026208 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 guardianstorage.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. guardianstorage.com at 0.4 s0.4 s
  2. guardianstorage.com at 0.8 s0.8 s
  3. guardianstorage.com at 1.1 s1.1 s
  4. guardianstorage.com at 1.5 s1.5 s
  5. guardianstorage.com at 1.9 s1.9 s
  6. guardianstorage.com at 2.3 s2.3 s
  7. guardianstorage.com at 2.7 s2.7 s
  8. guardianstorage.com at 3.1 s3.1 s

Speed

12 to fix43
  • Reduce unused JavaScript

    5.2 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 576 KiB

    23 files are served with short cache lifetimes, so returning visitors download them again (576 KiB).

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43 (desktop: 63). 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 Hello Bar and others), adding 2.2 MB and 1.2 s of main-thread time.

  • Google Tag Manager adds 588 ms

    588 ms

    Google Tag Manager costs a phone 588 ms of main-thread work and 810 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: 3.6 s

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

  • Facebook adds 289 ms

    289 ms

    Facebook costs a phone 289 ms of main-thread work and 304 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.

  • 14 long tasks on the main thread

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

  • 1,752 HTML elements

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

  • Google Maps adds 82 ms

    82 ms

    Google Maps costs a phone 82 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.

  • userway.org adds 46 ms

    46 ms

    userway.org costs a phone 46 ms of main-thread work and 360 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

    150 ms · 187 KiB

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

  • Minify JavaScript

    150 ms · 48 KiB

    48 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    50 ms · 112 KiB

    5 images could be 112 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • Legacy JavaScript

    58 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 55 ms

    55 ms

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

Core Web Vitals

9 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: 25.8 s

    25.8 s

    Your largest element takes 25.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A person relaxes on a couch, stretching with a joyful expre…”.

  • Time to Interactive: 29.2 s

    29.2 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Real-user INP: 265 ms

    265 ms

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

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

    +25%

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Total Blocking Time: 508 ms

    508 ms

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 702 ms

    702 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 218 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 218 requests on a phone: scripts 2.5 MB (129), images 796 KiB (28) and other files 658 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (51 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.

  • 1 image below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.7 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

5 to fixGoogle 9393
  • Scrollable region must have keyboard access (6 elements)

    Scrollable region must have keyboard access: 6 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • 7 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 9276
  • Title is long (129 characters)

    Your title is 129 characters, so Google will cut it off around 60: “Storage Units in Pittsburgh, West Virginia & Colorado | Self Storage Units Near Me | Stor…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Units Starting as Low as $12! *” and “Units Starting as Low as $19!*”). One clear main headline is easier for people and search engines.

  • Meta description is long (256 characters)

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

  • Structured data has 1 problem

    Structured data found (ImageObject, Organization, SelfStorage and WebPage) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

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

  • 95 internal links, 93 external

    The homepage links to 95 pages on guardianstorage.com and 93 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.guardianstorage.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.guardianstorage.com/sitemap_index.xml.

AI search readiness

100
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: 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 (3,578 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://www.guardianstorage.com/storage-amenities and https://www.guardianstorage.com/go-green-with-guardian use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.guardianstorage.com/colorado, https://www.guardianstorage.com/west-virginia, https://www.guardianstorage.com/upcoming-locations-2, https://www.guardianstorage.com/pay-online, https://www.guardianstorage.com/why-guardian and https://www.guardianstorage.com/guardian-gives and 7 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 36 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56300200&Ver=2&mid=6f06a038-2a38-41c2-a7a1-b61d7410b546&bo=1&sid=b0137a80d07711f1aaaa6b5e2f619b96&vid=b01366e0d07711f1beb7b3d8f13804a2&vids=1&msclkid=N&pi=918639831&lg.

  • 8 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “fusionLightboxVars is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,323 words of copy

    The homepage carries about 1,323 words of visible text.

9 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 2 customer or partner logos, a star rating and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, HubSpot, Segment and Matomo.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

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

  • 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

  • 6 trackers load before any consent

    6

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies (measured from a US location before any click).

  • 33 other companies contacted

    Loading the homepage contacts 33 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 guardianstorage.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 Tag Manager | Segment | Matomo

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 guardianstorage.com, including 21 speed issues, 6 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