simplyinsured.com website review

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

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

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

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

8 third-party services load with your homepage (honeybadger.io, Google Tag Manager and Hubspot and others), adding 1.5 MB and 334 ms of main-thread time.

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

site.com costs a phone 12 ms of main-thread work and 750 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.

33 KiB could be saved by minifying JavaScript.

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

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

10 KiB JavaScript is shipped twice across bundles.

Desktop scores 94 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

Real visitors wait 848 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 2.4 MB in 121 requests on a phone: scripts 1.4 MB (51), images 785 KiB (38) and stylesheets 117 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example [email protected] at 1,652 px wide, shown at 363 px. Resized copies would save about 54 KiB.

1 image (96 KiB) is 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.

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

Certain ARIA roles must contain particular children: 8 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 7 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 20 characters: “Home | SimplyInsured”. 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.

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

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

The homepage links to 16 pages on simplyinsured.com and 26 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://www.simplyinsured.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.simplyinsured.com/support has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.simplyinsured.com/support has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.simplyinsured.com/small-group/first-quote and https://www.simplyinsured.com/support 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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134615223&Ver=2&mid=f3e0dedb-cb72-4640-9519-ca1d1a3b37f3&bo=1&sid=dec3d970ce9011f18716bd535bac63d4&vid=dec40c40ce9011f19af27bf36bfd7dde&vids=1&msclkid=N&pi=918639831&l.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://simplyinsured.my.site.com/ESWSimplyInsuredSupport1787786963223/assets/styles/boots…”.

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

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

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

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