# Made by Aris: full article text > Every blog post by Aris Setiawan, as plain text. The short index is at https://madebyaris.com/llms.txt. --- ## Can a 1 GB VPS serve a million WordPress requests a minute? URL: https://madebyaris.com/blog/1-million-wordpress-requests-1gb-vps Published: 2026-11-12. Updated: 2026-11-12. ### Summary I wanted to know whether one small WordPress server could handle 1,000,000 requests per minute. The server was an UpCloud VPS with one vCPU and 1 GB of RAM, running Nginx, PHP 8.4, MariaDB and Valkey, with the finished HTML pages cached in RAM. Benchmarks run on the server itself said yes. It answered 1,000,000 HTTPS requests in 55.8 seconds, which works out to about 1,075,000 per minute. Real traffic from Loader.io said yes too, for a small page. The best external run was 1,034,655 requests in one minute with zero errors, an average response of 137 ms and a maximum of 792 ms, with Loader.io ramping from 0 to 5,000 clients. For the full 25 KB homepage, the best clean run was 271,412 requests in one minute. Most of the gap came from four things: the memory each open HTTPS connection costs, an Nginx setting I had added that made memory use worse, Cloudflare’s DDoS protection blocking the test when I put Cloudflare in front, and the fact that a benchmark on the same machine never touches the network. ### The test server Item | Value | Provider and location | UpCloud, Chicago | CPU | 1 vCPU, AMD EPYC 9575F (KVM) | RAM | 856 MiB usable (1 GB plan), plus a 2 GB swap file I added | Disk | 25 GB | OS and kernel | CentOS Stream 10, Linux 6.12 | Web server | Nginx 1.26.3 with OpenSSL 3.5 | PHP | PHP 8.4.27 FPM with OPcache and the tracing JIT | Database and object cache | MariaDB 10.11, Valkey 8.1 over a Unix socket | WordPress | WordPress 7.1.4, Ollie 1.6.6 block theme, Redis Object Cache plugin | The test site was testwp.madebyaris.com: a Gutenberg landing page, four inner pages, three blog posts, and a plain-text page at /lite/ made for low-bandwidth testing. ### How the server was set up #### Kernel and network The defaults on a small VPS are sized for light traffic, so I raised the connection queues and file limits and switched TCP to BBR: ``` net.core.somaxconn = 65535 net.ipv4.tcp_max_syn_backlog = 65535 net.core.netdev_max_backlog = 65535 net.core.default_qdisc = fq net.ipv4.tcp_congestion_control = bbr net.ipv4.tcp_fastopen = 3 net.ipv4.tcp_tw_reuse = 1 net.ipv4.ip_local_port_range = 1024 65535 net.ipv4.tcp_mem = 32768 49152 65536 net.ipv4.tcp_max_orphans = 65536 fs.file-max = 2097152 vm.swappiness = 10 ``` Nginx runs one worker (one CPU) with worker_connections 65535, reuseport, a listen backlog of 65535, and a file limit of 262,144. The kernel TLS module is loaded so Nginx can hand encryption to the kernel. HTTP/2 and HTTP/3 are on. #### Two layers of page cache in RAM A 192 MB tmpfs (a RAM disk) holds two caches: - A small must-use plugin writes every anonymous page view to the RAM disk as index.html, plus a pre-compressed index.html.gz. Nginx serves those files directly with try_files, gzip_static and sendfile, so a cached request never reaches PHP. - Behind that sits the Nginx FastCGI cache, also on the RAM disk, with fastcgi_cache_lock and fastcgi_cache_use_stale so a burst of misses produces one PHP render instead of hundreds. Logged-in users, WooCommerce cart cookies, query strings, wp-admin, wp-login.php and the REST API skip both caches. The plugin clears both when a post, menu, comment or theme changes. #### PHP and one SELinux surprise PHP-FPM uses OPcache (96 MB) and the tracing JIT (opcache.jit = 1255, 32 MB buffer). With SELinux enforcing, the first page request failed with “502 Bad Gateway”. The PHP workers were crashing with a segmentation fault, because SELinux blocks a web server process from creating executable memory, which the JIT needs. Setting setsebool -P httpd_execmem 1 fixed it while keeping SELinux enforcing. If you enable the JIT on RHEL, CentOS or Fedora and get unexplained 502s, check the audit log for execmem denials. ### Benchmarks on the server itself These ran on the VPS against its own address, with the load tool sharing the single CPU. Test | Result | 1,000,000 HTTPS requests, keep-alive, 200 connections, 12 KB gzipped page | 55.8 s, 17,922 requests/s, 0 failed, median 11 ms, 99th percentile 19 ms | Same, Ollie homepage (25.9 KB gzipped), 200,000 requests | 15,421 requests/s, 0 failed | /lite/ page (0.7 KB), new connection per request, 200,000 requests | 11,892 requests/s, 0 failed | Uncached dynamic page (logged-in cookie), 8 at a time | 27 requests/s, median 286 ms | The first row is the “1 million a minute” number. It is real, but it measures Nginx serving a file from RAM to a client on the same machine. Traffic never crosses the network card, there is no internet latency or packet loss, and every client finishes its connection almost instantly. The external tests below behaved very differently. The last row is worth keeping in mind too. Without the page cache, this server renders about 27 WordPress pages per second. ### Load tests from Loader.io Loader.io sends traffic from Amazon servers. Most runs used its “clients per second” mode: a set number of new clients each second for one minute, each making requests over its own connection. Run | Setup | Successful | Errors | Average response | Data received | 1 | Homepage, 10,000 clients/s, direct to VPS | 716 | 4,752 network | 14,206 ms | 37.5 MB (aborted) | 2 | Homepage, 1,500 clients/s, direct, HTTP | 89,998 | 0 | 28 ms | 2.19 GB | 3 | Homepage, 2,500 clients/s, direct, HTTP | 147,445 | 0 | 29 ms | 3.59 GB | 4 | Homepage, 10,000 clients/s, through Cloudflare, HTTPS | 48,049 | 201,389 HTTP 403 | 1,141 ms | 2.46 GB (aborted) | 5 | /lite/, 10,000 clients/s, direct | 94,086 | 7,018 network | 9,662 ms | 98.6 MB | 6 | /lite/, 10,000 clients/s, direct, after first fixes | 46,114 | 16,686 network | 15,118 ms | 48.3 MB | 7 | /lite/, 5,000 clients/s, direct | 299,799 | 0 | 1,063 ms | 314 MB | 8 | Homepage, ramp from 0 to 2,000 concurrent clients | 271,412 | 0 | 209 ms | 6.61 GB | 9 | 0 to 5,000 clients over 1 minute | 1,034,655 | 0 | 137 ms | 1.06 GB | Run 9 is the headline number: 1,034,655 requests in one minute with zero errors, an average response of 137 ms and a maximum of 792 ms. The Loader.io result summary does not show which URL it hit, but 1.06 GB over 1,034,655 responses is about 1 KB each, which fits the small /lite/ page rather than the homepage. During the run, htop on the VPS showed 416 MB of 857 MB RAM and 179 MB of swap in use. For the real homepage, run 8 is the best clean result among these runs, at about 270,000 requests per minute with no errors. Run 7 still had a stall in its first 20 seconds, when response times climbed to about 15 seconds before settling well under one second. The rest of this section is about what broke in the other runs. #### Run 1: more traffic than the server could hold 10,000 new clients per second at 25 KB each is about 257 MB/s, or roughly 2 Gbps of outgoing traffic. While connections waited, the kernel spent 61 seconds under TCP memory pressure (it had auto-sized its buffer limit to about 68 MB on this 1 GB machine), and the Nginx worker grew to about 1 GB, most of it pushed into swap. Response times climbed to 18 seconds and Loader.io aborted. At the time I measured outgoing bandwidth with parallel uploads to Cloudflare’s speed test and got about 550 Mbps. Run 8 later averaged 6.61 GB in 60 seconds, about 880 Mbps, so that upload test underestimated what the VPS can send. In either case, 2 Gbps was out of reach. #### Run 4: Cloudflare blocked the test With the DNS record switched to proxied and a cache rule for the site, Cloudflare served the homepage from its edge cache, with the fastest responses at 6 ms. Around five seconds in, Cloudflare’s HTTP DDoS protection classified Loader.io as an attack and returned 403 for the rest of the run. Cloudflare’s analytics showed the rule source as l7ddos, and only 6 requests reached the VPS. The zone already had a WAF custom rule that skips security checks for the loader.io user agent. That rule does not cover the DDoS protection. On the Free plan, the HTTP DDoS ruleset allows one override, and it applies to every request in the zone, so loosening it for a test also loosens it for every other subdomain. I chose not to, and tested directly against the VPS instead. #### Runs 5 and 6: the Nginx worker ran out of memory The 0.7 KB /lite/ page should have removed the bandwidth problem. It did, but the server still ran out of memory. After run 6 the Nginx worker held about 840 MB (355 MB in RAM and 480 MB in swap). A once-a-second memory recorder in a later run showed how fast this happens: the worker went from 34 MB to 872 MB within ten seconds of Loader.io starting, and for those seconds Nginx could not answer a local status check within one second. The request log showed Nginx itself was never slow: every one of 387,524 logged Loader.io requests took 0 ms to process. The time went to waiting for memory pages to come back from disk. I found two causes. The first was a setting I had added: aio threads with directio. For files that already live in RAM it adds nothing, and it made Nginx allocate extra buffers per request. With 5,000 keep-alive connections, removing it lowered the worker’s peak memory from 63 MB to 35 MB and raised throughput from about 25,000 to 31,000 requests per second. The second was HTTPS. With the same 5,000 keep-alive connections, the Nginx worker stayed at 35 MB over plain HTTP and reached 315 MB over HTTPS. That is about 56 KB of encryption state per open connection. Loader.io keeps around 20,000 connections open, which needs about 1.1 GB over HTTPS on a machine with 856 MB of RAM. Holding 20,000 idle HTTP keep-alive connections, for comparison, added only 9 MB to the worker. I did not log the protocol of runs 5 and 6, but their memory profile matched the HTTPS reproduction, and the HTTP reproduction never came close. Before finding the HTTPS cause I also tried two other ideas, a shorter keepalive_timeout (65 down to 15 seconds) and telling glibc to return freed memory sooner. The malloc change made no measurable difference, so I removed it. #### What Loader.io’s traffic looked like A temporary access log during run 7 and the run before it showed: - about 20,000 connections open at the same time, from 5 Amazon IP addresses - an average of 7.6 requests per connection, a maximum of 498, and no pipelining - 143-byte requests, all answered with status 200 - up to 11,002 requests per second at Nginx in a single second #### Connections that never arrived In run 6, the kernel counted about 45,600 new connections from Loader.io, while Loader.io reported about 62,800 attempts. The kernel’s listen queue never overflowed and the network card dropped no packets, so roughly 17,000 attempts never reached the server’s TCP stack. I could not tell whether they were lost in the provider’s network or never sent because Loader.io’s own client was saturated. The 15-second average response time fits clients retrying lost connection attempts, but this one stays unresolved. ### Making the homepage lighter Loader.io only downloads the HTML, but a real visitor downloads everything. I measured every file the homepage loads and cut the weight without changing how it looks. | Before | After | HTML (gzipped) | 25.1 KB | 15.6 KB | HTML plus every CSS, font and image file | 852 KB | 287 KB | Images loaded before scrolling | 19 | 1 | Font file (Mona Sans) | 164 KB | 47 KB | JavaScript | 20 KB | none | What changed: - Each image was resized to the size it is displayed at. The theme’s six avatar images were 1001 × 1000 px and display at 60 to 76 px; at 160 × 160 they went from 330 KB to 20 KB in total. The photo behind the stats banner sits under a 90% colour overlay, so it took heavier compression (38 KB to 17 KB). - Only the hero image loads immediately. The other 18 images get loading="lazy", and blog card images get a sizes hint so desktops pick the 768 px version instead of the full one. - Mona Sans is a variable font with weight and width axes. No page used the condensed or expanded widths, so I fixed the width at 100% with fonttools varLib.instancer and subset it to Latin characters with pyftsubset, keeping weights 200 to 900. - WordPress inlined about 40 KB of block CSS into every page. Setting the styles_inline_size_limit filter to 0 moved it into separate, cacheable CSS files. A first visit makes about 30 small extra CSS requests, which HTTP/2 handles well. - The emoji detection script went away, and so did the mobile hamburger menu, which loaded 42 KB of the Interactivity API. With five links, a menu that wraps onto a second line looks fine on a phone and needs no JavaScript. Two of these edits change files inside the Ollie theme (images and the font), so a theme update would bring the heavy versions back. A child theme is the better long-term home for them. ### Conclusions On this 1 vCPU, 1 GB VPS, an external Loader.io run reached 1,034,655 requests in one minute with zero errors for a small page (about 1 KB per response). For a real 25 KB homepage, the best clean external result among the runs in this post was 271,412 requests in one minute. So the answer to the title is yes, at least for a small cached page. What limited this machine, in the order I ran into it: - Outgoing bandwidth, for the full homepage at 10,000 new clients per second. - RAM per open connection, especially over HTTPS at about 56 KB each. With 856 MB of RAM, a few thousand concurrent HTTPS clients are safe and 20,000 are not. - My own aio threads setting, which made the memory problem worse and lowered throughput for files served from RAM. - Cloudflare’s DDoS protection, which blocks a load test that looks like an attack and cannot be loosened for one subdomain on the Free plan. To push the full homepage further on a machine this size, I would put a CDN’s edge cache in front, on a plan where DDoS sensitivity can be adjusted for test traffic, or give the origin more RAM and CPU if it must terminate HTTPS itself. I would also always run load tests from outside the server and check RAM, swap and the Nginx status page during the run, because a benchmark on the server itself hides exactly the problems that showed up here. ### Appendix: the Nginx pieces that mattered ``` worker_processes auto; worker_rlimit_nofile 262144; events { worker_connections 65535; use epoll; multi_accept on; } http { sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 15; open_file_cache max=50000 inactive=60s; open_file_cache_valid 30s; gzip_static on; ssl_conf_command Options KTLS; fastcgi_cache_path /var/cache/wp-ram/fastcgi levels=1:2 keys_zone=WORDPRESS:32m max_size=96m inactive=60m use_temp_path=off; server { listen 80 reuseport backlog=65535; listen 443 ssl reuseport backlog=65535; http2 on; location / { try_files $static_cache_root$cache_uri/index.html $uri $uri/ /index.php?$args; } } } ``` $static_cache_root comes from a map that points to the RAM-disk cache only for anonymous GET requests without a query string, and to a path that never exists otherwise, so those requests fall through to PHP. --- ## Fastify vs Express: mana yang dipilih untuk API Node.js baru URL: https://madebyaris.com/blog/fastify-vs-express-untuk-api-baru Published: 2026-11-08. Updated: 2026-11-08. Untuk API Node.js baru, pilih Fastify kalau kamu ingin input tervalidasi, logging bawaan, dan struktur yang jelas saat API tumbuh. Pilih Express kalau API-nya kecil, tim kamu sudah menguasainya, atau kamu bergantung pada middleware yang hanya ada untuk Express. Keduanya layak dipakai, dan pilihan di antara keduanya tidak sepenting yang sering ditulis. ### Perbedaan yang benar-benar terasa Perbandingan ini mengacu pada Fastify 5 dan Express 5, versi mayor saat ini. | Fastify | Express | Validasi input | Bawaan. Kamu mendeskripsikan request dengan JSON Schema dan Fastify memvalidasinya sebelum handler jalan. | Tidak termasuk. Kamu menambah library seperti Zod, Joi, atau express-validator dan menyambungkannya sendiri. | Logging | Pino sudah bawaan, log terstruktur tinggal diaktifkan. | Tidak termasuk. Kamu menambah morgan atau pino-http. | Struktur | Plugin dengan enkapsulasi. Satu plugin bisa menambah route, hook, dan decorator tanpa bocor ke bagian lain aplikasi. | Rantai middleware dan router. Sederhana, tetapi gampang berubah jadi kusut. | Handler async | Handler async berjalan secara native. | Express 5 meneruskan promise yang ditolak dari handler async ke error handler. | TypeScript | Tipe sudah ada di dalam paket. | Tipe datang dari paket terpisah, @types/express. | Ekosistem | Plugin banyak, usianya lebih muda. | Ekosistem terbesar di Node.js, dengan contoh dan jawaban paling banyak. | ### Benchmark kecil dari saya Saya menulis dua route yang sama di kedua framework dan mengujinya dengan autocannon: GET yang mengembalikan objek JSON kecil, dan POST yang memvalidasi body berisi dua field. Fastify memakai JSON Schema. Express memakai pengecekan yang ditulis manual. Route | Fastify 5.12.8 | Express 5.3.0 | GET /json | sekitar 101.000 request per detik | sekitar 40.000 request per detik | POST /echo dengan validasi | sekitar 68.000 request per detik | sekitar 35.000 request per detik | Angka ini adalah median dari tiga kali uji 8 detik dengan 100 koneksi, di Apple M4 dengan Node.js 26.13.0, sementara aplikasi lain terbuka di mesin yang sama. Uji pertama memberi angka absolut yang berbeda, jadi baca hasilnya sebagai “Fastify melayani sekitar 1,5 sampai 2,5 kali lebih banyak request per detik pada route ini”, tanpa terlalu serius pada angka persisnya. Benchmark hello-world hanya sedikit bercerita tentang API kamu. Di aplikasi nyata, database dan panggilan ke layanan lain biasanya memakan waktu jauh lebih lama daripada framework. Pilih berdasarkan struktur dan kecocokan dengan tim dulu, dan ukur route kamu sendiri sebelum memutuskan bahwa kecepatan adalah alasan pindah. ### Kapan saya memilih Express - API kecil dan akan tetap kecil. - Tim sudah menguasai Express dan merilis dengannya tiap minggu. - Kamu bergantung pada middleware atau library yang hanya mendukung Express. - Kamu butuh paling banyak tutorial dan jawaban untuk anggota tim baru. ### Kapan saya memilih Fastify - Kamu ingin validasi request menjadi bagian dari framework. - Kamu ingin log terstruktur sejak hari pertama. - API akan tumbuh, dan kamu ingin plugin memisahkan route dari logika bersama. - Throughput dan latensi penting, misalnya API di belakang front end yang sibuk. ### Pindah dari Express ke Fastify tanpa menulis ulang Kamu tidak perlu berhenti dan menulis ulang semuanya. Jalur yang aman adalah memindahkan satu route sekali waktu sambil menjaga test tetap lulus. Fastify punya plugin resmi, @fastify/express, yang membuat middleware Express bisa berjalan di dalam aplikasi Fastify, dan itu membantu selama masa pindah. Mulai dari route yang lambat atau validasinya lemah, karena di situ manfaatnya paling besar. ### Pilihan x.com X membangun ulang web app-nya di atas React, Vite, Fastify, dan TypeScript, menurut laporan teknik X yang diberitakan iTechPost pada 5 November 2026. Pilihan satu perusahaan besar tidak menentukan apa yang tepat untuk API kamu, tetapi ini menunjukkan Fastify tahan di skala yang sangat besar. ### Langkah berikutnya Kalau kamu ingin API baru di atas Fastify, atau aplikasi Express dipindahkan, lihat jasa Fastify. Kalau API sudah cepat tetapi database di belakangnya lambat, lihat jasa optimasi database. Versi bahasa Inggris tulisan ini ada di Fastify vs Express. Atau kirim API kamu lewat halaman kontak. Saya balas dalam 24 jam. --- ## Clean code adalah: arti, contoh, dan cara menerapkannya di tim dan AI agent URL: https://madebyaris.com/blog/apa-itu-clean-code Published: 2026-11-08. Updated: 2026-11-08. Clean code adalah kode yang mudah dibaca dan mudah diubah tanpa efek samping yang mengejutkan. Namanya jelas, strukturnya bisa ditebak, dan developer lain bisa memahami cara kerjanya tanpa membongkar logika yang berbelit. ### Tanda kode yang berantakan - Fungsi yang panjangnya puluhan baris dan mengerjakan beberapa hal sekaligus. - Nama variabel seperti data, temp, atau flag yang menyembunyikan maksudnya. - Kondisi bersarang dalam yang memaksa pembaca melacak banyak cabang. - Logika yang disalin ke banyak tempat, bukan dipakai bersama. - File yang bergantung erat pada struktur data di lapisan lain. ### Praktik yang paling berpengaruh Kamu tidak perlu menulis ulang seluruh arsitektur. Beberapa kebiasaan yang konsisten sudah memperbaiki kode di pull request harian. - Fungsi kecil dan fokus. Satu fungsi mengerjakan satu hal. Kalau sebuah fungsi membaca input, mengecek izin, menulis ke database, dan menyusun email, pecah menjadi beberapa fungsi. - Nama yang menjelaskan maksud. Kalau sebuah variabel butuh komentar di sebelahnya, ganti namanya. - Struktur folder per fitur. File yang berkaitan diletakkan berdekatan, sehingga mencari dan mengubah kode lebih cepat. - Test dan lint. Pengecekan otomatis menangkap kesalahan sebelum review. ### Contoh sebelum dan sesudah Fungsi berikut menghitung diskon pesanan. Versi pertama sulit dibaca. ``` function calc(d: any) { if (d.s === 'active') { if (d.t > 100) { return d.t * 0.9; } } return d.t; } ``` Singkatan menyembunyikan maksud, dan kondisi bersarang menambah beban pikiran. Versi yang dirapikan: ``` interface Order { status: 'active' | 'inactive'; totalAmount: number; } const MINIMUM_DISCOUNT_THRESHOLD = 100; const DISCOUNT_RATE = 0.1; function calculateDiscountedTotal(order: Order): number { const isEligible = order.status === 'active' && order.totalAmount > MINIMUM_DISCOUNT_THRESHOLD; if (!isEligible) { return order.totalAmount; } return order.totalAmount * (1 - DISCOUNT_RATE); } ``` Nama, tipe, dan konstanta yang jelas membuat aturan bisnisnya terbaca sekilas. ### Clean code untuk AI agent seperti Cursor Alat coding AI memprediksi kode berdasarkan konteks di sekitarnya. Di repo dengan penamaan konsisten, tipe yang jelas, dan folder yang rapi, agent menghasilkan kode yang lebih tepat. Di repo yang penuh kode mati dan pola yang bertentangan, agent meniru kekacauan itu. - Tulis konvensi di AGENTS.md dan aturan proyek, misalnya pola komponen yang dipakai dan library yang tidak boleh dipakai lagi. Lihat juga aturan proyek untuk Cursor (bahasa Inggris). - Pasang lint, tipe, dan test sebagai pagar pengaman, baik kodenya ditulis orang maupun agent. - Pakai checklist review untuk kode hasil AI (bahasa Inggris) sebelum menggabungkan pull request. ### Kesalahan yang sering terjadi - Mengejar kesempurnaan dan merapikan semua kode lama sebelum merilis fitur, sampai rilis tertunda. - Terlalu banyak abstraksi, misalnya memecah operasi tiga baris menjadi beberapa pola desain. - Menganggap satu baris yang padat sebagai kode yang bersih. Kode lebih sering dibaca daripada ditulis, jadi keterbacaan lebih penting. ### Pertanyaan yang sering muncul Apakah clean code memperlambat pengiriman fitur? Di sprint pertama, menulis test dan memperbaiki nama memang butuh sedikit waktu lebih. Setelah beberapa minggu, tim menghabiskan lebih sedikit waktu mengejar bug dan mengurai efek samping. Perlukah menulis ulang sistem lama dari nol? Penulisan ulang total jarang berhasil karena membuang penanganan kasus khusus yang sudah dikumpulkan bertahun-tahun. Lebih aman merapikan bertahap: terapkan konvensi di area yang aktif dikerjakan, isolasi modul lama di balik antarmuka yang jelas, dan tambahkan test sebelum mengubah logikanya. Apa satu aturan terbaik untuk sehari-hari? Tinggalkan kode lebih bersih daripada saat kamu menemukannya. Setiap kali menyentuh sebuah file, perbaiki satu hal kecil. ### Langkah berikutnya Kalau codebase kamu sudah penuh pola campur aduk dari penulisan cepat atau alat AI, lihat jasa clean code untuk tim dan AI agent. Untuk perbaikan yang terfokus, lihat juga memperbaiki kode hasil AI (bahasa Inggris). Atau kirim repo kamu lewat halaman kontak. Saya balas dalam 24 jam. --- ## Vite adalah: apa itu Vite dan kapan kamu perlu memakainya URL: https://madebyaris.com/blog/apa-itu-vite Published: 2026-11-08. Updated: 2026-11-08. Vite adalah build tool dan dev server untuk aplikasi web modern. Saat kamu menjalankan aplikasi di mode pengembangan, Vite menyajikan file lewat ES modules bawaan browser, jadi server menyala cepat dan perubahan kode muncul hampir seketika. Untuk produksi, Vite membundel kode menjadi file yang siap di-deploy. ### Apa bedanya Vite dengan Create React App dan Webpack Create React App dan setup Webpack lama membundel seluruh aplikasi sebelum dev server bisa dipakai, jadi waktu tunggu naik seiring aplikasi membesar. Vite melewati langkah itu saat pengembangan. Selain itu, tim React sudah menyatakan Create React App deprecated, sehingga proyek baru jarang punya alasan memakainya. | Create React App / Webpack lama | Vite | Dev server | Membundel dulu, makin lambat saat aplikasi besar | Menyajikan ES modules, menyala cepat | Konfigurasi | Tersembunyi atau perlu eject | File vite.config yang ringkas | Status | Create React App sudah deprecated | Aktif dikembangkan | Test | Biasanya Jest | Vitest cocok dipakai di sebelahnya | ### Kapan Vite cocok, dan kapan Next.js lebih cocok - Pilih Vite untuk aplikasi di balik login, dashboard, dan alat internal yang tidak bergantung pada trafik dari Google. - Pilih Next.js untuk situs yang butuh server rendering, SEO kuat, dan halaman yang harus terbaca mesin pencari. - Keduanya bisa dipakai di perusahaan yang sama, masing-masing untuk kebutuhannya. ### Langkah umum pindah dari Create React App ke Vite - Pasang vite dan @vitejs/plugin-react, lalu buat vite.config. - Pindahkan index.html ke root proyek dan tambahkan tag script bertipe module yang menunjuk ke file entry. - Ganti environment variable berawalan REACT_APP_ menjadi VITE_, dan baca lewat import.meta.env. - Perbarui script start dan build di package.json. - Jalankan test. Kalau memakai Jest, kamu bisa tetap memakainya atau pindah ke Vitest. - Bandingkan hasil build dengan versi lama sebelum rilis. Hal yang paling sering perlu perhatian adalah environment variable, import file non-JavaScript, dan langkah build khusus. Lakukan migrasi di branch terpisah supaya aplikasi yang sedang live tidak terganggu. ### Siapa yang memakai Vite Web app baru x.com dilaporkan dibangun di atas React, Vite, Fastify, dan TypeScript, menurut laporan teknik X yang diberitakan iTechPost pada 5 November 2026. Satu perusahaan besar memilih sebuah alat tidak otomatis berarti cocok untuk proyek kamu, tetapi ini menunjukkan Vite dipakai di aplikasi berskala sangat besar. ### Langkah berikutnya Kalau build kamu lambat atau setup lamanya tidak ada yang berani sentuh, lihat jasa migrasi dan pengembangan Vite. Kalau masalahnya ada di aplikasi React yang lambat, lihat jasa optimasi React. Atau kirim aplikasinya lewat halaman kontak. Saya balas dalam 24 jam. --- ## Fastify vs Express: which one for a new Node.js API URL: https://madebyaris.com/blog/fastify-vs-express Published: 2026-11-08. Updated: 2026-11-10. For a new Node.js API, pick Fastify if you want validated input, built-in logging, and a clear structure as the API grows. Pick Express if the API is small, your team already knows it, or you depend on middleware that only exists for Express. Both are fine. The choice matters less than most comparison posts claim. ### What actually differs Here are the differences that change how you write and run an API. I checked these against Fastify 5 and Express 5, the current major versions. | Fastify | Express | Input validation | Built in. You describe the request with JSON Schema and Fastify validates it before your handler runs. | Not included. You add a library such as Zod, Joi, or express-validator and wire it in yourself. | Logging | Pino is built in and structured logs are one option away. | Not included. You add morgan or pino-http. | Structure | Plugins with encapsulation. A plugin can add routes, hooks, and decorators without leaking into the rest of the app. | A chain of middleware and routers. Simple, and easy to let grow into a tangle. | Async handlers | Async handlers work natively. | Express 5 passes a rejected promise from an async handler to your error handler. | TypeScript | Types ship with the package. | Types come from the separate @types/express package. | Ecosystem | Large plugin ecosystem, younger. | Largest ecosystem in Node.js, and the most examples and answers online. | ### A small benchmark I ran I wrote the same two routes in both frameworks and load-tested them with autocannon: a GET that returns a small JSON object, and a POST that validates a body with two fields. Fastify used a JSON Schema. Express used a hand-written check. Route | Fastify 5.12.8 | Express 5.3.0 | GET /json | about 101,000 requests per second | about 40,000 requests per second | POST /echo with validation | about 68,000 requests per second | about 35,000 requests per second | These are the median of three 8-second runs at 100 connections, on an Apple M4 with Node.js 26.13.0, with other apps open on the same machine. A first trial gave different absolute numbers, so read the result as “Fastify served roughly 1.5 to 2.5 times more requests per second on these routes”, without taking the exact figures too seriously. A hello-world benchmark tells you little about your own API. In a real app, the database and external calls usually take far more time than the framework does. Pick on structure and team fit first, and measure your own routes before you decide that speed is the reason to switch. ### When I would pick Express - The API is small and will stay small. - Your team already knows Express well and ships with it every week. - You rely on a middleware or library that only supports Express. - You need the widest choice of tutorials and answers for new team members. ### When I would pick Fastify - You want request validation to be part of the framework. - You want structured logs from day one. - The API will grow, and you want plugins to keep routes and shared logic separate. - Throughput and latency matter, for example an API that sits behind a busy front end. ### Moving from Express to Fastify without a rewrite You do not need to stop and rewrite. A safe path is to move one route at a time and keep the tests passing. Fastify has an official plugin, @fastify/express, that lets Express middleware run inside a Fastify app, which helps while you move. Start with the routes that are slow or poorly validated, since those gain the most. ### What x.com chose X rebuilt its web app on React, Vite, Fastify, and TypeScript, according to its engineering report as covered by iTechPost on 5 November 2026. One large company picking a tool does not decide what is right for your API, but it shows that Fastify holds up at a very large scale. ### Next steps If you want a new API built on Fastify, or an Express app moved over, see my Fastify development service. If the API is fast and the database behind it is not, see database optimization. Or send me the API through the contact page. I reply within 24 hours. --- ## How I improved RankMySEO sign-in performance URL: https://madebyaris.com/blog/how-we-made-a-dashboard-fast-on-slow-networks Published: 2026-11-06. Updated: 2026-11-06. RankMySEO is a rank tracker I build and run. Many of its users open the dashboard on a phone, on a mobile network in Indonesia that is often busy. In a lab test I measured what that feels like, fixed what was slow, and measured again. On Chrome Slow 4G with an empty cache, sign-in first contentful paint (FCP) fell from 7.4 seconds to 1.6 seconds. The page downloads 295 KB instead of 1,368 KB. This post covers the method, each change, the restructure that came first, and one change I decided against. These figures are a lab before-and-after on one setup. They are not a real-world guarantee. ### The setup The stack is a React single-page app built with Vite, served from Cloudflare Workers static assets. The API is a separate Node service. The marketing site is prerendered HTML that hydrates later. I measured production builds served with compression, under these conditions: - Network: Slow 4G through the DevTools Protocol: 150 ms latency, 1.6 Mbps down, 750 Kbps up. - Cache: disabled. - Metrics: first contentful paint, largest contentful paint, JavaScript transferred, and total bytes, read from the Performance API after load. I alternated runs between the old and new builds on the same machine and connection. One lesson from that: run the measurements one at a time. When I fired navigations in parallel, they raced each other and produced numbers that meant nothing. ### What the baseline showed Build | First paint (FCP) | JavaScript | Total | Customer app sign-in | 7.4 s | 926 KB | 1,368 KB | Admin sign-in | 2.8 s | 171 KB | 420 KB | Marketing home | 2.2 s | 0 KB before paint | 108 KB | The marketing site was already fine. It ships prerendered HTML and adds its script after the first frame. The customer app was the problem. Every route was a static import in App.tsx. The sign-in page shipped all of the app code: a single 3.2 MB entry chunk. ### The changes #### Load each route when it opens I turned every page import into React.lazy, including the app shell and the site layout. The sign-in page no longer pulls either of them. The interesting part is where the Suspense boundaries go. A single boundary at the root would blank the whole screen on every navigation. Instead, each layout wraps its own : ``` export function RouteSuspense({ children }: { children: ReactNode }) { return ( }> {children} ) } ``` The shell, the site layout, and the section layouts each render . When you change screens, the navigation and the site switcher stay put, and only the content area waits. The entry chunk went from 3.2 MB to 373 KB, or 117 KB compressed. Lazy routes bring one new failure: a tab opened before a deploy asks for chunk names that no longer exist. Vite fires vite:preloadError when that happens. I reload once, guarded by sessionStorage, so a down network cannot cause a reload loop. #### Defer what is only decoration A source-map breakdown of the remaining entry showed the animation library at about 450 KB of source. A decorative grid behind the sign-in form pulled it in. I lazy-loaded that component with an empty fallback, so the form paints first. #### Shrink images to their display size The logo was a 512 px PNG, 205 KB, shown at 32 px. A 96 px WebP is 948 bytes and looks identical. The sign-in photo got a WebP srcSet (20 KB at 640 px, 47 KB at 1200 px) with fetchPriority="low". It does not compete with code and CSS for bandwidth. #### Share identical in-flight requests On load, the shell and the home page both asked for the account and the site list together. I changed the fetch helper so plain GETs for the same path share one in-flight promise. Each caller gets its own structuredClone of the result. Nothing is cached after the request settles, so no data goes stale, and writes are never shared. A unit test asserts both behaviours. #### Cache hashed files for a year Production was sending Cache-Control: public, max-age=0, must-revalidate for hashed build files. Every repeat visit revalidated each file, at one round trip each. On Slow 4G, that is at least 150 ms per file. One rule in each Worker _headers file fixed it: ``` /assets/* Cache-Control: public, max-age=31536000, immutable ``` Before shipping it, I confirmed that every file under /assets/ has a content hash in its name. #### Start the bot check with the page Sign-in uses Cloudflare Turnstile. Its script was requested only after the React form mounted, about 6.0 seconds into the slow test. The app Content Security Policy blocks inline scripts. I added a tiny same-origin loader that starts the Turnstile download on /login and /signup only. Now it starts at 0.3 seconds, and the challenge is running while the form is still loading. ### Results Page | Metric | Before | After | Total before | After | Customer sign-in | First paint (FCP) | 7.4 s | 1.6 s | 1,368 KB | 295 KB | Customer sign-in | Largest contentful paint (main image) | 8.5 s | 3.7 s | | | Admin sign-in | First paint (FCP) | 2.8 s | 1.5 s | 420 KB | 228 KB | Again: lab before-and-after on one setup, not a real-world guarantee. ### The restructure that came first None of this would have been a one-day job a week earlier. Before the speed work, I reorganized the codebase: - Folders by domain. The API and shared packages moved into domain folders. The dashboard 164 screen files moved into one folder per navigation area. File names did not change, so search still finds everything. - One source per rule. Plan limits, prices, and paid-plan lists were hand-copied across the API, the dashboard, the admin, and the marketing site. They now read from one shared table. That change surfaced a public comparison page listing a plan with 10 keywords instead of 20. - Fewer, clearer dependencies. Both packages now have zero import cycles, and the platform layer no longer imports from auth. - Less code. About 6,400 lines removed and 4,200 written, including tests that only restated a table. That is what made the lazy-route change mechanical. Every page already had an obvious module to point React.lazy at. ### The upgrade gotcha CI caught I also moved the marketing site from Vite 6 to Vite 8. Its client build dropped from 3.4 seconds to 0.3. CI then failed on its “bundle contains localhost” check. This code: ``` const env = import.meta.env; export const appOrigin = env.VITE_APP_ORIGIN ?? "http://localhost:5174"; ``` worked in Vite 6, where the minifier folded the fallback away. In Vite 8 the aliased import.meta.env became a whole inlined object, and the fallback string stayed in the bundle. The runtime value was still the production origin, but the gate was right to fail. Reading import.meta.env.VITE_APP_ORIGIN directly lets the build replace it, and the fallback drops out. ### Why I did not adopt GraphQL The marketing pages already stream HTML with early data. For the dashboard, the changes above covered the rest. A second API would also have been costly. The REST API has 256 routes and serves customer API keys, MCP clients, and a phone app. Every GraphQL field would need the same plan limits and cost caps as its REST route. A client-side query cache over the existing REST calls is the next step. It gives the part of a client cache I would actually use. The last answer shows at once while it refreshes. ### Takeaways - Measure on a throttled connection, with an empty cache, against production builds. Office Wi-Fi hides all of this. - Put a Suspense boundary at each layout outlet, not only at the root. - Check your cache headers in production. Hashed files that revalidate on every visit cost a round trip each. - Look for decoration in the entry chunk with a source map. Mine was 450 KB of animation code on a login page. - Keep a CI check for the mistakes you have made before. Mine caught a build-tool change on the first try. --- ## What Is PHP? A Plain Introduction for Website Owners URL: https://madebyaris.com/blog/what-is-php Published: 2026-10-27. Updated: 2026-10-27. Your developer says the site “runs on PHP”, your hosting panel has a PHP version dropdown, and a search for “what is PHP” mixes in pages about the Philippine peso. So what is PHP, in plain words, and should you care which version you run? This post is about PHP the programming language. I will keep it practical: what it is, how it turns code into a page, what a PHP file looks like, and how you can run one on your own laptop in a few commands. ### What is PHP, exactly? PHP is a recursive acronym for “PHP: Hypertext Preprocessor”, which is the kind of name only programmers find funny. The PHP manual uses that name. Rasmus Lerdorf created PHP in 1994. In June 1995 he released the source code of “PHP Tools” to the public. The original name was “Personal Home Page Tools”. The PHP history page has the full story. PHP is open source. Current PHP uses the Modified BSD License (PHP License v4), and older releases used PHP License versions 2.01 to 3.01. The PHP license page has the text. Two groups have a formal role. The PHP Group holds the copyright and publishes the license. The PHP Foundation funds and guides core developers. A wider community of contributors does core work as well. ### How does PHP turn code into a page? A browser asks a server for a page. The server runs the PHP code for that page, PHP builds the response, usually HTML, and the server sends that HTML back. The browser never sees the PHP code. It only sees the result, which is why “view source” on a PHP site shows HTML and nothing else. PHP can run in more than one way, and two names come up often: - CLI. The PHP manual says the CLI “is for developing shell applications”. You run a PHP script from a terminal, with no browser involved. - PHP-FPM. The manual calls FPM (FastCGI Process Manager) a primary PHP FastCGI implementation, meant for sites with heavy load. When your host talks about PHP-FPM, this is the part that serves your web pages. A CLI command is the easiest one to try: ``` php -r "echo 2 + 2, PHP_EOL;" ``` ### What is PHP used for? #### Websites and WordPress WordPress runs on PHP. The WordPress requirements recommend PHP 8.3 or later. The same page says WordPress also works with PHP 7.4+, which has reached end of life. So if your site is on WordPress, you already depend on PHP, whether you have opened a PHP file or not. #### Web apps A PHP app can handle logins, forms, carts and admin screens. That is the everyday work behind many business sites: take input, check it, store it, show a page. #### APIs PHP can also serve JSON to a separate front end, such as a Next.js site. For that setup, read PHP API development for Next.js. ### What does a PHP file look like? A PHP file ends in .php, and the PHP code starts with the Hello, " . htmlspecialchars($name) . ".

