Deprecated: Optional parameter $content declared before required parameter $post is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/functions.php on line 840

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 553

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 594

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 534

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 543

Warning: Private methods cannot be final as they are never overridden by other classes in /home/blogcert/public_html/wp-includes/class-wp-session-tokens.php on line 69

Deprecated: Optional parameter $object_id declared before required parameter $taxonomy is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/nav-menu.php on line 1060

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 934

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 954

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 966

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 977

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $block_name declared before required parameter $block_content is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/blocks.php on line 405

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 386

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 378

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 372

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 390

Warning: The magic method OCDI\OneClickDemoImport::__wakeup() must have public visibility in /home/blogcert/public_html/wp-content/plugins/one-click-demo-import/inc/OneClickDemoImport.php on line 128

Deprecated: Optional parameter $type declared before required parameter $wrapper is implicitly treated as a required parameter in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/class-fs-logger.php on line 145

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/wp-db.php on line 3008

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378
{"id":3655,"date":"2021-10-11T04:39:38","date_gmt":"2021-10-11T04:39:38","guid":{"rendered":"https:\/\/blog.certifiedfinancialguardian.com\/?p=3655"},"modified":"2021-10-11T04:39:38","modified_gmt":"2021-10-11T04:39:38","slug":"sensex-above-60000-should-you-look-at-the-navs-to-select-the-best-equity-mutual-fund-schemes","status":"publish","type":"post","link":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/2021\/10\/11\/sensex-above-60000-should-you-look-at-the-navs-to-select-the-best-equity-mutual-fund-schemes\/","title":{"rendered":"Sensex Above 60,000! Should You Look at the NAVs to Select the Best Equity Mutual Fund Schemes?"},"content":{"rendered":"\n

The equity market at an all-time high<\/a> has made it challenging to find good stocks at a lower price. With Sensex above the 60,000 mark and broader market at an all-time high, investors are actively participating in Initial Public Offerings (IPOs). Investing in IPOs enables investors to benefit from the growth potential of a stock when they are available at low price.<\/p>\n\n\n\n

Considering the expensive valuations in the equity market, should consider buying equity mutual fund schemes that have low NAV?<\/p>\n\n\n\n

And,<\/p>\n\n\n\n

Does buying a mutual fund with high NAV mean the fund is expensively priced?<\/p>\n\n\n\n

First let’s understand what is mutual fund NAV…<\/strong><\/p>\n\n\n\n

The Net Asset Value (NAV) of a mutual fund scheme is the value of its assets minus liabilities, i.e. its networth. In other words, it is the market value of all the securities that the scheme holds. This value is divided by the number of outstanding units (the number of units that the fund has issued to investors) to calculate the NAV per unit. Since the markets are dynamic in nature, the NAV changes every day.<\/p>\n\n\n\n

NAV per unit = (Total Assets – Total Liabilities) \/ Total Number of Outstanding Units<\/em><\/p>\n\n\n\n

Mutual fund houses disclose the closing NAV of each scheme after deducting expenses<\/a> towards management, administration, and other costs, on a daily basis. All purchase and sale transactions of mutual funds take place at the closing NAV of the scheme.<\/p>\n\n\n\n

It is a common misconception among investors that buying a mutual fund scheme that has a low NAV will give them the higher benefit of future growth of the scheme. So, when a New Fund Offer (NFO) hits the market, many investors rush to buy lured by the ‘Rs 10 NAV’ proposition, disregarding whether the traits of the mutual fund schemes and their envisioned financial goals and risk profile sync well.<\/p>\n\n\n\n

In fact, to bust another misconception, a mutual fund NAV is not similar to the stock price of a company. Unlike stock prices, where the demand and supply influences the price, the NAV of a mutual fund is not affected by purchase and sale transactions. Likewise, NAV does not tell if the fund is available cheap or expensive. It simply denotes the current value of all securities the scheme’s portfolio holds.<\/p>\n\n\n\n

Generally, funds that have been in existence for a long time have higher NAVs which suggests that they have performed well in the past. By avoiding a scheme that has a high NAV you may be penalizing it for its stellar performance record. That said, there is no assurance that it will generate good returns in the future either.<\/p>\n\n\n\n

The NAV of a mutual fund is a useful tool to determine its performance, but it does not indicate the future prospects of a mutual fund scheme.<\/strong><\/p>\n\n\n\n

New Fund Offers (NFOs) are generally launched at a NAV of Rs 10 per unit. So, if the old scheme and the new scheme have invested in the same companies with similar weightage, they are likely to generate similar returns. Their NAV will not have an impact on their potential in any way.<\/p>\n\n\n\n

Table: NAV does not have an impact on the performance of mutual funds<\/em><\/strong><\/p>\n\n\n\n

\n
\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t
Scheme Name<\/b><\/td>\n\t\t\tLatest NAV(Rs)<\/b><\/td>\n\t\t\t1-Yr Return<\/b><\/td>\n\t\t<\/tr>\n\t\t
SBI BlueChip Fund<\/a><\/td>\n\t\t\t67.29<\/td>\n\t\t\t58.88<\/td>\n\t\t<\/tr>\n\t\t
Aditya Birla SL Frontline Equity Fund<\/a><\/td>\n\t\t\t373.51<\/td>\n\t\t\t58.25<\/td>\n\t\t<\/tr>\n\t\t
ICICI PruBluechip Fund<\/a><\/td>\n\t\t\t70.21<\/td>\n\t\t\t56.37<\/td>\n\t\t<\/tr>\n\t\t
Mirae Asset Large Cap Fund<\/a><\/td>\n\t\t\t87.56<\/td>\n\t\t\t54.01<\/td>\n\t\t<\/tr>\n\t\t
Axis Bluechip Fund<\/a><\/td>\n\t\t\t52.49<\/td>\n\t\t\t50.70<\/td>\n\t\t<\/tr>\n\t<\/tbody>\n<\/table>\n<\/div>\n<\/center>\n\n\n\n\n

Data as on October 07, 2021
(Source: ACE MF)  <\/p>\n\n\n\n

As we can see in the table above, there is a stark difference in the NAV of the two Large-cap Funds<\/a> — SBI Bluechip Fund (67.29) and Aditya Birla SL Frontline Equity Fund (373.51). However, when we compare the performance data of the two funds in the last 1 year, it is relatively close. In short, the NAV cannot be a criterion to compare the performance of schemes.<\/p>\n\n\n\n

Furthermore, if two funds have a similar NAV, it does not mean that they will generate similar returns. At the most, funds in the same category may move in one direction; but it depends on how prudently the fund manager has played his\/her role.<\/p>\n\n\n\n

Consider another instance:<\/p>\n\n\n\n

Say you have invested Rs 5,000 each in two Large-cap Funds that have similar portfolios. Fund A has a NAV of Rs 10 and Fund B has a NAV of Rs 50. When you invest Rs 5,000, you will be allotted 500 units of Fund A and 100 units of Fund B.<\/p>\n\n\n\n

Let’s assume in 1 year both funds have grown by 25%.<\/p>\n\n\n\n

The NAV of Fund A<\/strong> will be 12.5, and NAV of Fund B<\/strong> will be 62.5.<\/p>\n\n\n\n

The value of your investment will be:<\/p>\n\n\n\n

Fund A:<\/strong> 500 units x Rs 12.5 = Rs 6250<\/p>\n\n\n\n

Fund B:<\/strong> 100 units x 62.5 = Rs 6,250.<\/p>\n\n\n\n

Thus, both the funds have generated similar returns irrespective of the NAV.<\/p>\n\n\n\n

Therefore, it is wrong to assume that a mutual fund available at an NAV of, say, Rs 10 is cheaper than a mutual fund with an NAV of Rs 100 per unit. A mutual fund with a higher NAV does not mean it is expensive, just as a low NAV is not indicative that it is available at a bargain price.<\/p>\n\n\n\n

Instead of assessing the NAV of a scheme, you should focus on the following parameters to select the best equity mutual fund<\/a>:<\/p>\n\n\n\n

1) Risk-reward matrix<\/strong><\/p>\n\n\n\n

