unitedfiregroup.com website review

4 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

Google Tag Manager costs a phone 301 ms of main-thread work and 331 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 third-party services load with your homepage (Google Tag Manager, Optanon and FullStory and others), adding 696 KiB and 480 ms of main-thread time.

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

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

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

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

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

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

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.

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

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

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When you visit UFG’s website, we store cookies, tags or emb…”. Most of its time is element render delay (2.6 s).

10 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-31, real Chrome visitors' tap response (inp) went from 85 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.3 MB in 61 requests on a phone: images 4.4 MB (15), scripts 714 KiB (18) and stylesheets 82 KiB (9). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example homepage-banner-construction.jpg at 3,333 px wide, shown at 390 px. Resized copies would save about 3.5 MB.

6 images (4.3 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.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 81 characters, so Google will cut it off around 60: “UFG Insurance | Business insurance, excess and surplus, surety bonds, reinsurance”.

Structured data found (Corporation) but with 1 problem, for example “Corporation: missing @context (expected "https://schema.org")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

3 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 73 pages on unitedfiregroup.com and 5 external pages.

There is no https://www.ufginsurance.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.

https://www.ufginsurance.com/insurance/products and https://www.ufginsurance.com/insurance/products/business all use the title “Commercial Insurance Products | UFG Insurance”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ufginsurance.com/insurance/products and https://www.ufginsurance.com/insurance/products/business use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ufginsurance.com/about-ufg/ufg-news, whose canonical is https://www.ufginsurance.com/about-ufg/ufg-news/2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ufginsurance.com/insurance/products/excess-and-surplus has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://qvdt3feo.com/events.js' violates the following Content Security Policy directive: "script-s…”.

2 images are served at too low a resolution for sharp phone screens.

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.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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

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 324 words of visible text.

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

Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

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