MyJackfruit

Help
Browse topics · Development

Development

← Back to Do big pictures and videos make my app slow?

How do I make sure my app is fast, and how do I measure it?

Short answer

A written speed rule tells your AI to measure; once it is live, check it yourself with PageSpeed Insights or Lighthouse.

Deeper

No one can promise how fast your app will be for every person: it also depends on their device and their connection. What you can do is have it measured, before and after each change, and check it yourself once it is live.

What GilbPlatform gives today. When your app goes live, at https://<name>.pages.dev, a web address of its own, where <name> is the name given to your site, its files are served by Cloudflare, a web company. Cloudflare says its pages service "comes with built in caching defaults that are optimized for caching as much as possible", that is, it keeps copies of your files ready to send, and that it will also serve Gzip and Brotli responses whenever possible, files packed smaller for the trip (https://developers.cloudflare.com/pages/configuration/serving-pages/, read 13 November 2026). What your app reads from vaults, the places where records are kept, comes from GilbPlatform's servers. GilbPlatform and GilbApp have no speed check and no speed report for your app.

What your AI does. Agent.Coder, the agent that writes your app's code, follows a written speed rule whenever it builds or speeds up a screen, a list or anything a person waits on. An agent is your AI following one written procedure, its standing instructions, for one kind of work. The rule counts the seconds from when a person does something to when the screen shows what they expect. When your plan names no speed, it aims for 0.3 seconds and accepts at most 1 second. It is to measure on the live address, on a phone as well as a computer, and to fill in a table before and after each change; a speed claim without that table does not count. The same rule asks the app to show a screen you have seen in the same visit at once and check for changes behind it, to read only what changed, to show at once that it is updating, and to be built for a phone on a mobile network first. The rule's own status note (29 October 2026) says it is the target, not a result, and that none of it was measured on a phone yet. A written rule does not make your app fast; the table and your own check do. Ask your AI to show you its speed table.

Measure it yourself, once it is live. Your app on your own computer is not the live app, so measure the live address.
- PageSpeed Insights, a page at Google: open https://pagespeed.web.dev, type your app's address and start the check. Google says it reports on the user experience of a page on both mobile and desktop devices. It shows lab data, measured in a test (useful for debugging issues), and field data from real visits (useful for capturing true, real-world user experience), which a new site may not have yet (https://developers.google.com/speed/docs/insights/v5/about, read 13 November 2026).
- Lighthouse, a check built into the Chrome browser: open your app in Chrome, open DevTools, Chrome's tools for looking inside a page, choose the Lighthouse tab, press Analyze page load, then press Run audit, and wait about 30 to 60 seconds for the report (https://developer.chrome.com/docs/lighthouse/overview, read 13 November 2026).

Google names three numbers as good, for most of your visitors (it measures the 75th percentile of page loads) (https://web.dev/articles/vitals, read 13 November 2026): the biggest part of the page shows within 2.5 seconds; the page answers a tap or a click within 200 milliseconds; and the page does not jump about while it loads (a score of 0.1 or less).

If a number is poor, send it to your AI with the address you checked; the answer Why is my app slow, and is it slower on phones or a weak connection? tells what to say. Pictures can be a cause; see Do big pictures and videos make my app slow? How your app goes live is in How do I put my app or website live on the internet?

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (Contextual: read Rule_Code_gilb-app-speed when building or speeding up anything the person waits on; AskGoLive), Rule_Code_gilb-app-speed (seconds from the act to the expected screen, on the real host, phone and computer; 0.3 s aimed for and 1 s at most when the spec names no speeds; RuleAppspeedMeasureFirst: the table before and after, a claim without it is not evidence; RuleAppspeedPaintFromMemory, RuleAppspeedChangesOnly, RuleAppspeedVisibleWait, RuleAppspeedPhoneFirst), Rule_Code_deployment (RuleDeployPagesDev: https://<name>.pages.dev). Cloudflare, Serving Pages (https://developers.cloudflare.com/pages/configuration/serving-pages/, read 13 November 2026). Google, About PageSpeed Insights (https://developers.google.com/speed/docs/insights/v5/about, read 13 November 2026). Chrome, Lighthouse overview (https://developer.chrome.com/docs/lighthouse/overview, read 13 November 2026). web.dev, Web Vitals (https://web.dev/articles/vitals, read 13 November 2026). Live help pages, sentences shared: How do I put my app or website live on the internet?; Can I try my app on my phone?; How can I see what I've built?

Checked against GilbApp d529620.