Evaluate the mutual fund’s past performance as well as performance across past market phases and cycles when compared to its peers and benchmark index. This data will give you a comprehensive idea about how consistent is the mutual fund’s performance. However, avoid giving too much weightage to past performance because it is not an indicative of future returns.<\/p>\n\n\n\n

Then determine how well the fund has rewarded its investors for the risk they have taken using risk-reward ratios like Sharpe Ratio, Sortino Ratio, and Standard Deviation over a 3-year period.<\/p>\n\n\n\n

When short listing funds for your portfolio, give preference to those funds that stand strong on risk-reward parameters.<\/p>\n\n\n\n

2) Portfolio characteristics<\/strong><\/p>\n\n\n\n

The performance of a mutual fund is extensively dependent on the quality of its underlying portfolio, i.e. stocks and other securities. A mutual fund scheme should be well-diversified across stocks\/sectors and other securities depending on its investment mandate. Remember that a concentrated portfolio can expose you, the investor, to higher risk.<\/p>\n\n\n\n

Moreover, ensure that the fund has a reasonable turnover ratio. High turnover can make a fund more volatile and also lead to higher expense ratio, which can impact the overall returns.<\/p>\n\n\n\n

3) Qualitative indicators<\/strong><\/p>\n\n\n\n

Qualitative parameters are often overlooked though they are a vital aspect in the selection process. It involves determining the quality of the portfolio and the efficiency of fund manager\/house.<\/p>\n\n\n\n

