mea.com website review

10 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and marsflag.com and others), adding 1.4 MB and 511 ms of main-thread time.

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

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

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

embedsocial.com costs a phone 30 ms of main-thread work and 310 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.

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

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 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Better begins here.”.

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

9 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 162 ms to 172 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 3.4 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 1026_di2.jpg at 1,500 px wide, shown at 360 px. Resized copies would save about 748 KiB.

Your homepage downloads 3.9 MB in 149 requests on a phone: images 2.4 MB (23), scripts 1.1 MB (73) and fonts 193 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

img_tile_serendie.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

There are 2 <h1> headlines (“” and “Better begins here.”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://www.mitsubishielectric.com/en/x-default_hreflang-sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 61 pages on mea.com and 66 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.mitsubishielectric.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mitsubishielectric.com/en/about/rd/ip/index.html, whose canonical is https://www.mitsubishielectric.com/intellectual-property/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mitsubishielectric.com/en/about/rd/index.html has 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 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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