tmamerica.com website review

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

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

6 images could be 318 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

8 third-party services load with your homepage (YouTube, allyable.com and Google Tag Manager and others), adding 1.9 MB and 1.2 s of main-thread time.

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

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

YouTube costs a phone 637 ms of main-thread work and 986 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.

allyable.com costs a phone 308 ms of main-thread work and 482 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.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

6 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

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.

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tokio Marine America header image”.

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

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

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

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

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

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

11 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' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 67 requests on a phone: scripts 1.6 MB (26), images 426 KiB (11) and fonts 227 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images (297 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 (69 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.71 g of CO₂e: 84.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 3 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.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

Your title is 83 characters, so Google will cut it off around 60: “Tokio Marine America 東京海上アメリカ – US Based Commercial Property and Casualty Insurance”.

There are 2 <h1> headlines (“Tokio Marine America” and “Tokio MarineAmerica”). One clear main headline is easier for people and search engines.

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

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

Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("www.tmamerica.com")”.

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

The homepage links to 41 pages on tmamerica.com and 13 external pages.

There is no https://tmamerica.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://tmamerica.com/products/personal-lines.aspx has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected identifier 'content'”.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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.

The homepage has only about 223 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

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 8 cookies, 1 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.