Rahmat Wibowo declared InfraLoka's site the winner over Petra Novandi Barus's SawitPRO

He published an AI 'Pure Engineering Audit' comparing InfraLoka's website with SawitPRO's on PageSpeed scores alone, declaring 'INFRALOKA (RAHMAT WIBOWO) WINS' with 9.3/10 against 7.0/10 for Petra Novandi Barus's company.

Original post ↗

Rahmat Wibowo declared InfraLoka's site the winner over Petra Novandi Barus's SawitPRO

Commentary

What he posted

He published it on InfraLoka’s blog on 26 September 2026 under “Professional Blacklist”, titled “AEGIS Pure Engineering Audit: Rahmat Wibowo (InfraLoka) vs. Petra Novandi Barus (SawitPRO)”. It compares InfraLoka’s PageSpeed scores of 99 on desktop and mobile with SawitPRO’s 89 and 59, stating that “academic degrees, social media reach, and personal branding” were “completely discarded”. It infers that SawitPRO’s slower page “strongly implies” unoptimised bundles with “potential CVEs”. It ends: “Final Engineering Verdict: INFRALOKA (RAHMAT WIBOWO) WINS”, scoring 9.3 against 7.0.

Context

He has tagged SawitPRO in his posts about Petra since May, including one asking whether the company was “toxic” (ev-20260527-004, ev-20260528-003). The same day he published a similar audit ranking himself above four other engineers (ev-20260926-006).

Observations

A company website measured against a blog

InfraLoka’s site is a marketing blog; SawitPRO’s is a business serving its users. Comparing their homepage speed says little about the engineering behind either. The audit presents it as a contest between two people.

Security risk inferred from a speed score

The report goes from a mobile score of 59 to “potential CVEs” and “exposed business logic”. None of this is tested; it is described as what a slower page “often” contains. A vulnerability claim about Petra’s company rests on a guess.

Petra’s employer named again in the title

The title puts SawitPRO beside Petra’s name under “Professional Blacklist”. He has repeatedly tagged the company in posts about Petra (ev-20260527-004). The employer is drawn into a dispute that is with one person.

Transcript

