fisdom.com website review

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

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

7 third-party services load with your homepage (Google Tag Manager, Facebook and moengage.com and others), adding 1.0 MB and 862 ms of main-thread time.

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

About 375 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

8 KiB could be saved by minifying CSS.

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.2 MB in 130 requests on a phone: images 1.1 MB (59), scripts 1.1 MB (24) and stylesheets 31 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example best_fintech_2023.jpg at 1,613 px wide, shown at 390 px. Resized copies would save about 26 KiB.

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

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

The homepage links to 45 pages on fisdom.com and 31 external pages.

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.

/pms, /mutual-fund, /research-home, /blog, /calculators and /aboutus and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/customer-service and /become-a-partners have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

3 links from your homepage to your own site are broken, for example https://www.fisdom.com/?page_id=14727 (404).

2 links to other sites are dead, for example https://app.fisdom.com/login?base_url=https://my.fisdom.com&generic_callback=true (404).

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://fisdom.onelink.me/VCH6/9d184034.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

fisdom.com 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.

fisdom.com'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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 1,857 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 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.

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

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.

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