The mutual fund house should have a significant performance record and must follow robust investment processes with adequate risk management systems in place.<\/p>\n\n\n\n

And because the fund’s performance is directly dependent on the ability of its fund manager, check the qualification and experience of the fund manager and the track record of the other schemes they manage.<\/p>\n\n\n\n

4) Asset under Management (AUM)<\/strong><\/p>\n\n\n\n

The Mutual fund AUM<\/a>, also known as corpus, indicates how big or small a scheme is. Note that while a high AUM shows the funds growing popularity, it does not necessarily mean that it will translate into better returns. On the contrary, it may hamper the fund’s ability to perform.<\/p>\n\n\n\n

A large corpus can make it difficult for a mutual fund scheme to actively manage the portfolio and time the entry and exit more efficiently, in line with changing market conditions. A Large-cap oriented mutual fund can still deliver decent performance despite its large AUM because large-cap stocks are highly liquid. But if the mutual fund is mandated to invest across market capitalisation, a large asset size may cause constraints as mid and small caps are less liquid.<\/p>\n\n\n\n

Given the burgeoning size of some equity funds in India, it is best to assess the proportion of AUM actually performing.<\/p>\n\n\n\n

Most importantly, the scheme that you choose should be in alignment with your risk appetite, financial goals, and investment horizon. Following these principles while selecting a mutual fund and it will surely help you to build a winning mutual fund portfolio.<\/p>\n\n\n\n

This article first appeared on PersonalFN\u00a0here<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

The equity market at an all-time high has made it challenging to find good stocks at a lower price. With Sensex above the 60,000 mark and broader market at an all-time high, investors are actively participating in Initial Public Offerings (IPOs). Investing in IPOs enables investors to benefit from the growth potential of a stock…<\/p>\n","protected":false},"author":5,"featured_media":3656,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"cybocfi_hide_featured_image":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/3655"}],"collection":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/comments?post=3655"}],"version-history":[{"count":1,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/3655\/revisions"}],"predecessor-version":[{"id":3657,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/3655\/revisions\/3657"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/media\/3656"}],"wp:attachment":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/media?parent=3655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/categories?post=3655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/tags?post=3655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}