"; echo "

Today is " . date("j M Y") . ".

"; ``` The server runs this file and sends two paragraphs of HTML to the browser. The htmlspecialchars call is a small habit worth having from day one, because it escapes text before it goes into HTML. ### What is Composer? Composer is a tool for dependency management in PHP. You declare the libraries your project needs, and Composer installs and updates them. It is not a system package manager, so it does not install PHP itself. ``` composer init composer install ``` ### Is PHP still used, and is it safe? Yes, it is still used. PHP is on 69.2% of websites with a known server-side language, per W3Techs on 27 Oct 2026. Safety depends on the version and the code. PHP apps need updates and safe code. ### How do I start with PHP? - Install PHP. The PHP install guide has pages for Linux packages, macOS and Windows. - Check the version with php -v. On 27 Oct 2026, php.net lists 8.5.12 as the latest stable release. - Make a folder with an index.php file, like the sample above. - Run the built-in web server in that folder. - Open localhost:8000 in your browser. ``` mkdir hello-php && cd hello-php php -v php -S localhost:8000 ``` The built-in server is for development only. The PHP manual says not to use it on a public network, so keep it on your laptop. ### How long have I worked with PHP? I have worked with PHP and WordPress since 2013, when I started as a full-stack PHP developer one week after vocational school. Now I also build with JavaScript and Go, but clients still ask me for PHP apps, and I still trust PHP. ### When does PHP fit your project? If your site runs on WordPress, you already use PHP. Learn enough to read a theme file and to know which PHP version your host runs. If you need a content site with an admin area, PHP and WordPress can do that job. If you need a custom web app or an API, PHP can do the job too. Pick it when your team or your developer knows it well, because that matters more to me than the language chart. If your front end is Next.js, PHP can still serve the data. Read tentang Next.js dan PHP (Indonesian). ### Verdict PHP is a server-side language that turns code into HTML, it runs WordPress, and it is easy to try on your own machine with php -S. For a website owner, the two things worth knowing are that it exists under your site and that its version needs updates. If you want a PHP app built or fixed, this is how I work on PHP development. --- ## Is PHP Dead? PHP and WordPress Now, and What Is Set for 2027 URL: https://madebyaris.com/blog/future-of-php-and-wordpress-2027 Published: 2026-10-27. Updated: 2026-10-27. You run a business on a PHP app or a WordPress site. Someone at a meetup, or in a comment thread, told you PHP is dead and you should rebuild everything in JavaScript before it is too late. Is that true, and is it still safe to keep building on PHP? Short answer: no, PHP is not dead. The usage numbers below are large, and the release calendar says it is still moving. The more useful question is whether your own app is on a version that still gets fixes. ### What do the numbers say? All W3Techs figures here are from 27 Oct 2026. PHP is on 69.2% of websites with a known server-side language. Of those PHP sites, 65.6% run version 8, 26.6% run version 7, and 7.7% run version 5. WordPress runs 39.6% of all websites, and 58.3% of sites with a known CMS. Developers still use it, too. The Stack Overflow Developer Survey 2025 asked about extensive development work in the past year, and PHP got 18.9% of all respondents. That is a lot of people for a dead language. For WordPress sites, the wordpress.org stats API gives the PHP version split. You can read the raw data yourself: ``` curl -s https://api.wordpress.org/stats/php/1.0/ ``` On 27 Oct 2026 it returned these shares: PHP version | Share of WordPress sites | 8.3 | 27.355% | 8.2 | 23.161% | 7.4 | 15.076% | 8.4 | 10.179% | 8.1 | 9.588% | 8.5 | 5.647% | 8.0 | 3.508% | Add up 8.1, 8.0, 7.4 and the older lines, and you get about 34% of WordPress sites on PHP versions with no project support. That figure is the total of the API values for those versions. So PHP is alive, and a large share of it runs old. ### What changed in PHP, and what is next? The current release is PHP 8.5.12. PHP 8.5.0 came out on 20 Nov 2025. PHP 8.6 is next: RC4 came out on 21 Oct 2026, the PHP project plans RC5 for 5 Nov, and it targets general availability on 19 Nov 2026. That plan can change, as release plans do. Each version gets active support, then security fixes only. This is the php.net table on 27 Oct 2026: Version | Active support until | Security fixes until | 8.2 | ended | 31 Dec 2026 | 8.3 | ended | 31 Dec 2027 | 8.4 | 31 Dec 2026 | 31 Dec 2028 | 8.5 | 31 Dec 2027 | 31 Dec 2029 | PHP 8.2 loses security fixes at the end of 2026. On the API numbers above, that is the second largest group of WordPress sites, so a lot of upgrades are due in the next two months. Support windows matter in practice. On 21 Oct 2026, the PHP project fixed two remote code execution flaws in PHP itself. The fixes shipped for 8.5, 8.4, 8.3 and 8.2. PHP 8.1 and older got no project updates, except minimal source backports for 7.4, 8.0 and 8.1. To see where your own app stands, this is the check I would run first: ``` php -v ``` ### What has WordPress published so far? WordPress shipped 7.0 on 20 May 2026 and 7.1 on 19 Aug 2026. The latest release is 7.1.3, from 6 Oct. WordPress 7.2 Beta 1 came out on 20 Oct, and the planned release date for 7.2 is 8 Dec 2026. The roadmap set a goal of three major releases in 2026. Phase 3 of Gutenberg is underway, and it is about collaborative editing. WordPress has published no release dates for 2027. A roadmap survey is open until 16 Nov 2026. So anyone who gives you a WordPress 2027 calendar today is guessing, including me below. WordPress recommends PHP 8.3 or later. On the API numbers above, 8.3, 8.4 and 8.5 together cover about 43% of WordPress sites, as a total of the API values. ### Where do PHP and WordPress fall short? A PHP monolith and a classic WordPress theme tie content and front end together. That is fine until the front end needs to do something the theme was never built for. A JavaScript front end such as Next.js can split the two, with WordPress kept as the place editors write. For that trade, read WordPress vs Next.js: when it is worth it. For the platform limits, read kekurangan WordPress (Indonesian). ### What do I think happens next? This part is my prediction, not a fact. I think a chatbot will make WordPress easy to use in 2027. I also think design will be easier with editors and drag-and-drop tools. Custom code will replace many plugins, in my view. AI tools will help people write that code for their own site. Time will show if I am right. ### Should I keep, modernize or move? If your PHP app runs on 8.3 or later and works, keep it, and update it on schedule. If it runs on 8.2, plan the upgrade before 31 Dec 2026. If it runs on 8.1 or older and breaks on upgrade, that is a modernization job. If WordPress works for your editors but the front end is slow or limited, consider headless WordPress. If you have already decided to leave WordPress, read migrasi WordPress ke Next.js (Indonesian). For background, read tentang Next.js dan PHP (Indonesian). ### Verdict PHP and WordPress are both alive. The real deadline is version support, and php.net publishes those dates in advance. Check your version, plan around the support table, and move only when the stack blocks the product you need. If your app is the kind that breaks on every upgrade, this is how I approach PHP modernization. --- ## WordPress Security Checklist for Business Websites URL: https://madebyaris.com/blog/wordpress-security-checklist Published: 2026-10-27. Updated: 2026-10-27. Your business site runs on WordPress. It works, the leads come in, and the dashboard shows a red number next to Plugins that nobody has clicked for a while. Is the site safe, and what should someone actually do each month to keep it that way? WordPress is still the top choice on hosting in Indonesia, and I still work with it. That is why I treat a plugin update on a live site as real work. So this is the monthly routine I would run on a business site, with the commands and settings I would use. It starts with two updates that cannot wait for next month. ### Which updates do I need right now? On 22 Sep 2026, WordPress 7.1.2 fixed a flaw in WordPress core. It is CVE-2026-87902, a path traversal through get_page_template(). The flaw has two ratings: WordPress calls it critical, and the NVD record shows 8.1 HIGH (CISA-ADP). NVD data shows fixes back to the 4.7 branch, in 4.7.37. If your site is on 7.1, you need 7.1.2 or later, and if it is on an older branch, take the latest release on that branch. On 21 Oct 2026, the PHP project fixed two remote code execution flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619. The ratings differ by source. The PHP project scores both 9.2 CRITICAL, while NVD scores CVE-2026-109618 at 9.8 CRITICAL and CVE-2026-109619 at 8.1 HIGH. These PHP flaws are not in WordPress, and WordPress plans no update for them. Your server needs PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35. The PHP project says the risk is highest for mod_php. PHP 8.1 and older get no project updates, except minimal source backports for 7.4, 8.0 and 8.1, and the release notes say the temporary mitigations do not make an installation safe. You can see both versions in Tools > Site Health > Info. If you have shell access with WP-CLI, I would check from the server instead: ``` wp core version php -v ``` ### Why is WordPress a target at all? WordPress runs 39.6% of all websites, per W3Techs on 27 Oct 2026. It runs 58.3% of sites with a known CMS, per the same page. Anything that common is worth automating attacks against. Risk comes from four places. Core has its own security releases, as above. Plugins and themes add code from many authors. Hosting decides the PHP version and the server settings. The monthly routine below touches all four. ### How do updates work, and what should I update by hand? WordPress has run background updates since version 3.7, for four types: core, plugin, theme and translation. Since 5.6, new installs auto-update minor and major core releases, while older installs keep their old behavior. So a site set up years ago may not behave like a fresh one. Check your own setting in the update guide. For plugins and themes, I would update on staging first, click through the pages that make money, then update live. ``` wp plugin list --update=available wp plugin update --all ``` ### Do my backups actually restore? A backup you never restored is a guess. Restore one to a staging copy each month, and check that the site loads and that you can log in. The WordPress backup guide covers the files and the database. Both matter, because a database without the uploads folder is a site with no images. ### Who still has an account? Remove accounts nobody uses, and give each person the lowest role that does the job. The intern from two years ago does not need to be an Administrator. ``` wp user list --role=administrator ``` ### Is the login hardened? Two-factor login is not in core. The wordpress.org Two Factor plugin adds it. Version 0.17.0 has 100,000+ active installs and needs WordPress 7.0 or later. I would also limit failed login attempts, so a password guesser has to be patient as well as lucky. ### Which plugins and themes should go? Delete what you do not use. A deactivated plugin is still code on the server, and it still needs updates you will forget to run. The same goes for the default themes nobody switched to. ### Is the PHP version current? WordPress recommends PHP 8.3 or later. It also recommends MariaDB 10.11+ or MySQL 8.0+, and HTTPS. Many sites are behind. The wordpress.org stats API shows about 34% of WordPress sites on PHP older than 8.2. That figure is the total of the API values for those versions. Those sites get no fix from the PHP project for the October flaws, except the minimal backports. ### Which settings would I harden once? The Hardening WordPress guide covers file permissions, database security, wp-admin, backups, logging and monitoring. Two settings from that guide go straight into wp-config.php: ``` define( 'DISALLOW_FILE_EDIT', true ); ``` This turns off the theme and plugin editor in the dashboard, so a stolen admin login cannot edit PHP files from the browser. The guide also lets you move wp-config.php one folder above the web root, if your host allows it. I would also set fresh security keys and salts, serve every page over HTTPS, and add security headers. ### What if the site is already hacked? The wordpress.org FAQ My site was hacked gives the full process. I would start with five steps: - Put the site in maintenance mode or take it offline. - Change all admin, hosting, database and SFTP passwords. - Restore a clean backup from before the hack. - Update core, plugins, themes and PHP. - Find how they got in before you go live again. If you skip step 5, the hole that let them in is still open after the restore. ### Verdict WordPress is safe enough for a business site when somebody owns the routine. Update core and PHP for the two flaws above now, then run the same short list each month: updates on staging, a restore test, a user review, a login check, a plugin cleanup and the PHP version. If nobody on your side has the time to own that list, this is how I handle WordPress maintenance. --- ## React Security: Patch, Check and Harden Your Next.js App URL: https://madebyaris.com/blog/react-nodejs-security-checklist Published: 2026-10-27. Updated: 2026-10-27. You ship a Next.js app on the App Router. Someone in the team chat posts a link about a React Server Components vulnerability with a CVSS score of 10.0, and the next message is “are we affected?” Nobody answers for a while, because nobody is sure which package versions the app actually runs. This is how I would answer that question, then how I would check the everyday React and Node.js risks while the repo is open anyway. ### What was the React Server Components vulnerability? On 3 Dec 2025, React disclosed CVE-2025-55182, and React rates it CVSS 10.0. It sits in the server packages that run Server Components: react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack. The affected versions are 19.0, 19.1.0, 19.1.1 and 19.2.0. On 11 Dec 2025, React disclosed more flaws in the same area. CVE-2025-55184 and CVE-2025-67779 are denial of service flaws, rated 7.5, and CVE-2025-55183 exposes source code, rated 5.3. Some early fixes were incomplete, so React says to use 19.0.4, 19.1.5, 19.2.4 or later. On 26 Jan 2026, React updated the post again with CVE-2026-23864, rated 7.5. The latest React release is 19.3, from 9 Sep 2026. So the advisory history is long, and the safe reading is that “we patched in December” does not settle anything. The first thing I would run is a list of what is installed, from the lockfile, without guessing: ``` npm ls react react-dom next npm ls react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack ``` ### Does it affect my Next.js app? Next.js tracked this as CVE-2025-66478. Next.js 14.x stable, the Pages Router and the Edge Runtime were not affected. That first fix is now old, though. On 14 Oct 2026, Next.js shipped more security fixes on its LTS lines, so the answer is to use the latest patch for your line, and not to stop at the December 2025 fix. Your setup | What I would do | App Router on Next.js 15 or 16 | Update to the latest patch on your line | Next.js 14.x stable or Pages Router only | Not affected by CVE-2025-66478; still take the latest patch | Edge Runtime only | Not affected by CVE-2025-66478; still take the latest patch | To see how far behind the app is, I would start with this: ``` npm outdated next react react-dom ``` Then I would pin the newest patch on the same major line, run the build and the tests, and only then think about a major upgrade. For what changed in recent releases, see Next.js 16.4 (Indonesian). ### Where does raw HTML get into the page? The React docs warn that dangerouslySetInnerHTML can introduce an XSS vulnerability. At least the name is honest about it. I would search for every use and trace where the HTML comes from: ``` grep -rn "dangerouslySetInnerHTML" app components src ``` Each hit should get HTML you trust or have sanitized. If the answer to “where does this come from” is “a form field”, that is the bug. ### Are secrets leaking into the browser bundle? Next.js puts only NEXT_PUBLIC_ variables into the browser bundle, and other variables stay on the server. So a NEXT_PUBLIC_ name means the value is public, whatever the variable is called. I would list them and read each one: ``` grep -rn "NEXT_PUBLIC_" .env* app src ``` An API secret with that prefix is a public API secret. Move it to a server-side variable, and rotate it, because it already shipped. ### Is auth checked on the server? A check in a component hides a button. It does not protect the data behind it. Every route handler and Server Action that reads or writes data needs its own session check on the server, for example: ``` "use server"; export async function deleteInvoice(id: string) { const session = await getSession(); if (!session) throw new Error("Unauthorized"); // delete only after the check } ``` getSession here stands for whatever auth helper the app already uses. For route patterns, see Next.js App Router API. ### What about the Node.js side? npm audit sends a description of your dependencies to the registry and reports known vulnerabilities. It exits with a non-zero code when it finds any, so it can fail a CI job. By default it needs a package-lock or shrinkwrap file. npm writes package-lock.json when it changes your dependency tree, so commit that file and let CI read it. ``` npm ci npm audit --omit=dev ``` Keep secrets in server-side variables and out of the logs. Validate every request body on the server, and add rate limits to login, signup and any costly endpoint. The OWASP input validation cheat sheet covers the checks. ### Which Node.js line should I run? On 27 Oct 2026, Node.js 22 and 24 are in maintenance, and Node.js 26 starts Active LTS on 28 Oct 2026. Node.js 20 reached end of life on 30 Apr 2026, so an app still on 20 is running without security fixes. Line | Status | End of life | 20 | ended | 30 Apr 2026 | 22 | maintenance | 30 Apr 2027 | 24 | maintenance since 20 Oct 2026 | 30 Apr 2028 | 26 | Active LTS from 28 Oct 2026 | 30 Apr 2029 | ``` node -v ``` ### What about AI-written code? On my own side projects, I let AI agents write code. On company work, I do not trust AI code until I read it and test it. I also keep dependencies few. If I can write a small part myself, I do not install a package for it. AI tools write code fast, and they can copy an unsafe pattern just as fast. I would review that code like any other pull request, with the same searches as above. The PR review checklist for AI-generated code is the list I would use. For the long-term cost, read technical debt in AI-built apps (Indonesian). ### Verdict If the app runs the App Router, update React and Next.js to the latest patch on your line today, and treat the December 2025 versions as a floor you have already passed. Then spend the same afternoon on raw HTML, NEXT_PUBLIC_ variables, server-side auth checks, npm audit in CI and the Node.js line. If the update breaks the build and you want help getting it green, this is how I handle code fixing. --- ## PHP Security: What to Check First in an Older PHP App URL: https://madebyaris.com/blog/php-security-checklist Published: 2026-10-27. Updated: 2026-10-27. You have a PHP app that was built years ago. It still takes orders, or bookings, or leads, and nobody wants to touch it because the last person who knew the code left. Then a security headline about PHP shows up in your feed, and the question is simple: is my app exposed, and what do I fix first? This is how I would check an app like that, in the order I would do it. The first step happens on the server. ### Is my PHP version already the problem? On 21 Oct 2026, the PHP project shipped a critical security release for two flaws that allow unauthenticated remote code execution. The ids are CVE-2026-109618 and CVE-2026-109619. The flaws are in PHP itself, so they affect PHP installs that serve web requests, and the PHP project says the risk is highest for mod_php. The ratings depend on who you ask. The PHP project scores both 9.2 CRITICAL (CVSS 4.0). NVD scores CVE-2026-109618 at 9.8 CRITICAL and CVE-2026-109619 at 8.1 HIGH. Either way, I would put it on this week. The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Within each branch, older releases are vulnerable. PHP 8.1 and older get no project updates, except minimal source backports for 7.4, 8.0 and 8.1. The release notes list temporary mitigations, and they also say those mitigations do not make an installation safe. I read that as “update, do not tune”. The first thing I would run on the server is this: ``` php -v php -i | grep -i "session.cookie" ``` The first line gives the version. The second shows the session cookie settings, which you will need later. If the site runs WordPress, there is no WordPress update for this. WordPress shows the PHP version in Tools > Site Health > Info > Server, and the fix is a PHP update on the host. ### Which PHP versions still get fixes? This is the php.net support table on 27 Oct 2026. Version | Active support until | Security fixes until | 8.2 | ended | 31 Dec 2026 | 8.3 | ended | 31 Dec 2027 | 8.4 | 31 Dec 2026 | 31 Dec 2028 | 8.5 | 31 Dec 2027 | 31 Dec 2029 | The latest stable release is 8.5.12. PHP 8.2 stops getting security fixes in about two months, so an app on 8.2 is fine today and on borrowed time in January. Old versions are common. The wordpress.org stats API shows about 34% of WordPress sites on PHP older than 8.2. That number covers WordPress sites only, and it is the total of the API values for those versions. It still tells you that “we never upgraded” is a normal state for many sites. ### Is PHP itself insecure? The language gets security fixes on a public schedule. Old versions do not. Once the version is current, the rest of the work is in your own code, and the OWASP Top 10 is a good map. The current edition is 2025. Injection is A05, Cryptographic Failures is A04, and Software Supply Chain Failures is A03. Those three are where I would start reading an old PHP codebase, so they get their own sections below. ### How do I stop SQL injection? Do not build a query string out of user input. Use prepared statements with PDO, so the database treats the input as data and never as SQL. ``` $stmt = $pdo->prepare("SELECT id, email FROM users WHERE email = :email"); $stmt->execute(["email" => $_POST["email"]]); $user = $stmt->fetch(); ``` When I read an old app, I search for queries glued together with a dot and a request variable. Every hit is a candidate. ### How do I stop XSS? Escape every value at output time, for the context it lands in, such as HTML body or an attribute. htmlspecialchars is the basic tool for HTML. A Content-Security-Policy header is a good second layer. The OWASP XSS cheat sheet covers the contexts. ``` echo htmlspecialchars($comment, ENT_QUOTES, "UTF-8"); ``` ### How should I store passwords? Use password_hash and password_verify, and nothing you wrote yourself. PASSWORD_DEFAULT uses bcrypt today, and the php.net manual says this default can change over time. So store the full hash string and give the column room to grow. ``` $hash = password_hash($password, PASSWORD_DEFAULT); if (password_verify($input, $hash)) { // log the user in } ``` If the old app stores md5 hashes, that is the moment to plan a rehash on next login. ### What about file uploads? Treat every upload as hostile. Check the type on the server, store files outside the web root, and never let an uploaded file run as code. The OWASP file upload cheat sheet lists the full set of checks. The question I would ask is short: if someone uploads a file named shell.php, can the web server run it? ### Are the session defaults safe? Not for a production site. The php.ini defaults are session.cookie_httponly “0”, session.cookie_secure “0”, an empty session.cookie_samesite, and session.use_strict_mode “0”. That is four settings left for you to decide. ``` session.cookie_httponly = 1 session.cookie_secure = 1 session.cookie_samesite = "Lax" session.use_strict_mode = 1 ``` Add a CSRF token to every form that changes data, too. ### Are my dependencies safe? composer audit checks your installed packages for known security vulnerabilities. Composer added it in version 2.4.0, and you can also run install or update with the –audit flag. ``` composer audit composer update --audit ``` ### What would my own check list look like? - Run php -v and compare it with the fixed versions above. - Search the code for queries that join strings with user input. - Search for echo or print of request data without escaping. - Check how passwords are stored. - Check where uploads go, and whether that folder can run PHP. - Read the session settings in php.ini. - Run composer audit. ### When is a patch not enough? A patch fixes one flaw. It does not fix an app that cannot move to a supported PHP version. Some apps break on each upgrade, and some have no tests, so nobody trusts a change. If your app runs PHP 8.1 or older, a version bump is a project that needs its own plan and tests. ### Verdict Update PHP first, because the October flaws sit in PHP itself and no code review fixes them. Then read your queries, your output, your passwords, your uploads and your session settings, in that order. If the upgrade itself is the wall you keep hitting, that is a modernization job, and this is how I approach PHP modernization. --- ## Grok Bot untuk kantor: inbox, riset, dan expense di komputer cloud URL: https://madebyaris.com/blog/grok-untuk-kantor Published: 2026-10-24. Updated: 2026-10-24. Grok Bot mengerjakan tugas kantor di komputer cloud yang punya browser, file, dan command line. Pekerjaannya tetap berjalan walaupun aplikasi atau laptop kamu ditutup. Saya Aris Setiawan. Penjelasan dasarnya ada di Mengenal Grok Bot, dan versi Inggris untuk kerja kantor ada di Grok Bot for office work. Di sini saya menulis dari sisi orang yang memegang inbox dan persetujuan. ### Apa bedanya dengan chat Dengan chat, kamu menempelkan email, membaca ringkasannya, lalu menyalin hasilnya kembali. Tool kantornya tetap tertutup selama proses itu. Grok Bot membuka tool tersebut sendiri. Ada tool yang terhubung sebagai app, dan ada yang dibuka lewat browser. Halaman resminya ada di x.ai/bot. ### Satu komputer untuk semua Bot Semua Bot dalam satu akun memakai satu komputer cloud yang sama. Cookie browser dan sesi login juga ikut dipakai bersama. Karena itu nama Bot hanya berfungsi sebagai label, dan Bot kedua tidak bisa dijadikan tempat aman untuk password penting. ### Tugas yang bisa diserahkan Daftar berikut berisi tugas yang sudah ada di meja kantor, beserta bagian yang tetap saya pegang: - Inbox: Bot meringkas thread dan menyiapkan draf balasan, sedangkan pengirimannya tetap di tangan saya. - Riset: Bot membuka sumber dan menulis ringkasan, sedangkan kalimat dari sumber yang tidak bisa saya buka tidak saya pakai. - Expense: Bot mengisi form dari struk, sedangkan angkanya tetap saya setujui. - Catatan rapat: Bot merangkum rapat menjadi satu halaman, sedangkan bagian yang terlalu panjang saya potong. Mulailah dari satu tugas untuk satu Bot. Pilih tugas yang perintahnya muat dalam lima kalimat. ### Langkah yang tetap diketik sendiri Untuk password, kode 2FA, atau CAPTCHA, kamu sendiri yang mengisinya. Bot menyerahkan layar komputer bersama ke kamu lewat computer takeover. Pembelian dan transfer uang menunggu persetujuan kamu lebih dulu. Auto-review memeriksa tool call dan aksi di komputer. Aturannya bisa diatur menjadi “Ask first” atau “Allow automatically”, dan setiap permintaan punya pilihan “Allow once”, “Always allow”, atau “Deny”. Persetujuan tidak membatalkan pekerjaan yang sudah selesai, jadi atur aturan “Ask first” sebelum Bot masuk ke inbox kerja. Akses dan paket Grok Bot dijelaskan di Mengenal Grok Bot. Terakhir dicek: 24 Oktober 2026. Jadi, Bot bisa mengerjakan langkah kantor, tetapi keputusan dan login tetap di tangan kamu. Langkah pertamanya cukup memilih satu tugas inbox dan menuliskannya sebagai satu permintaan ke satu Bot. --- ## Grok Bot for office work: inbox, expenses and research URL: https://madebyaris.com/blog/grok-bot-for-office-worker Published: 2026-10-24. Updated: 2026-10-24. Office work is inbox, expenses, research and status checks in tools with no API. These are the jobs I would give a Grok Bot first. For what the app is, read the Grok Bot intro. I am Aris Setiawan. I ship Next.js for client work. This post is my plan for an office desk. ### Jobs I would hand a Bot I name each Bot for its job, so the name tells me what it does. The name is only a label. All Bots on one account share one cloud computer. The product page shows example Bots such as Sales Outbound, Expense Manager and Account Health. I give no time savings for them. This list shows the jobs I would hand off and the step that I keep: Job | What the Bot does | What I keep | Inbox | Drafts replies, sorts mail, pulls threads before a meeting | I send any reply that commits us | Expenses | Exports the month, matches receipts, flags gaps | I approve the spend | Research | Opens sources and writes a brief into /workspace | I decide what we believe | Meeting prep | Collects the agenda, the last email and open tickets | I lead the meeting | Status checks | Uses a connected app, or the website in the browser | I check the result | A Bot can keep working when I close the laptop. Closing the app does not stop a background turn. ### What I still type myself Passwords, two-factor codes and CAPTCHAs come back to me through a computer takeover. Purchases and financial transfers wait for my approval. Auto-review checks tool calls and computer actions. I can set “Ask first” or “Allow automatically” rules. A prompt offers “Allow once”, “Always allow” or “Deny”. The intro post explains what an approval cannot undo. Browser cookies and signed-in sessions belong to the shared computer, not to one Bot. So I do not use a second Bot as a safe place for production credentials. ### How I would set it up - Install the app on the computer or phone I use. The FAQ lists the supported systems. - Sign in with the plan I have. Grok Bot uses Cursor authentication. - Name one Bot each for inbox, expenses and research. - Sign each Bot into its tools, watch the first run and type the codes. - Make a skill for the task. Add a routine only after one run finishes well. Teach a task can record a browser workflow into a draft skill. The recording has a ten minute limit. The rollout may be gradual, so some accounts may not have it yet. Last checked: 24 October 2026. Start with one office job that you can check in five minutes. Today, pick that job and write it as a single request to one Bot. --- ## Mengenal Grok Bot, aplikasi xAI untuk mengerjakan tugas di komputer cloud URL: https://madebyaris.com/blog/mengenal-grok-bot Published: 2026-10-24. Updated: 2026-10-24. Grok Bot adalah aplikasi dari xAI yang halamannya ada di x.ai/bot. Kamu memberi nama dan tugas ke sebuah Bot, lalu Bot itu bekerja di komputer cloud dan membuka tool yang biasa kamu pakai. Saya Aris Setiawan, developer Next.js untuk proyek klien. Sebelum aplikasi ini saya hubungkan ke akun mana pun, saya ingin paham dulu cara kerjanya. Versi Inggrisnya ada di Grok Bot. ### Tiga hal yang sama-sama bernama Grok Grok di grok.com dan di X adalah chat yang menjawab pertanyaan. Di Cursor, Grok muncul sebagai salah satu nama model. Grok Bot berbeda dari keduanya karena ia mengerjakan tugas di sebuah komputer. Aplikasinya tersedia untuk Mac, Windows, dan Linux. Versi Linux tersedia sebagai paket .deb, .rpm, atau AppImage untuk x64 dan Arm64. Di ponsel dan tablet, syaratnya minimal iOS 18, iPadOS 18, atau Android 9. ### Cara kerjanya Setiap Bot bisa memakai browser, command line, file, dan tool yang sudah terhubung. Semua Bot dalam satu akun memakai satu komputer yang sama, termasuk cookie dan sesi login di browser-nya. Dokumentasi xAI menegaskan bahwa Bot yang berbeda tidak bisa dijadikan batas keamanan. Tool tertentu terhubung sebagai app, yang dipasang sebagai plugin lewat menu Connect apps. Tool tanpa plugin tetap bisa dipakai, karena Bot membuka website-nya lewat browser. Untuk password, kode 2FA, atau CAPTCHA, kamu sendiri yang mengisinya. Bot menyerahkan layar komputer bersama ke kamu lewat computer takeover. Pembelian dan transfer uang menunggu persetujuan kamu. Persetujuan itu tidak membatalkan pekerjaan yang sudah selesai, jadi pahami dulu batas ini sebelum Bot masuk ke email kamu. Skill berisi cara mengerjakan sebuah tugas, sedangkan routine menentukan kapan tugas itu jalan. Saya memisahkan keduanya supaya tidak ada tugas yang terjadwal sebelum saya melihatnya selesai satu kali. ### Akses dan paket xAI merilis Grok Bot dalam status beta pada 11 Agustus 2026. Login-nya memakai autentikasi Cursor. Grok Bot tidak dijual terpisah. Di The X Subscription, Grok Bot termasuk dalam paket Premium, Super, dan Ultra, tetapi tidak termasuk dalam Plus dan Free. SuperGrok adalah langganan terpisah yang bisa ditautkan ke paket Cursor lama. Paket Cursor berbayar yang lama juga sudah termasuk Grok Bot. Untuk tim, ada dua jalur yang sudah termasuk Grok Bot: seat tim di The X Subscription dan paket Cursor Teams lama yang self-serve. Akses Enterprise diatur lewat admin atau tim akun, jadi tanyakan langsung ke tim sales. ### Sumber yang saya baca Saya mulai dari x.ai/bot, lalu membaca Introducing Grok Bot (11 Agustus) dan Grok Bot is now included with more plans (26 Agustus). Soal komputer bersama ada di Computer and apps, soal login dan persetujuan ada di Approvals, security, and privacy. Daftar perangkat dan paket ada di FAQ. Terakhir dicek: 24 Oktober 2026. Jadi, semua Bot di satu akun berbagi satu komputer, dan langkah login tetap ada di tangan kamu. Langkah pertamanya cukup membuka FAQ Grok Bot dan mencocokkan perangkat serta paket yang kamu punya. --- ## Grok Bot: what the xAI app is and what it can do URL: https://madebyaris.com/blog/grok-bot Published: 2026-10-24. Updated: 2026-10-24. Grok Bot is an app from xAI, at x.ai/bot. You give a named Bot a job. The Bot works on a cloud computer, and it can open the tools you already use. I am Aris Setiawan. I ship Next.js for client work. I wanted to know what this app does before I signed it into my accounts. ### Same word, three products The Grok chat on grok.com and on X answers what you type. In Cursor, Grok is a model name in the model list. Grok Bot is a third thing: an app that does work on a computer. The app runs on Mac, Windows and Linux. Linux builds come as a .deb, .rpm or AppImage package, for x64 and Arm64. Phones and tablets need iOS 18, iPadOS 18 or Android 9, or a later version. ### What it is You name a Bot and you give it work. The Bot can use a browser, a command line, files and connected tools. All Bots on one account share one computer. Browser cookies and signed-in sessions are shared too. The docs say that separate Bots are not a security boundary. Some tools connect as apps. The app installs them as plugins from Connect apps. For a tool with no connector, the Bot uses the website in the browser. Some steps come back to you. You type passwords, two-factor codes and CAPTCHAs through a computer takeover. Purchases and financial transfers need your approval. An approval does not reverse work that is already complete. Read that line before you sign a Bot into your email. A skill describes how to do a task. A routine tells the Bot when to run. I do not schedule a task before I see it finish once. ### Access and plans xAI launched Grok Bot in beta on 11 Aug 2026. Grok Bot uses Cursor authentication. Grok Bot is not sold alone. On The X Subscription, Premium, Super and Ultra include Grok Bot. Plus and Free do not include it. SuperGrok is a separate subscription. You can link it to a legacy Cursor plan. Legacy paid Cursor plans also include Grok Bot. For teams, two paths include Grok Bot. One is a team seat on The X Subscription. The other is a legacy self-serve Cursor Teams plan. Enterprise access goes through an admin or account team; check with sales. ### What I read I started at x.ai/bot. Then I read the launch post from 11 Aug, Introducing Grok Bot. The access post from 26 Aug is Grok Bot is now included with more plans. For the shared computer, I read Computer and apps. For logins and approvals, I read Approvals, security, and privacy. The FAQ has the platform list and the plan details. Last checked: 24 October 2026. All Bots on your account work on one shared cloud computer. Treat them as one desk. Today, open the FAQ and check that your device and plan are on the list. --- ## AI ROI for small businesses: how to judge your AI tool spending in 2026 URL: https://madebyaris.com/blog/ai-roi-small-business Published: 2026-10-18. Updated: 2026-10-18. On Friday, 16 October 2026, the Nasdaq Composite fell 2.14%, per CNN Business, accessed 18 October 2026. Investors had questions about the debt that some AI companies use to grow. If you pay for AI tools in a small business, use this news to check your AI ROI. AI ROI (return on investment) compares the value that each tool gives you with its cost. ### Short answer List every paid AI tool. Give each tool one job and one measure. Compare the monthly cost with the time or money that the tool saves. After 30 days, cancel each tool that has no measure. ### What the AI debt news means for a small business Large AI companies spend a lot of money on data centers. Some of this money is borrowed. The Bank for International Settlements calls some of it “shadow borrowing”, per BIS Quarterly Review, accessed 18 October 2026. The review describes obligations that are “economically akin to debt but largely reside outside corporate balance sheets”. Investors worry that this spending will not pay back. A small business does not borrow for data centers. The same question applies to your tool bill: does the money you spend come back as value? AI vendors can also change their billing model. GitHub Copilot moved to usage-based billing on 1 June 2026, per the GitHub blog, accessed 18 October 2026. GitHub kept its base plan prices, but the bill now depends on usage. A U.S. Census Bureau working paper gives data about how US firms used AI. Of all US firms, 18% used AI in a business function, per CES Working Paper 26-25, accessed 18 October 2026. The period was November 2025 to January 2026. The survey sample frame was about 1.2 million US businesses. This is a working paper, not an official Census publication. It does not give an ROI figure. ### Step 1: List each AI tool and its monthly cost Open your bank statement and your card statement. Find each AI subscription. Write the tool name, the plan, the number of seats, and the monthly cost. Include tools inside other products, for example an AI add-on in your email or design software. If you find a tool that nobody uses, cancel it now. ### Step 2: Give each tool one job and one measure Write one job for each tool in one sentence. For example: “This tool writes the first draft of product descriptions.” Then write one measure that you can count: - Time: hours that the team saves each week. - Output: drafts, tickets, or pages that the team completes. - Money: sales, leads, or costs that change because of the tool. If you cannot write a job, the tool has no job. If you cannot write a measure, you cannot judge the tool. ### Step 3: Compare the cost with the time saved Multiply the hours saved by the hourly cost of the person who does the work. Compare the result with the monthly cost of the tool. Collect data for 30 days. Do not use estimates from the vendor. Use your own records, for example time logs or the number of closed tickets. If you pay for Cursor, you can read my notes on Cursor AI pricing to see how the plans operate. ### Step 4: Check the hidden costs Ask these questions about each tool before you decide: - Seats: do you pay for people who left or do not use the tool? - Usage limits: what happens when you go over the limit? - Data exports: can you take your data out in a usable format? - Lock-in: how much work is it to move to a different tool? - Review time: how long does a person need to check the output? ### Step 5: Keep, reduce, or cancel Use your measures to make one decision for each tool: - Keep: the value is clearly more than the cost. - Reduce: the tool helps, but the plan is too large. Move to a smaller plan or fewer seats. - Cancel: the tool has no job, no measure, or the cost is more than the value. Do this review again every quarter. Tools change, and your business changes. ### A simple AI spending review template Copy this table. The figures are examples only. They are not real data. Tool (example) | Job | Measure | Monthly cost | Monthly value | Decision | Writing assistant | First drafts of product text | 6 hours saved | USD 20 | USD 90 | Keep | Meeting notes tool | Summaries of client calls | Not used in 30 days | USD 15 | USD 0 | Cancel | Image generator, 5 seats | Social media images | 2 active seats | USD 100 | USD 60 | Reduce to 2 seats | If one AI feature is part of your website, read what AI integration services include. Some features do not need a large model. My notes on when a website needs machine learning explain that decision. For tasks with many steps, see AI agent development. ### Frequently asked questions #### How do I calculate the ROI of an AI tool? Subtract the monthly cost from the monthly value, then divide the result by the monthly cost. For the value, use the time result from Step 3, or use the extra sales from the tool. If you cannot find a value, the ROI is unknown, and the tool is a candidate to cancel. #### How long should I test an AI tool before I decide? Use 30 days for most tools, and write the job and the measure on day one. If the work happens only once a month, for example a monthly report, test for two cycles. Keep a short log with dates and hours, because a log gives better data than an opinion at the end. #### Do AI stock drops change the price of AI tools for small businesses? I cannot show a direct link between a stock drop and the price of a tool. The billing model can change, so save the price page and the billing terms on the day that you subscribe. At each quarterly review, compare the saved pages with the current pages to find differences early. #### Which costs do AI tool price pages not show? The hidden costs are unused seats, charges above a usage limit, review time, and the cost to leave a tool. To find them, check your invoices for unused seats and usage charges, and ask the team about weekly review time. Then try one data export, so that you see what leaving the tool involves. ### Next step Keep only the AI tools that have a job and a measure. List your paid AI tools and their monthly costs in the template above. Do you want an AI feature with a clear measure from the first day? Send me the task through AI integration services. I reply within 24 hours and tell you plainly whether I am the right fit for the task. You can also see all my AI development services. --- ## Cara membuat bracket turnamen bulu tangkis interaktif dengan Next.js URL: https://madebyaris.com/blog/bracket-turnamen-nextjs Published: 2026-10-18. Updated: 2026-10-18. BWF World Junior Championships 2026 berlangsung di Kairo pada 12 sampai 17 Oktober, sesuai halaman turnamen di situs BWF. Kalau klub kamu menggelar turnamen internal dengan bagan yang digambar di kertas atau di spreadsheet, bagan itu harus difoto ulang dan dikirim ke grup setiap kali ada pemenang baru. ### Jawaban singkat Untuk turnamen sekali jalan, generator bracket gratis sudah cukup. Bracket buatan sendiri dengan Next.js masuk akal kalau klub ingin bagan itu ada di website-nya sendiri, dengan URL, data, dan tampilan milik klub, serta pemenang yang naik ke babak berikutnya secara otomatis. Project di tutorial ini terdiri dari empat bagian, yaitu pasangan perempat final, pasangan babak berikutnya yang diambil dari pemenang, tampilan tiga babak, dan logika memilih pemenang. ### Kapan cukup pakai generator gratis, kapan perlu bracket sendiri? Sebelum memilih, jawab tiga pertanyaan berikut. Apakah hasil turnamen perlu tetap bisa dibuka di website klub tahun depan? Apakah bracket perlu tampil dengan nama, warna, dan alamat website klub sendiri? Apakah ada orang yang bisa merawat kodenya setelah turnamen selesai? Kalau ketiga jawabannya tidak, generator gratis lebih hemat waktu. ### Hasil akhir: bracket yang terisi otomatis Hasilnya berupa bracket sistem gugur untuk 8 pemain dengan tiga babak, yaitu perempat final, semifinal, dan final. Pemenang yang kamu pilih otomatis muncul di babak berikutnya, dan nama pemain di demo adalah nama contoh (fiktif). Saya membangun demo ini dengan bantuan AI coding agent, lalu hasilnya saya cek sendiri. ### Yang kamu perlukan Versi yang dipakai adalah Next.js 16.4.2 (App Router), React 19.3.0, dan Tailwind CSS v4, jadi kamu perlu Node.js yang bisa menjalankan versi Next.js itu dan pemahaman dasar tentang komponen React dan hook seperti useState. Kalau App Router masih baru buat kamu, baca dulu App Router dalam praktik. ### Langkah 1: tulis pasangan perempat final Bracket ini dibuat untuk nomor tunggal, dan setiap slot berisi satu nama pemain. Empat pasangan perempat final ditulis langsung di kode, lalu state bracket menyimpan pemenang setiap babak, yang awalnya masih kosong. Komponen BadmintonBracket, pasangan perempat final: ``` const QUARTER_PAIRINGS: [string, string][] = [ ["Andi Wijaya", "Budi Santoso"], ["Citra Dewi", "Dedi Pratama"], ["Eka Putri", "Fajar Nugroho"], ["Gita Rahma", "Hadi Susilo"], ]; interface BracketState { quarterWinners: (string | null)[]; semiWinners: (string | null)[]; finalWinner: string | null; } const initialState: BracketState = { quarterWinners: [null, null, null, null], semiWinners: [null, null], finalWinner: null, }; ``` ### Langkah 2: susun semifinal dan final dari pemenang Pasangan semifinal dan final tidak ditulis di kode, karena keduanya baru terbentuk setelah pemenang babak sebelumnya dipilih. Semifinal pertama mempertemukan pemenang perempat final pertama dan kedua, semifinal kedua mempertemukan pemenang ketiga dan keempat, sedangkan final terisi setelah kedua semifinal punya pemenang. Komponen BadmintonBracket, pasangan semifinal dan final dari pemenang: ``` const semiPairings = useMemo((): ([string, string] | null)[] => { const w = state.quarterWinners; const p0 = w[0] && w[1] ? ([w[0], w[1]] as [string, string]) : null; const p1 = w[2] && w[3] ? ([w[2], w[3]] as [string, string]) : null; return [p0, p1]; }, [state.quarterWinners]); const finalPairing = useMemo((): [string, string] | null => { const [a, b] = state.semiWinners; return a && b ? [a, b] : null; }, [state.semiWinners]); ``` ### Langkah 3: tampilkan bracket di halaman Setiap babak tampil sebagai satu kolom di layar lebar, sehingga ketiga babak berjajar dari kiri ke kanan, sedangkan di layar yang lebih kecil ketiganya tersusun ke bawah dalam satu kolom. Slot di semifinal dan final tampil sebagai tempat kosong sampai pemenang dari babak sebelumnya dipilih. Komponen BadmintonBracket, tampilan tiga babak: ```
{QUARTER_PAIRINGS.map((pair, i) => ( pickQuarter(i, player)} /> ))} {semiPairings.map((pair, i) => pair ? ( pickSemi(i, player)} /> ) : ( ), )} {/* … Final … */}
``` ### Langkah 4: pilih pemenang dan naikkan ke babak berikutnya Pemenang dipilih dengan mengetuk nama pemain, dan yang disimpan hanya nama pemenang, tanpa skor. Semua pilihan itu ada di state React di browser, jadi hasilnya hilang setelah halaman di-reload. Kalau salah pilih, pemenang bisa dikoreksi dengan mengetuk pemain lain di pertandingan yang sama, tetapi babak setelahnya ikut dikosongkan dan perlu dipilih ulang, sedangkan tombol “Reset bracket” mengosongkan semuanya. Komponen BadmintonBracket, memilih pemenang dan reset: ``` const pickQuarter = useCallback((matchIndex: number, player: string) => { setState((prev) => ({ quarterWinners: prev.quarterWinners.map((w, i) => i === matchIndex ? player : w, ), semiWinners: [null, null], finalWinner: null, })); }, []); const pickSemi = useCallback((matchIndex: number, player: string) => { setState((prev) => ({ ...prev, semiWinners: prev.semiWinners.map((w, i) => i === matchIndex ? player : w, ), finalWinner: null, })); }, []); const pickFinal = useCallback((player: string) => { setState((prev) => ({ ...prev, finalWinner: player })); }, []); const reset = () => setState(initialState); ``` ### Langkah 5: rencana untuk turnamen sungguhan Karena hasil di demo hanya tersimpan di browser, turnamen sungguhan membutuhkan dua tambahan, yaitu database untuk menyimpan pemenang supaya hasilnya tidak hilang setelah reload, dan hosting supaya panitia cukup membagikan satu link. Kalau kamu ingin memakai server sendiri, langkahnya ada di deploy Next.js di VPS murah. ### Pertanyaan yang sering ditanyakan #### Apa bedanya bracket sistem gugur dan klasemen setengah kompetisi? Di sistem gugur, pemain yang kalah langsung tersingkir, sehingga 8 pemain hanya butuh tujuh pertandingan sampai juara ditentukan, seperti di demo ini. Di setengah kompetisi (round robin), setiap pemain bertemu semua pemain lain satu kali, jadi 8 pemain membutuhkan 28 pertandingan dan tidak ada yang tersingkir di tengah jalan. Karena bentuknya berbeda, tampilannya juga berbeda, yaitu bracket untuk sistem gugur dan tabel hasil untuk setengah kompetisi, dan yang dibangun di tutorial ini hanya sistem gugur. #### Bagaimana cara mengatur bye kalau jumlah pemain ganjil? Demo di tutorial ini belum menangani bye, karena ukurannya tetap 8 pemain dengan pasangan yang ditulis langsung di kode. Untuk jumlah pemain lain, kamu perlu fungsi yang membulatkan jumlah slot ke 2, 4, 8, 16 atau 32, mengisi slot kosong sebagai bye, lalu meloloskan lawan bye ke babak berikutnya secara otomatis. #### Apakah bracket ini bisa dipakai untuk ganda dan beregu? Bracket di tutorial ini dibuat untuk tunggal, tetapi untuk ganda kamu cukup menulis nama pasangan di slot, misalnya “Pemain A/Pemain B”. Untuk beregu, satu pertemuan berisi beberapa partai, jadi data dan tampilannya perlu diubah supaya bisa mencatat partai-partai itu dan menentukan regu yang menang. Fitur beregu ini belum ada di demo. #### Bisakah pemenang dikoreksi setelah naik ke babak berikutnya? Bisa, seperti dijelaskan di Langkah 4, dengan aturan pengosongan berikut: - Pemenang perempat final yang diganti mengosongkan kedua semifinal dan final, termasuk semifinal di paruh bracket yang lain, karena fungsi pickQuarter mengisi ulang semiWinners dan finalWinner dengan null. - Pemenang semifinal yang diganti hanya mengosongkan final. - Pemenang final bisa diganti bebas tanpa mengosongkan apa pun. - Ketukan kedua pada pemenang yang sama juga mengosongkan babak setelahnya. ### Penutup Bracket di website sendiri paling berguna saat hasil turnamen klub perlu bisa dibuka lagi di satu URL milik klub. Catat dulu turnamen apa saja yang akan klub kamu gelar tahun ini. Kalau kamu ingin bracket seperti ini dibuatkan sekaligus dengan scoreboard live dengan Next.js, kirim daftar turnamen itu lewat jasa pembuatan website Next.js, dan saya balas dalam 24 jam. Kamu juga bisa melihat dulu layanan Next.js development saya. Terakhir dicek: 18 Oktober 2026. --- ## SEO halaman jadwal: cara membuat halaman jadwal bisnis yang mudah ditemukan di Google URL: https://madebyaris.com/blog/seo-halaman-jadwal Published: 2026-10-18. Updated: 2026-10-18. “Indosiar” masuk daftar pencarian yang sedang naik di Google Trends Indonesia pada 18 Oktober 2026, dengan berita dari Liputan6.com tentang jadwal sinetron siang itu pukul 13.30 WIB. Kalau gym, tempat kursus, atau klinik kamu memasang jadwal hanya sebagai gambar di Instagram, orang yang mencari jadwal itu di Google tidak menemukan halaman yang bisa dibaca. ### Jawaban singkat Halaman jadwal yang mudah ditemukan punya satu URL tetap yang isinya diperbarui, jadwal yang ditulis sebagai teks di samping gambar apa pun, tanggal yang jelas, serta baris “terakhir diperbarui” yang terlihat. Structured data Event hanya dipakai untuk acara sungguhan di lokasi fisik yang bisa didatangi umum. ### Satu URL tetap atau satu halaman untuk setiap tanggal? Saran saya untuk kebanyakan bisnis adalah satu URL tetap, misalnya /jadwal, yang isinya kamu perbarui setiap minggu, karena tautan dari Instagram, Google Maps, dan WhatsApp tetap mengarah ke halaman yang sama. Saran ini saya dasarkan pada cara Google menangani halaman yang mirip, yaitu dengan memilih satu URL kanonis untuk ditampilkan. Panduan Google tentang URL duplikat juga menjelaskan cara memberi tahu Google URL mana yang utama. Pengecualiannya adalah acara yang berdiri sendiri, seperti seminar atau turnamen, yang memang layak punya halaman sendiri. ### Jadwal dalam bentuk teks, dengan alt text untuk gambar Tulis jadwal sebagai teks HTML biasa, misalnya tabel hari, jam, dan nama kelas, lalu kalau kamu tetap ingin memasang gambar jadwal yang dibuat desainer, beri gambar itu alt text yang menjelaskan isinya. Google menjelaskan bahwa mereka memakai alt text bersama computer vision dan isi halaman untuk memahami gambar. ### Kapan structured data Event membantu, dan kapan tidak Structured data Event dari Google punya syarat yang ketat, karena setiap event harus punya URL sendiri dengan markup di URL itu dan harus berlangsung di lokasi fisik. Event juga harus bisa didatangi umum, sedangkan acara yang hanya online, jam buka usaha, dan kupon tidak termasuk. Artinya, jadwal siaran TV seperti jadwal sinetron tidak cocok diberi markup Event, dan jadwal kelas rutin di gym juga perlu dipikirkan dulu. Tampilan event khusus di hasil pencarian juga belum tercantum untuk Indonesia, jadi anggap markup ini sebagai cara membuat halaman lebih jelas tanpa berharap tampilan baru. ### Contoh untuk bisnis: kelas, klinik, dan event Berikut tiga contoh hipotetis untuk menggambarkan pilihan di atas: - Studio yoga, misalnya: satu halaman /jadwal-kelas berisi tabel mingguan dalam teks, diperbarui setiap Minggu malam, tanpa markup Event. - Klinik gigi, misalnya: jam praktik dokter ditulis sebagai teks di satu halaman, dan karena jam buka tidak termasuk event, markup Event tidak dipakai. - Penyelenggara workshop, misalnya: satu halaman untuk setiap workshop berbayar di lokasi tertentu, lengkap dengan markup Event, ditambah satu halaman daftar yang menautkan semuanya. Kalau jadwal kamu untuk klub olahraga yang ingin skor ikut tampil, saya pernah menulis tutorial scoreboard live dengan Next.js. ### Checklist singkat sebelum halaman jadwal di-publish - URL: satu alamat tetap yang tidak berubah setiap minggu. - Isi: jadwal ditulis sebagai teks, dengan hari, tanggal, jam, dan zona waktu. - Gambar: kalau ada, beri alt text yang menjelaskan isinya. - Tanggal: baris “terakhir diperbarui” yang terlihat oleh pengunjung. - Markup: Event hanya untuk acara di lokasi fisik yang bisa didatangi umum. - Plugin: kalau jadwal kamu ada di plugin WordPress, cek apakah plugin itu menulis jadwal sebagai teks, dan baca juga risiko plugin secara umum di kekurangan WordPress. Untuk pemeriksaan teknis yang lebih luas, gunakan checklist audit SEO teknis. ### Pertanyaan yang sering ditanyakan #### Apakah jadwal dalam bentuk gambar bisa dibaca Google? Google tidak menjanjikan hal itu, karena yang disebut di panduannya adalah alt text, computer vision, dan isi halaman sebagai bahan untuk memahami gambar. Panduan yang sama juga menyarankan agar gambar yang berisi teks tidak dipilih sebagai gambar utama untuk og:image, yaitu gambar yang tampil saat link dibagikan. Jadi kalau kamu membagikan link jadwal di WhatsApp atau Facebook, pakai foto atau ilustrasi biasa sebagai og:image dan biarkan jadwalnya tertulis di halaman. #### Lebih baik satu halaman jadwal atau satu halaman per tanggal? Untuk jadwal rutin, saya menyarankan satu halaman tetap, sedangkan posting per tanggal cocok untuk acara yang memang berbeda setiap kali. Panduan Google juga menyebut bahwa konten duplikat tidak termasuk pelanggaran spam, jadi posting jadwal lama yang sudah terlanjur ada tidak perlu dihapus dengan panik. Yang perlu kamu lakukan adalah berhenti membuat posting baru untuk jadwal rutin dan mengarahkan pengunjung ke halaman tetap itu. #### Kapan halaman jadwal perlu structured data Event? Ketika setiap acara punya halaman sendiri, berlangsung di lokasi fisik, dan bisa didatangi umum. Panduan umum structured data dari Google bahkan memberi contoh pelanggaran yang mirip dengan kasus jadwal TV, yaitu situs live streaming olahraga yang menandai siarannya sebagai event lokal. Jadi untuk jadwal siaran atau kelas online, cukup tulis jadwalnya sebagai teks yang rapi tanpa markup Event. #### Kapan halaman jadwal perlu diperbarui? Setiap kali ada perubahan, termasuk sesi yang batal, pengajar yang berganti, atau jam yang bergeser. Hapus sesi yang sudah lewat dari tabel supaya pengunjung tidak salah datang, dan ubah isi di URL yang sama tanpa membuat alamat baru. Kalau jadwal kamu juga dipasang di Google Maps atau Instagram, cocokkan ketiganya di hari yang sama supaya tidak ada dua versi jadwal yang beredar. ### Penutup Halaman jadwal yang ditemukan di Google bertumpu pada satu URL tetap dan jadwal dalam bentuk teks, sedangkan markup Event hanya membantu untuk acara sungguhan. Buka halaman jadwal bisnis kamu dan coba blok teks jadwalnya dengan kursor, karena jadwal yang tidak bisa diblok masih berupa gambar. Kalau kamu ingin saya mengecek halaman itu, kirim URL-nya lewat halaman jasa SEO, dan saya balas dalam 24 jam. Terakhir dicek: 18 Oktober 2026. --- ## Kenapa halaman spam live streaming bisa muncul di Google, dan apa artinya untuk website bisnis URL: https://madebyaris.com/blog/halaman-spam-live-streaming-google Published: 2026-10-18. Updated: 2026-10-18. Pada 18 Oktober 2026, berita teratas untuk pencarian “leverkusen vs freiburg” di Google Trends Indonesia adalah halaman spam yang menawarkan live streaming laga Bundesliga itu, dengan judul penuh simbol aneh dan campuran kata Jerman. Pemilik website bisnis yang melihat hal seperti ini wajar bertanya kenapa halaman semacam itu bisa muncul dan apakah website mereka sendiri bisa ikut terkena dampaknya. ### Jawaban singkat Pada 18 Oktober, halaman spam itu menumpang pada pencarian laga yang baru ramai, dan Google sendiri pernah menulis bahwa untuk topik baru, informasi yang terbit paling awal belum tentu yang paling bisa diandalkan. Taktik seperti ini termasuk black hat SEO, yaitu cara mengejar ranking dengan melanggar aturan mesin pencari, dan kebijakan spam Google melarangnya. Untuk website kamu sendiri, risiko yang perlu dijaga adalah halaman spam yang ditaruh lewat celah keamanan, misalnya CMS versi lama yang tidak aman. ### Apa yang terlihat di Google Trends Di daftar pencarian yang sedang naik di Indonesia, “leverkusen vs freiburg” muncul dengan berita teratas berupa halaman yang menjanjikan siaran langsung pertandingan. Judulnya diawali deretan simbol seperti tanda seru, tanda dolar, dan kurung siku, lalu kata “Übertragung” dan “Livestream” dengan tanggal pertandingan di belakangnya. Saya sengaja tidak menautkan dan tidak menyebut nama situsnya. Judul seperti itu disusun untuk sistem pencarian. Kebijakan spam Google mencantumkan pola serupa sebagai spam, yaitu konten yang hampir tidak masuk akal bagi pembaca tetapi berisi kata kunci pencarian. ### Kenapa halaman spam bisa muncul untuk pencarian yang sedang ramai Untuk topik yang benar-benar baru, Google pernah menulis bahwa informasi yang terbit paling awal belum tentu yang paling bisa diandalkan. Tulisan dari 2021 itu membahas berita yang berkembang cepat dan tidak menyebut spam. ### Apakah ini termasuk black hat SEO? Ya, karena kebijakan spam Google memberi nama untuk beberapa pola yang cocok dengan halaman seperti ini. Berikut tiga yang paling dekat dengan kasus live streaming: - Konten massal (scaled content abuse): banyak halaman dibuat terutama untuk memanipulasi ranking pencarian, misalnya satu halaman untuk setiap laga dengan isi yang hampir sama. - Konten hasil peretasan (hacked content): konten yang ditaruh di sebuah situs tanpa izin pemiliknya, lewat celah keamanan. - Reputasi situs (site reputation policy): konten pihak ketiga yang di-publish di situs lain terutama untuk menumpang reputasi situs tersebut, pola yang juga disebut parasite SEO. ### Apakah website bisnis kamu bisa kena dampaknya? Dampak yang perlu kamu waspadai muncul ketika website kamu sendiri dipakai sebagai tempat menaruh halaman spam. Salah satu celah yang disebut Google adalah WordPress, Joomla! atau Drupal versi lama yang tidak aman. ### Cara melindungi website: cek halaman asing, akun admin, plugin, dan Search Console Cek empat hal berikut, dan semuanya bisa kamu kerjakan sendiri: - Halaman asing: cari site:domainkamu.com di Google, lalu perhatikan judul yang tidak pernah kamu tulis, terutama yang memakai kata streaming, slot, atau bahasa asing. - Akun admin: hapus akun yang sudah tidak dipakai dan ganti password yang lemah. - Plugin dan tema: update semuanya, dan hapus yang tidak aktif. Kalau website kamu memakai WordPress, risiko plugin saya bahas di kekurangan WordPress. - Search Console: buka laporan Masalah keamanan (Security issues) dan Tindakan manual (Manual actions), yang menampilkan temuan kalau Google menilai situs kamu diretas atau peninjau di Google menilai halaman kamu melanggar kebijakan. Untuk pengecekan teknis yang lebih lengkap, kamu bisa memakai checklist audit SEO teknis, dan untuk memantau posisi setelah ada perubahan, ada catatan tentang cara saya mengecek ranking setelah rilis. ### Cara melaporkan halaman spam ke Google Google punya halaman untuk melaporkan masalah kualitas yang mengarahkan kamu ke form terpisah untuk halaman spam, malware, dan phishing. ### Pertanyaan yang sering ditanyakan #### Apa itu parasite SEO? Parasite SEO adalah sebutan umum untuk konten yang ditaruh di situs lain yang sudah punya reputasi supaya konten itu ikut naik di Google. Di halaman kebijakan spamnya, Google memakai nama kebijakan reputasi situs dan tidak lagi memakai label lama “site reputation abuse”. Halaman yang sama juga mencatat perubahan khusus untuk Kawasan Ekonomi Eropa (EEA), jadi baca versi terbarunya kalau website kamu melayani pengunjung di sana. #### Bagaimana cara mengetahui website kamu diretas atau melanggar kebijakan spam? Buka dua laporan yang selalu tersedia di Search Console, yaitu Masalah keamanan (Security issues) dan Tindakan manual (Manual actions), setiap kali kamu menemukan judul asing di hasil site:. Selama tidak ada masalah, kedua laporan itu tidak berisi temuan. Kalau laporan Masalah keamanan berisi temuan, minta developer kamu memeriksa satu celah lain yang disebut di halaman bantuannya, yaitu direktori yang tidak aman di server. #### Bagaimana cara melaporkan halaman spam ke Google? Mulai dari halaman pelaporan masalah kualitas, lalu pilih form yang sesuai, karena Google memisahkan laporan untuk halaman spam, malware, dan phishing. Jangan sertakan data pribadi apa pun di laporan, karena Google meminta hal itu dan menjelaskan bahwa isi laporan bisa diteruskan ke pemilik situs yang kamu laporkan. Halaman kebijakan spam Google juga menautkan form laporan pengguna untuk kualitas pencarian, jadi kamu bisa masuk dari salah satu halaman itu. #### Kenapa judul halaman spam terlihat berantakan? Judul itu berisi deretan simbol, campuran bahasa, tanggal laga, dan kata kunci pencarian yang ditumpuk tanpa membentuk kalimat. Kamu bisa memakai ciri ini untuk mengenali spam sebelum mengeklik, yaitu judul yang diawali simbol seperti tanda seru dan tanda dolar, kata dari bahasa yang tidak cocok dengan negara pencarian, dan janji siaran langsung. Pada kasus 18 Oktober, ketiga ciri itu muncul sekaligus di satu judul. ### Penutup Halaman spam di pencarian yang ramai berada di luar kendali kamu, sedangkan celah di website sendiri bisa kamu tutup. Cari site: dengan domain kamu di Google dan baca setiap judul yang muncul. Kalau ada judul asing dan kamu butuh bantuan menelusurinya, kirim URL website kamu lewat halaman jasa SEO, dan saya balas dalam 24 jam. Terakhir dicek: 18 Oktober 2026. --- ## Cara membuat halaman jadwal dan hasil pertandingan yang ramah SEO dengan Next.js URL: https://madebyaris.com/blog/halaman-jadwal-pertandingan-nextjs Published: 2026-10-18. Updated: 2026-10-18. Borneo FC memainkan laga debutnya di AFC Challenge League (ACGL) melawan Yangon United di Stadion Segiri, Samarinda, pada Minggu, 18 Oktober 2026 pukul 20.00 WITA atau 19.00 WIB, sesuai jadwal di website resmi klub. Kalau klub atau turnamen kamu membagikan jadwal hanya sebagai gambar di grup WhatsApp atau sebagai satu file PDF, Google tidak punya halaman untuk setiap pertandingan yang bisa diberi data terstruktur dan diperbarui dengan mudah. ### Jawaban singkat Struktur yang ramah SEO cukup terdiri dari satu halaman daftar dan satu halaman untuk setiap pertandingan, dengan data yang diambil dari satu file supaya tidak ada dua versi jadwal. Setiap halaman pertandingan diberi JSON-LD SportsEvent, yaitu data terstruktur yang menjelaskan siapa bertanding, kapan, dan di mana. Setelah halaman live, hasilnya dicek di Rich Results Test dan Search Console. ### Hasil akhir: halaman jadwal yang bisa dibaca Google Hasilnya berupa satu halaman daftar jadwal dan hasil, ditambah satu URL untuk setiap pertandingan dengan judul, tempat, dan waktu dalam bentuk teks biasa. Data yang dipakai adalah data contoh (fiktif), yaitu liga “Liga Contoh” dengan tim “Tim A FC” sampai “Tim H FC”. Saya membangun demo ini dengan bantuan AI coding agent, lalu hasilnya saya cek sendiri. Di tutorial ini kita tidak membuat skor live yang berubah tanpa reload. Untuk kebutuhan itu, saya sudah menulis scoreboard sepak bola live dengan Next.js, dan halaman jadwal di sini bisa menjadi pasangannya. ### Yang kamu perlukan Demo ini dibuat dengan Next.js 16.4.2 (App Router), React 19.3.0, dan Tailwind CSS v4, jadi kamu perlu Node.js yang bisa menjalankan versi Next.js itu, editor kode, dan sedikit pengalaman dengan App Router. Kalau App Router masih terasa baru, baca dulu App Router dalam praktik. ### Langkah 1: simpan data pertandingan di satu tempat Semua halaman membaca data dari satu file JSON berisi daftar pertandingan, lewat fungsi kecil seperti getAllMatches() dan getMatchBySlug(), sehingga perubahan jadwal cukup ditulis sekali dan muncul di halaman daftar maupun di halaman pertandingan setelah build berikutnya. Halaman-halaman itu tidak memanggil API atau database. Cuplikan data pertandingan (JSON), 2 dari 8 pertandingan: ``` [ { "slug": "tim-a-fc-vs-tim-b-fc-pekan-1", "matchday": 1, "homeTeam": "Tim A FC", "awayTeam": "Tim B FC", "status": "finished", "homeScore": 2, "awayScore": 1, "kickoff": "2026-10-12T15:30:00+07:00", "venue": "Stadion Contoh Utara, Jakarta" }, … { "slug": "tim-a-fc-vs-tim-c-fc-pekan-2", "matchday": 2, "homeTeam": "Tim A FC", "awayTeam": "Tim C FC", "status": "scheduled", "kickoff": "2026-10-25T19:00:00+07:00", "venue": "Stadion Contoh Utara, Jakarta" }, ] ``` Laga yang sudah selesai punya homeScore dan awayScore, sedangkan laga yang belum dimainkan tidak punya kolom skor, dan kickoff selalu membawa zona waktu (+07:00). ### Langkah 2: buat halaman daftar jadwal dan hasil Halaman daftar ada di /jadwal dan mengelompokkan pertandingan per pekan, dengan judul “Pekan 1”, “Pekan 2”, dan seterusnya, lalu setiap kartu menampilkan “Selesai” beserta skornya atau “Akan main” beserta jam kick-off WIB. Semua isi ditulis sebagai teks HTML, sehingga setiap baris jadwal bisa dibaca, disalin, dan diperbarui tanpa membuat gambar baru. Di halaman yang sama, demo juga menaruh satu tag script berisi JSON-LD untuk kedelapan pertandingan. Google sendiri menyarankan markup event dipasang di halaman setiap event daripada di halaman yang berisi daftar jadwal, jadi markup yang penting ada di halaman pertandingan pada langkah berikutnya. app/jadwal/page.tsx: ``` export default function JadwalPage() { const matches = getAllMatches(); const byDay = groupMatchesByMatchday(matches); const jsonLd = matches.map((m) => sportsEventJsonLd(m)); return ( <>