Website review, no card needed

emkayglobal.com logo

emkayglobal.com website review

Visit site (opens in a new tab)Reviewed 3 November 202650 issues · 85 checks

This review found 50 issues worth fixing on emkayglobal.com, 20 of them high impact, across 85 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.1 s5.5 sMay 16Oct 315.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.8 s
May 23, 20266.1 s
May 30, 20266.3 s
Jun 6, 20266.6 s
Jun 13, 20266.9 s
Jun 20, 20266.8 s
Jun 27, 20266.5 s
Jul 4, 20266.3 s
Jul 11, 20266.1 s
Jul 18, 20266.0 s
Jul 25, 20265.9 s
Aug 1, 20265.8 s
Aug 8, 20265.8 s
Aug 15, 20265.7 s
Aug 22, 20265.8 s
Aug 29, 20265.9 s
Sep 5, 20266.0 s
Sep 12, 20266.1 s
Sep 19, 20266.1 s
Sep 26, 20266.2 s
Oct 3, 20266.2 s
Oct 10, 20266.0 s
Oct 17, 20266.0 s
Oct 24, 20265.9 s
Oct 31, 20265.8 s
Real-visitor tap response (INP)75th percentile, phones
257 ms136 msMay 16Oct 31150 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026206 ms
May 23, 2026201 ms
May 30, 2026242 ms
Jun 6, 2026243 ms
Jun 13, 2026224 ms
Jun 20, 2026219 ms
Jun 27, 2026185 ms
Jul 4, 2026185 ms
Jul 11, 2026178 ms
Jul 18, 2026174 ms
Jul 25, 2026160 ms
Aug 1, 2026154 ms
Aug 8, 2026154 ms
Aug 15, 2026156 ms
Aug 22, 2026166 ms
Aug 29, 2026167 ms
Sep 5, 2026160 ms
Sep 12, 2026158 ms
Sep 19, 2026150 ms
Sep 26, 2026151 ms
Oct 3, 2026159 ms
Oct 10, 2026154 ms
Oct 17, 2026158 ms
Oct 24, 2026150 ms
Oct 31, 2026150 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of emkayglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. emkayglobal.com at 0.8 s0.8 s
  2. emkayglobal.com at 1.6 s1.6 s
  3. emkayglobal.com at 2.4 s2.4 s
  4. emkayglobal.com at 3.2 s3.2 s
  5. emkayglobal.com at 3.9 s3.9 s
  6. emkayglobal.com at 4.7 s4.7 s
  7. emkayglobal.com at 5.5 s5.5 s
  8. emkayglobal.com at 6.3 s6.3 s

Speed

13 to fix35
  • Improve image delivery

    8.7 s · 3.4 MB

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

  • Reduce unused JavaScript

    7.2 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

  • Render-blocking requests

    6.5 s

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

  • Reduce unused CSS

    2.9 s · 605 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Document request latency

    700 ms · 168 KiB

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

  • Minify CSS

    600 ms · 135 KiB

    135 KiB could be saved by minifying CSS.

  • 7 third-party services on the page

    7 third-party services load with your homepage (YouTube, Google Tag Manager and Cloudflare CDN and others), adding 1.2 MB and 579 ms of main-thread time.

  • Reduce initial server response time

    695 ms

    Reduce initial server response time. Google estimates savings of 695 ms on a phone.

  • YouTube adds 376 ms

    376 ms

    YouTube costs a phone 376 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.

  • Minify JavaScript

    300 ms · 120 KiB

    120 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    350 ms · 62 KiB

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

  • Server response: 795 ms

    795 ms

    Your server takes 795 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 6 long tasks on the main thread

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 955 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.9 s

    4.9 s

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

  • Real-user CLS: 0.41

    0.41

    For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • First Contentful Paint: 9.5 s

    9.5 s

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

  • Largest Contentful Paint: 33.7 s

    33.7 s

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

  • Speed Index: 17.8 s

    17.8 s

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

  • Time to Interactive: 34.0 s

    34.0 s

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

  • Cumulative Layout Shift: 0.405

    0.405

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 13 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 26% faster for real visitors

    -26%

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

  • Total Blocking Time: 129 ms

    129 ms

    Scripts block the page for only 129 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 7.2 MB in 112 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 112 requests on a phone: images 4.0 MB (46), scripts 2.3 MB (32) and stylesheets 600 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    award1.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    696 KiB

    5 images are downloaded at several times the size a phone draws them, for example 870e2a28-27db-4c19-89e0-bbee72159f52.png at 1,280 px wide, shown at 260 px. Resized copies would save about 696 KiB.

  • 23 images in older formats

    23 images (3.8 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.

  • 9 images below the first screen load straight away

    9 images further down the page (710 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.05 g

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

Accessibility

4 to fixGoogle 9095
  • 5 tap targets too small

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 6770
  • No meta description

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

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No robots.txt

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

  • 11 links with vague text

    11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 64 internal links, 25 external

    The homepage links to 64 pages on emkayglobal.com and 25 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Emkay Global Financial Services”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Emkay Global: A Research & Investment Powerhouse”.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.emkayglobal.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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,279 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.emkayglobal.com/global-investing/index and https://www.emkayglobal.com/indiainx/index have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

5 to fixGoogle 4681
  • 15 small tap targets

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

  • 5 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'Constructor')”.

  • 8 distorted images

    8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 29-field form

    Your longest form asks for 29 fields (17 required). Every extra field lowers completion.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 637 words of copy

    The homepage carries about 637 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REGISTER”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Register” and “Contact us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 10 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at emkayglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
F5 Networks SARL

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on emkayglobal.com, including 24 speed issues, 7 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25