arbella.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 1.3 MB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 950 ms of main-thread work and 1,018 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.

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

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

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

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

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

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

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

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.

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A New England Beach scene.”.

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

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

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

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

4 images weigh 27.1 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example shutterstock_2488947719.jpg at 8,192 px wide, shown at 390 px. Resized copies would save about 24.6 MB.

Your homepage downloads 5.2 MB in 123 requests on a phone: images 3.5 MB (54), scripts 1.4 MB (23) and fonts 130 KiB (2). Under 2 MB keeps phones on slow connections fast.

13 images (28.5 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.

8 images further down the page (27.1 MB) 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 1.47 g of CO₂e: 175.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 83 characters, so Google will cut it off around 60: “Personal and Business Insurance Company in New England - MA, CT | Arbella Insurance”.

There are 3 <h1> headlines (“Homeowners Insurance”, “Auto Insurance” and “Business Insurance”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 109 pages on arbella.com and 24 external pages.

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.

/bsobus and /mass-save have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

1 link to other sites is dead, for example https://connect.arbella.com/ (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 7 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://www.arbella.com/arbella-insurance/why-arbella/arbella-insurance-foundation.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

arbella.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

arbella.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 mores (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 11 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.