Website review, no card needed

axismf.com logo

axismf.com website review

Visit site (opens in a new tab)Reviewed 18 November 202642 issues · 91 checks

This review found 42 issues worth fixing on axismf.com, 11 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
10.8 s2.1 sMay 30Nov 143.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20264.0 s
Jun 20, 20265.9 s
Jun 27, 20269.4 s
Jul 4, 20269.8 s
Jul 11, 20269.4 s
Jul 18, 20268.6 s
Jul 25, 20266.7 s
Aug 1, 20265.2 s
Aug 8, 20264.7 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.1 s
Sep 12, 20263.7 s
Sep 19, 20263.1 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Oct 31, 20263.4 s
Nov 7, 20263.3 s
Nov 14, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
378 ms240 msMay 30Nov 14260 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026275 ms
Jun 6, 2026280 ms
Jun 13, 2026278 ms
Jun 20, 2026305 ms
Jun 27, 2026346 ms
Jul 4, 2026360 ms
Jul 11, 2026362 ms
Jul 18, 2026357 ms
Jul 25, 2026335 ms
Aug 1, 2026318 ms
Aug 8, 2026309 ms
Aug 15, 2026309 ms
Aug 22, 2026313 ms
Aug 29, 2026308 ms
Sep 5, 2026296 ms
Sep 12, 2026276 ms
Sep 19, 2026257 ms
Sep 26, 2026256 ms
Oct 3, 2026257 ms
Oct 10, 2026261 ms
Oct 17, 2026265 ms
Oct 24, 2026267 ms
Oct 31, 2026265 ms
Nov 7, 2026265 ms
Nov 14, 2026260 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 axismf.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. axismf.com at 1.4 s1.4 s
  2. axismf.com at 2.8 s2.8 s
  3. axismf.com at 4.1 s4.1 s
  4. axismf.com at 5.5 s5.5 s
  5. axismf.com at 6.9 s6.9 s
  6. axismf.com at 8.3 s8.3 s
  7. axismf.com at 9.6 s9.6 s
  8. axismf.com at 11.0 s11.0 s

Speed

10 to fix50
  • Render-blocking requests

    2.3 s

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

  • Main-thread work: 6.4 s

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

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    900 ms · 169 KiB

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

  • Mobile performance score: 50

    50/100

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

  • Document request latency

    800 ms

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

  • Reduce initial server response time

    790 ms

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

  • 16 long tasks on the main thread

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

  • 2,780 HTML elements

    The page has 2,780 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 890 ms

    890 ms

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

  • Use efficient cache lifetimes

    150 ms · 206 KiB

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

  • Legacy JavaScript

    54 KiB

    Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    54 KiB

    54 KiB could be saved by minifying JavaScript.

  • 2 third-party services on the page

    2 third-party services load with your homepage (clevertap-prod.com and Facebook), adding 1 KiB and 22 ms of main-thread time.

  • Improve image delivery

    10 KiB

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

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

10 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 CLS: 0.27

    0.27

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

  • Time to Interactive: 13.9 s

    13.9 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Real-user INP: 299 ms

    299 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Largest content (LCP) got 25% faster for real visitors

    -25%

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

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 165 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 165 requests on a phone: scripts 1.8 MB (73), images 300 KiB (55) and stylesheets 274 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Defence_Mobile_Banner_7d683c4dee.webp 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).

  • About 0.8 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9191
  • 4 text elements with low contrast

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

  • Form elements should have a visible label (2 elements)

    Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 234 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • Meta description is long (183 characters)

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

  • 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 X (Twitter) card tag

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

  • 270 internal links, 30 external

    The homepage links to 270 pages on axismf.com and 30 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Trending Mutual Funds”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Mutual Funds: Invest in Mutual Funds Online | Axis Mutual Fund”.

  • Canonical URL set

    The canonical URL is https://www.axismf.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.axismf.com/sitemap-index.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.axismf.com/llms.txt (42 KiB, 154 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.axismf.com/corporate-investments has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.axismf.com/corporate-investments is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.axismf.com/corporate-investments has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.axismf.com/campaign/daily-sip, https://www.axismf.com/campaign/micro-investing and https://www.axismf.com/nfo have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.axismf.com/mutual-funds/equity-funds/axis-innovation-fund/ss-dg/direct and https://www.axismf.com/mutual-funds/index-funds/axis-nifty-smallcap-50-index-fund/ns-dg/direct took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 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.

Best practices

2 to fixGoogle 8591
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Ignoring duplicate Content-Security-Policy directive 'img-src'.”.

  • 11 distorted images

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

  • 2 low-resolution images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    138 of 144 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix64
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,489 words of copy

    The homepage carries about 1,489 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe For Passives”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Subscribe For Passives”, “Start Here” and “What is 'Buy the Dip' All About?”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 2 other companies contacted

    Loading the homepage contacts 2 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 axismf.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Microsoft Clarity
Hosting
Akamai

Company

Founded
2009
Headquarters
Mumbai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on axismf.com, including 20 speed issues, 2 SEO issues and 5 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