texasbar.com website review

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

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.9 MB and 826 ms of main-thread time.

About 759 KiB of JavaScript is downloaded but never used on this page.

Google/Doubleclick Ads costs a phone 397 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.

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

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

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

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

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

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

25 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

30 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

The layout shifts by 1.285 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The State Bar of Texas Seal”.

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 115 requests on a phone: scripts 1.5 MB (37), images 815 KiB (24) and fonts 292 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images (244 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.

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

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

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

2 elements hidden from screen readers can still receive keyboard focus.

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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.

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

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

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 (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is only 25 characters: “State Bar of Texas | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

No XML sitemap at https://www.texasbar.com/sitemap.xml, so Google discovers your pages only by following links.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 207 pages on texasbar.com and 70 external pages.

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.

There is no /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.

Your homepage links to /iwasthefirst, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

5 errors were logged to the browser console while the page loaded, for example “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.

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

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

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

The homepage carries about 715 words of visible text.

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.

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

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.

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.