Website review, no card needed

tpfx.co.id logo

tpfx.co.id website review

Visit site (opens in a new tab)Reviewed 18 November 202650 issues · 96 checks

This review found 50 issues worth fixing on tpfx.co.id, 26 of them high impact, across 96 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
8.0 s6.6 sMay 30Nov 147.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20267.5 s
Jun 6, 20267.7 s
Jun 13, 20267.8 s
Jun 20, 20267.9 s
Jun 27, 20267.8 s
Jul 4, 20267.6 s
Jul 11, 20267.6 s
Jul 18, 20267.6 s
Jul 25, 20267.5 s
Aug 1, 20267.4 s
Aug 8, 20267.4 s
Aug 15, 20267.4 s
Aug 22, 20267.4 s
Aug 29, 20267.4 s
Sep 5, 20267.3 s
Sep 12, 20267.2 s
Sep 19, 20267.0 s
Sep 26, 20267.0 s
Oct 3, 20266.9 s
Oct 10, 20266.7 s
Oct 17, 20266.9 s
Oct 24, 20267.0 s
Oct 31, 20267.2 s
Nov 7, 20267.1 s
Nov 14, 20267.1 s
Real-visitor tap response (INP)75th percentile, phones
407 ms390 msMay 30Nov 14402 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026396 ms
Jun 6, 2026401 ms
Jun 13, 2026402 ms
Jun 20, 2026399 ms
Jun 27, 2026404 ms
Jul 4, 2026399 ms
Jul 11, 2026401 ms
Jul 18, 2026402 ms
Jul 25, 2026392 ms
Aug 1, 2026394 ms
Aug 8, 2026395 ms
Aug 15, 2026398 ms
Aug 22, 2026405 ms
Aug 29, 2026405 ms
Sep 5, 2026399 ms
Sep 12, 2026394 ms
Sep 19, 2026393 ms
Sep 26, 2026394 ms
Oct 3, 2026396 ms
Oct 10, 2026398 ms
Oct 17, 2026398 ms
Oct 24, 2026400 ms
Oct 31, 2026401 ms
Nov 7, 2026398 ms
Nov 14, 2026402 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 tpfx.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tpfx.co.id at 1.5 s1.5 s
  2. tpfx.co.id at 3.1 s3.1 s
  3. tpfx.co.id at 4.6 s4.6 s
  4. tpfx.co.id at 6.2 s6.2 s
  5. tpfx.co.id at 7.7 s7.7 s
  6. tpfx.co.id at 9.2 s9.2 s
  7. tpfx.co.id at 10.8 s10.8 s
  8. tpfx.co.id at 12.3 s12.3 s

Speed

15 to fix39
  • Use efficient cache lifetimes

    30.6 s · 22.6 MB

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

  • Render-blocking requests

    25.3 s

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

  • Improve image delivery

    5.7 s · 8.3 MB

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

  • Reduce unused JavaScript

    7.9 s · 2.6 MB

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

  • Font display

    2.2 s

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

  • Reduce unused CSS

    1.8 s · 258 KiB

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

  • tradingcentral.com adds 1.1 s

    1.1 s

    tradingcentral.com costs a phone 1.1 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 6.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (tradingcentral.com, Google Tag Manager and TikTok and others), adding 6.3 MB and 2.3 s of main-thread time.

  • Google Tag Manager adds 641 ms

    641 ms

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

  • 20 long tasks on the main thread

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

  • TikTok adds 249 ms

    249 ms

    TikTok costs a phone 249 ms of main-thread work and 299 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.

  • 2,013 HTML elements

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

  • qontak.com adds 87 ms

    87 ms

    qontak.com costs a phone 87 ms of main-thread work and 325 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 CSS

    160 ms · 19 KiB

    19 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    30 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • 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: 463 ms

    463 ms

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

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: 7.6 s

    7.6 s

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

  • Real-user FCP: 8.1 s

    8.1 s

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

  • First Contentful Paint: 26.6 s

    26.6 s

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

  • Largest Contentful Paint: 51.7 s

    51.7 s

    Your largest element takes 51.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner New 545x640-app”.

  • Speed Index: 40.4 s

    40.4 s

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

  • Time to Interactive: 77.7 s

    77.7 s

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

  • Total Blocking Time: 661 ms

    661 ms

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

  • Real-user INP: 475 ms

    475 ms

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

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

2 checks passed
  • Real-user CLS: 0.09

    0.09

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

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

5 to fix14
  • Page weight: 32.4 MB in 367 requests

    32.4 MB

    Your homepage downloads 32.4 MB in 367 requests on a phone: media 14.6 MB (2), images 10.1 MB (69) and scripts 6.8 MB (97). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    1.9 MB

    7 images are downloaded at several times the size a phone draws them, for example slider-banner-1.png at 1,349 px wide, shown at 332 px. Resized copies would save about 1.9 MB.

  • 18 images in older formats

    18 images (7.7 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.

  • An image on the first screen is lazy-loaded

    Group-585x237.png 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 9.2 g of CO₂ per visit

    9.19 g

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

Accessibility

10 to fixGoogle 8487
  • Images must have alternative text (6 elements)

    Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.

  • 11 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (7 elements)

    Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • All page content should be contained by landmarks (36 elements)

    All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 161 internal links, 76 external

    The homepage links to 161 pages on tpfx.co.id and 76 external pages.

8 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “Broker forex terbaik di Indonesia dengan layanan trading profesional, spread rendah, eksekusi cepat, dan platform terpe…”.

  • One H1 headline

    Your main headline reads: “Mulai Trading di TPFx”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Broker Forex Terbaik & aman Teregulasi BAPPEBTI - TPFx”.

  • Canonical URL set

    The canonical URL is https://tpfx.co.id/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.tpfx.co.id/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 14 pages without an H1

    https://www.tpfx.co.id/tentang-kami, https://www.tpfx.co.id/spread-komisi, https://www.tpfx.co.id/partnership, https://www.tpfx.co.id/kamus-forex, https://www.tpfx.co.id/jenis-akun and https://www.tpfx.co.id/spread-komisi-old and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages slow to respond

    https://www.tpfx.co.id/spread-komisi, https://www.tpfx.co.id/partnership, https://www.tpfx.co.id/kamus-forex, https://www.tpfx.co.id/jenis-akun, https://www.tpfx.co.id/spread-komisi-old and https://www.tpfx.co.id/deposit-withdraw and 7 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5083
  • 7 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 11 distorted images

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

  • No opening hours

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

  • 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 676 words of copy

    The homepage carries about 676 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Coba Akun Demo”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Coba Akun Demo” and “Akun Demo”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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.

  • 22 cookies set on arrival

    22

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

  • 37 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Alibaba Cloud

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 tpfx.co.id, including 26 speed issues, 1 SEO issue 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