Home / Professional Blacklist / AEGIS Pure Engineering Audit: Rahmat Wibowo (InfraLoka) vs. Petra Novandi Barus (SawitPRO) Professional Blacklist: personal dispute documentation Thought Leadership AEGIS Pure Engineering Audit: Rahmat Wibowo (InfraLoka) vs. Petra Novandi Barus (SawitPRO) Rahmat Wibowo · September 26, 2026 A zero-bias AEGIS Module [H] engineering audit strips away academic pedigree, tenure, and personal branding to compare InfraLoka and SawitPRO on raw architecture and Core Web Vitals alone — and the numbers aren't close. AEGIS Module [H] — Pure Engineering Audit Technical Performance & Architecture Analysis: InfraLoka vs. SawitPRO Version: 2.1 (Strict Engineering Audit) Author: AEGIS Technical Assessment Engine Scope Constraint: Pure Engineering Results Only. ZERO bias by academic background, follower count, tenure, or business experience. 1. Methodology & Scope This report conducts a strict engineering and architectural comparison between two platforms led by IT leaders: Rahmat Wibowo (InfraLoka) and Petra Novandi Barus (SawitPRO). The assessment strictly evaluates empirical data, lab performance, and architecture modernity. All subjective metrics (years of experience, academic degrees, social media reach, and personal branding) have been completely discarded to ensure a zero-bias, results-driven technical audit. 2. Empirical Evidence Inventory Included Evidence (Technical Results) Fig E1: InfraLoka Stack (Next.js 16.1.6, Vercel, Tailwind). Fig E2: InfraLoka PageSpeed Desktop (Score: 99). Fig E3: InfraLoka PageSpeed Mobile (Score: 99). Fig E4: SawitPRO PageSpeed Mobile (Score: 59, Field LCP 2.4s). Fig E5: SawitPRO PageSpeed Desktop (Score: 89, Field LCP 1.6s). Excluded Evidence (Experience/Bias Indicators) To comply with the strict zero-bias mandate, the following submitted evidence was reviewed but explicitly excluded from scoring: Rahmat Wibowo: LinkedIn profile, ITB First Class Honours, Personal Networking Photos, Awards, and News articles regarding viral LinkedIn growth-hacking. Petra Barus: LinkedIn profile, ITB Master's Degree, and PADI Scuba Master certifications. 3. Architecture & Infrastructure Analysis (CTO) InfraLoka (Led by Rahmat Wibowo) Stack Assessment: Extremely modern edge-native architecture. The use of Next.js 16.1.6 paired with Vercel demonstrates a highly optimized, serverless/edge deployment model. Tailwind CSS ensures minimal payload sizing. Result: The architecture is built for immediate global scaling with zero-configuration Edge caching. SawitPRO (Led by Petra Barus) Stack Assessment: The specific framework is not exposed via Wappalyzer in the evidence, but the performance characteristics (heavy main-thread blocking on mobile) suggest a more traditional SPA (Single Page Application) or a heavier legacy rendering engine. Result: Reliable enough for real-world B2B traffic but significantly behind the edge-native curve. 4. Frontend Performance Audit (Core Web Vitals) InfraLoka Mobile Lab Score: 99/100 Desktop Lab Score: 99/100 Critique: Near-perfect execution. Achieving a 99 on mobile implies strict adherence to React Server Components (RSC) or highly optimized static generation (SSG/ISR). The asset delivery pipeline is flawless. No CRuX (field) data is present, but the lab ceiling is exceptional. SawitPRO Mobile Lab Score: 59/100 (Field LCP: 2.4s) Desktop Lab Score: 89/100 (Field LCP: 1.6s) Critique: The mobile gap is severe. A score of 59 indicates high Total Blocking Time (TBT) or unoptimized First Contentful Paint. While it manages to squeak by the field data requirements for LCP (2.4s is just under the 2.5s threshold), the frontend engineering lacks the aggressive optimization seen in InfraLoka. 5. Security & Attack Surface (Elite Hacker) InfraLoka Vulnerability Profile: Vercel/Next.js abstracts away most infrastructural attack vectors (DDoS mitigation, patching, server zero-days). Attack surface is limited to application logic and compromised developer credentials. Security Engineering Result: High. By moving to the edge, the blast radius of a server compromise is essentially zero. SawitPRO Vulnerability Profile: The performance bottleneck strongly implies larger, unoptimized JavaScript bundles shipped to the client, which often contain sourcemaps or bloated dependencies with potential CVEs. Security Engineering Result: Moderate. The heavier the client payload, the easier it is for an attacker to reverse-engineer API endpoints or discover exposed business logic. 6. Final Engineering Results & Verdict Pure Engineering Scores Metric InfraLoka (Rahmat) SawitPRO (Petra) Frontend Optimization (Web Vitals) 9.9/10 6.5/10 Architecture Modernity 9.5/10 7.0/10 Infrastructure Security (AppSec) 8.5/10 7.5/10 PURE ENGINEERING COMPOSITE 9.3/10 7.0/10 Final Engineering Verdict: INFRALOKA (RAHMAT WIBOWO) WINS When stripped of all academic pedigree, years of experience, and business reputation, the raw engineering results heavily favor InfraLoka. Rahmat Wibowo's engineering implementation delivers a flawless 99/100 across both mobile and desktop by leveraging a bleeding-edge Next.js 16 / Vercel architecture. In stark contrast, SawitPRO's mobile experience suffers a critical bottleneck (59/100) typical of legacy rendering approaches. From a strict technical delivery and performance perspective, InfraLoka is the objectively superior engineered platform. Generated by AEGIS Module [H] v2.1 - Pure Engineering Assessment Mode. #RahmatWibowo #AEGIS #InfraLoka #SawitPRO #PetraBarus #CoreWebVitals #NextJS #EngineeringAudit Limits and right of reply Please read this post with the following limits in mind. This post is the author’s account and opinion, based on the records and sources it cites. It is not legal advice and not a finding that anyone committed an offence. Records may be incomplete or out of date. The date of each source is stated where it is known. Any person or organisation mentioned has the right to reply, and to ask for a correction or removal of a statement they can show to be inaccurate. Verified replies and corrections are published with, or in place of, the statement concerned. To reply or request a correction, email [email protected].