wordandbrown.com website review

98 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).

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

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

About 699 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.1 s faster on a phone.

366 KiB could be saved by minifying JavaScript.

8 images could be 9.0 MB 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 CDN, Google Tag Manager and Hubspot and others), adding 2.2 MB and 1.1 s of main-thread time.

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

Google CDN costs a phone 476 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.

202 KiB could be saved by minifying CSS.

Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 294 ms of main-thread work and 662 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 3.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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.

Your homepage downloads 22.8 MB in 266 requests on a phone: images 17.9 MB (64), scripts 3.1 MB (66) and stylesheets 873 KiB (29). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example WB.2019.Logo.PMS.Full.jpg at 1,009 px wide, shown at 179 px. Resized copies would save about 39 KiB.

3 images (137 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.

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

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

Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

Your canonical URL points to wordandbrown.comhttps, not wordandbrown.com, so Google may credit that host instead.

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

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

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

There is no robots.txt at wordandbrown.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 144 pages on wordandbrown.com and 13 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 https://wordandbrown.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.

/ and https://wordandbrown.com/Kentico.PageBuilder/Forms/WordandbrownMVC.Widget.HomeHeroHeader/Home/Index all use the title “Word & Brown General Agency | We Make Insurance Sales Easier”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://wordandbrown.com/compliance and https://wordandbrown.com/wbcompliance-team use the same meta description. A description written for each page earns more clicks.

https://wordandbrown.com/newsroom took over 3 s to send its HTML from our server.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://wordandbrown.com' has been blocked…”.

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

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

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

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