Website review, no card needed

b2bsaasleads.com logo

b2bsaasleads.com website review

Visit site (opens in a new tab)Reviewed 20 November 202623 issues · 69 checks

This review found 23 issues worth fixing on b2bsaasleads.com, 8 of them high impact, across 69 checks. The most urgent: font display. 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.5 s1.9 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.7 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20263.3 s
Aug 22, 20263.2 s
Sep 5, 20263.1 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
465 ms216 msMay 16Aug 8352 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026245 ms
May 23, 2026246 ms
May 30, 2026261 ms
Jun 6, 2026292 ms
Jun 13, 2026396 ms
Jun 20, 2026424 ms
Jun 27, 2026436 ms
Jul 4, 2026429 ms
Jul 11, 2026431 ms
Jul 18, 2026429 ms
Jul 25, 2026427 ms
Aug 1, 2026429 ms
Aug 8, 2026352 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 b2bsaasleads.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. b2bsaasleads.com at 0.4 s0.4 s
  2. b2bsaasleads.com at 0.8 s0.8 s
  3. b2bsaasleads.com at 1.1 s1.1 s
  4. b2bsaasleads.com at 1.5 s1.5 s
  5. b2bsaasleads.com at 1.9 s1.9 s
  6. b2bsaasleads.com at 2.3 s2.3 s
  7. b2bsaasleads.com at 2.6 s2.6 s
  8. b2bsaasleads.com at 3.0 s3.0 s

Speed

3 to fix82
  • Font display

    1.3 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).

  • Mobile performance score: 82

    82/100

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

  • Reduce unused JavaScript

    300 ms · 73 KiB

    About 73 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 195 KiB

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

  • Render-blocking requests

    150 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare and others), adding 193 KiB and 128 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    25 KiB

    1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    14 KiB

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

  • Legacy JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 127 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix88
  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tulsa’s Leading Local Storage Solution Provider”. Most of its time is element render delay (2.0 s).

  • Speed Index: 4.5 s

    4.5 s

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

  • 1 image without width and height

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

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

3 checks passed
  • Time to Interactive: 3.5 s

    3.5 s

    The page is fully interactive after 3.5 s.

  • Cumulative Layout Shift: 0.005

    0.005

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.14 g

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

4 checks passed
  • Page weight: 497 KiB in 36 requests

    497 KiB

    Your homepage downloads 497 KiB in 36 requests on a phone: fonts 224 KiB (5), scripts 199 KiB (15) and HTML 32 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails 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 (18 elements)

    All page content should be contained by landmarks: 18 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.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 4 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9274
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Tulsa Solutions Ministorage | The smart choice for mini-storage in Tulsa”.

  • No structured data

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

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

  • No favicon declared

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

  • No X (Twitter) card tag

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

  • 27 internal links, 6 external

    The homepage links to 27 pages on b2bsaasleads.com and 6 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Tulsa Solutions Ministorage”.

  • Canonical URL set

    The canonical URL is https://tulsasolutionsstorage.com/.

  • 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://tulsasolutionsstorage.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://tulsasolutionsstorage.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 (833 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix0
  • 11 linked pages are broken

    Your homepage links to https://tulsasolutionsstorage.com/about, https://tulsasolutionsstorage.com/storage-sizes, https://tulsasolutionsstorage.com/storage-guide, https://tulsasolutionsstorage.com/contact, https://tulsasolutionsstorage.com/moving-tips and https://tulsasolutionsstorage.com/movig-tips/moving-tips-that-minimize-stress and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

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

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

    The homepage carries about 783 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Call Now” and “Learn More”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 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
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

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

  • 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 b2bsaasleads.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on b2bsaasleads.com, including 7 speed issues, 5 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