mtiamerica.com website review

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

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

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

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

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

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

Google Tag Manager costs a phone 276 ms of main-thread work and 428 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.

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

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

Vimeo costs a phone 37 ms of main-thread work and 516 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.

6 third-party services load with your homepage (Google Tag Manager, Vimeo and LinkedIn Ads and others), adding 973 KiB and 343 ms of main-thread time.

10 images could be 217 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

35 KiB could be saved by minifying JavaScript.

17 KiB could be saved by minifying CSS.

Polyfills for old browsers add 10 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.

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.

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

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We know that it is through empathy – through understanding …”. Most of its time is element render delay (4.9 s).

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

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

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

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

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

Your homepage downloads 5.8 MB in 153 requests on a phone: media 2.8 MB (2), scripts 1.4 MB (48) and fonts 713 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example hearingImpairedweb.jpg at 1,170 px wide, shown at 351 px. Resized copies would save about 24 KiB.

4 images (192 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.

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

25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 66 characters, so Google will cut it off around 60: “MTI America – Workers’ Compensation Ancillary Healthcare Solutions”.

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

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

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 120 pages on mtiamerica.com and 9 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.mtiamerica.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.mtiamerica.com/service-providers/how-to-become-a-network-provider, https://www.mtiamerica.com/ez-referral, https://www.mtiamerica.com/service/transportation, https://www.mtiamerica.com/service/language-services, https://www.mtiamerica.com/service/video-remote-interpretation and https://www.mtiamerica.com/service/physical-medicine and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mtiamerica.com/service-providers/how-to-become-a-network-provider, https://www.mtiamerica.com/ez-referral, https://www.mtiamerica.com/service/transportation, https://www.mtiamerica.com/service/language-services, https://www.mtiamerica.com/service/physical-medicine and https://www.mtiamerica.com/service/complex-rehab-mobility-program and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mtiamerica.com/service/home-antibiotic-therapy-program, https://www.mtiamerica.com/service/orthotics-prosthetics, https://www.mtiamerica.com/service/home-vehicle-modifications and https://www.mtiamerica.com/service/at-home-wound-care-healing-program took over 3 s to send their HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “screenReaderText is not defined”.

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

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