ima.global website review

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

Your mobile performance score is 62 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

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

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

7 third-party services load with your homepage (Google Tag Manager, Clarity and Optanon and others), adding 705 KiB and 427 ms of main-thread time.

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

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

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

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

About 21 KiB of CSS is downloaded but never applied on this page.

Desktop scores 94 but mobile only 62. 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.

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 92 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 108 requests on a phone: scripts 963 KiB (21), images 809 KiB (28) and media 583 KiB (4). Under 2 MB keeps phones on slow connections fast.

image 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).

3 images are downloaded at several times the size a phone draws them, for example image at 2,048 px wide, shown at 342 px. Resized copies would save about 132 KiB.

1 image further down the page (94 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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.

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

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

Your title is only 12 characters: “IMA | Global”. 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 only 64 characters: “A global agency to Create Connections People Buy for our clients”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 41 pages on ima.global and 2 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 /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 /en/linkedin.com/company/imaglobal, which answers with an error. Visitors hit a dead end and search engines drop it.

/en/work, /en/services and /en/news are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/en/contact-us and /undefined/contact-us all use the title “IMA | Contact Us”. Search engines can't tell which page to show for a search, so each competes with the others.

/en/work, /en/services, /en/news, /en/contact-us, /undefined/contact-us and /en/ima-modern-slavery-act have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /undefined/contact-us, whose canonical is /en/undefined/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en/careers 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 18 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://ima.global/en/linkedin.com/company/imaglobal/ (404).

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

ima.global is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

ima.global 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.

ima.global'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.

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.

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.

The homepage carries about 276 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 Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 4 cookies (measured from a US location before any click).

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