Skip to content

Building Web & Apps

A hands-on guide to building and running your own websites and apps, in the order the work actually happens. We cover choosing a domain and a server, measuring how fast a page opens in different countries, getting found in search and adding ads, and the steps for publishing an app to the stores.

This is also home for small tool-style sites people use for a moment and leave - so-called low-involvement web and apps. We look at how to ship one feature quickly, how to bring visitors back, and which choices keep running costs down, with real examples. Trends in generative AI technology and industry live in "AI & Development"; here we stay with what you run into when you build and operate things yourself.

Things you can check with numbers, such as speed, search visibility and running costs, come with how to measure them and how to read the results, along with case notes on improving small tools step by step.

Site Speed by Country

See how fast your site responds from many countries at once. Each country shows DNS, connect, TLS and time to first byte, plus the response status.

Example: measure https://example.com from Korea, Japan and the US to see each country's time to first byte and which step is slow.

Site Speed by Country

Pick an address and countries, and public measurement points in those countries send the same request and time it. Members only, with a daily allowance.

Loading…

How it measures

  • Tests are run by measurement points of the public network Globalping in each country. Our server only creates the test and collects the results; it never requests the target site itself.
  • First byte adds up DNS lookup, connecting, TLS negotiation and the server's wait; total also includes downloading the body. You can compare which step is slow in each country.
  • 3 runs measure three times from the same points and show the median of each value. The first request can be slower because DNS and connections start cold.
  • Limits are counted in measurement points (countries x runs). Only what the network actually ran is counted, and points that were offline are returned.
  • Only tests you choose to share appear on the site page, without your name. Each member keeps the 20 most recent tests for 30 days.
  • This test cannot tell how fast a page renders (FCP, LCP) or how long images and scripts take to load.

Loading related content.

Public test records

Tests members chose to share. Who ran them is not shown, and the part of the address after ? is removed.

Loading…

Public test

Loading…