Website review, no card needed

ifastcorp.com logo

ifastcorp.com website review

Visit site (opens in a new tab)Reviewed 2 November 202644 issues · 68 checks

This review found 44 issues worth fixing on ifastcorp.com, 10 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. 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
1.8 s1.2 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
98 ms78 msMay 16Oct 3190 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202689 ms
May 30, 202685 ms
Jun 6, 202691 ms
Jun 13, 202689 ms
Jun 20, 202689 ms
Jun 27, 202693 ms
Jul 4, 202689 ms
Jul 11, 202690 ms
Jul 18, 202689 ms
Jul 25, 202694 ms
Aug 1, 202691 ms
Aug 8, 202693 ms
Aug 15, 202694 ms
Aug 22, 202692 ms
Aug 29, 202696 ms
Sep 5, 202689 ms
Sep 12, 202688 ms
Sep 19, 202683 ms
Sep 26, 202682 ms
Oct 3, 202680 ms
Oct 10, 202681 ms
Oct 17, 202682 ms
Oct 24, 202686 ms
Oct 31, 202690 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 ifastcorp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ifastcorp.com at 0.4 s0.4 s
  2. ifastcorp.com at 0.8 s0.8 s
  3. ifastcorp.com at 1.1 s1.1 s
  4. ifastcorp.com at 1.5 s1.5 s
  5. ifastcorp.com at 1.9 s1.9 s
  6. ifastcorp.com at 2.3 s2.3 s
  7. ifastcorp.com at 2.6 s2.6 s
  8. ifastcorp.com at 3.0 s3.0 s

Speed

12 to fix70
  • Use efficient cache lifetimes

    2.1 s · 21.0 MB

    67 files are served with short cache lifetimes, so returning visitors download them again (21.0 MB).

  • Render-blocking requests

    1.0 s

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

  • Improve image delivery

    14.4 MB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (ifasttv.com, Google Tag Manager and Facebook and others), adding 5.8 MB and 1.5 s of main-thread time.

  • Mobile performance score: 70

    70/100

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

  • Avoid multiple page redirects

    761 ms

    The page goes through 1 redirect before it starts loading, costing about 761 ms. Link and advertise the final URL directly.

  • ifasttv.com adds 613 ms

    613 ms

    ifasttv.com costs a phone 613 ms of main-thread work and 1.2 MB 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.

  • Google Tag Manager adds 602 ms

    602 ms

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

  • Reduce unused JavaScript

    508 KiB

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

  • LongTail Ad Solutions adds 72 ms

    72 ms

    LongTail Ad Solutions costs a phone 72 ms of main-thread work and 3.4 MB 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.

  • Font display

    400 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).

  • Main-thread work: 3.3 s

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

  • 18 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 15 KiB

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

  • Legacy JavaScript

    7 KiB

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

  • 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
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 27.1 s

    27.1 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Largest content (LCP) got 28% slower for real visitors

    +28%

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

  • Total Blocking Time: 522 ms

    522 ms

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 86 ms

    86 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 780 ms

    780 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix0
  • Page weight: 23.0 MB in 117 requests

    23.0 MB

    Your homepage downloads 23.0 MB in 117 requests on a phone: images 20.0 MB (32), scripts 1.7 MB (38) and other files 444 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • About 6.5 g of CO₂ per visit

    6.51 g

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

Accessibility

3 to fix76
  • Links do not have a discernible name

    Links do not have a discernible name (9 elements).

  • 7 text elements with low contrast

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

SEO

11 to fixGoogle 7352
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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.ifastcorp.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

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

1 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “Group Company for Fundsupermart.com and iFAST Platform Services across selected countries in Asia”.

AI search readiness

1 to fix83
  • 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.ifastcorp.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
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

5 to fixGoogle 8526
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • No character set

    No character set is declared, so some characters can render as gibberish.

  • 5 distorted images

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

  • 2 console errors

    2 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_CONNECTION_FAILED”).

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

Content and conversion

5 to fix30
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

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

Upkeep, stack and company

Stack

Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on ifastcorp.com, including 18 speed issues, 11 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