Website review, no card needed

1stbrokerage.com logo

1stbrokerage.com website review

Visit site (opens in a new tab)Reviewed 21 November 202642 issues · 85 checks

This review found 42 issues worth fixing on 1stbrokerage.com, 15 of them high impact, across 85 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

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

How it loaded on a phone

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

Speed

11 to fix51
  • Reduce unused JavaScript

    5.0 s · 965 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 361 KiB

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

  • Render-blocking requests

    1.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Weebly and Google Tag Manager and others), adding 2.1 MB and 873 ms of main-thread time.

  • Mobile performance score: 51

    51/100

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

  • Reduce unused CSS

    450 ms · 77 KiB

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

  • Improve image delivery

    456 KiB

    12 images could be 456 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google CDN adds 267 ms

    267 ms

    Google CDN costs a phone 267 ms of main-thread work and 784 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.

  • Weebly adds 246 ms

    246 ms

    Weebly costs a phone 246 ms of main-thread work and 618 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.

  • Google Tag Manager adds 168 ms

    168 ms

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

  • Google Maps adds 145 ms

    145 ms

    Google Maps costs a phone 145 ms of main-thread work and 391 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.

  • 7 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix59
  • Largest Contentful Paint: 16.1 s

    16.1 s

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

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Time to Interactive: 16.3 s

    16.3 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Total Blocking Time: 306 ms

    306 ms

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

  • 20 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix65
  • Page weight: 3.6 MB in 102 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 102 requests on a phone: scripts 1.8 MB (29), images 1.5 MB (42) and fonts 183 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.2 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.

  • 2 images far larger than shown

    114 KiB

    2 images are downloaded at several times the size a phone draws them, for example adobestock-89081934_1_orig.jpeg at 1,100 px wide, shown at 290 px. Resized copies would save about 114 KiB.

  • 4 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.02 g

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

Accessibility

9 to fixGoogle 8083
  • 9 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links look like plain text

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

4 to fixGoogle 9281
  • No H1 headline

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

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

  • 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 set, so this is minor.

  • 41 internal links, 13 external

    The homepage links to 41 pages on 1stbrokerage.com and 13 external pages.

5 checks passed
  • Meta description: 85 characters

    Your meta description is 85 characters: “1st Brokerage | A Texas Real Estate Company | Austin | Dallas | Houston | San Antonio”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “1st Brokerage | A Texas Real Estate Company - 1st Brokerage”.

  • 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.1stbrokerage.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.1stbrokerage.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 (376 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.1stbrokerage.com/thank-you.html, https://www.1stbrokerage.com/community-connections.html, https://www.1stbrokerage.com/consumer-notice.html, https://www.1stbrokerage.com/services.html, https://www.1stbrokerage.com/apartment-locator-services.html and https://www.1stbrokerage.com/commercial-property.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.1stbrokerage.com/thank-you.html, https://www.1stbrokerage.com/community-connections.html, https://www.1stbrokerage.com/consumer-notice.html, https://www.1stbrokerage.com/services.html, https://www.1stbrokerage.com/apartment-locator-services.html and https://www.1stbrokerage.com/commercial-property.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.1stbrokerage.com/community-connections.html, https://www.1stbrokerage.com/consumer-notice.html and https://www.1stbrokerage.com/join-our-team.html have 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 17 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.

  • Canonical URLs point to themselves

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

  • 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

1 to fixGoogle 9693
  • 6 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

4 to fix69
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 279 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN OUR TEAM” and “CONTACT US”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Buy and Hold Program”, “JOIN OUR TEAM” and “Contact Us”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 6 cookies set on arrival

    6

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

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

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 1stbrokerage.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
Hosting
Weebly, Inc.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on 1stbrokerage.com, including 17 speed issues, 4 SEO issues and 4 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