Website Speed Test

Simple step-by-step speed test

1. Enter the full URL of the page you want to test, such as your home page or a specific landing page.
2. Optionally, set a render budget in seconds, which determines how much time the tool will spend trying to render the page.
3. Check or uncheck the additional rendering test option if you are only interested in raw server speed.
4. Click the run speedtest button and wait for the tool to perform the measurement and generate the report.
5. View a summary with load time, TTFB, page size and optimization suggestions.

The entire process usually takes only a few moments, so you can test multiple URLs, compare page versions after changes, and constantly monitor how your site is performing in terms of loading speed.

What information will the speedtest report show

• HTTP status and whether the page responds correctly or returns a 404 or 500 error, for example.
• The total page load time in seconds, calculated from the time of invocation until the download is completed.
• TTFB, or time to first byte, which shows how quickly the server starts sending the response.
• The approximate size of the downloaded page in kilobytes or megabytes, useful for analyzing heavy graphics.
• Average download speed in megabits per second, which helps you understand network limitations.
• An overall speed rating, divided into fast, okay or slow, with simple scoring.
• Approximate FCP and LCP metrics based on collected data that resemble PageSpeed ​​reporting.

Thanks to this, even a person who is not professionally involved in server administration or frontend can quickly find out whether the website requires optimization, and if so, in what area it is best to start making corrections.

What exactly does website speedtest measure

• Measures DNS and server connection time, which helps detect network infrastructure problems.
• TTFB calculation that clearly shows the health of the backend and application server configuration.
• The total page download time, which is the sum of server operation and resource size.
• The page size, which reveals whether graphics, CSS, JS and other elements are not too heavy.
• Download speed estimation, especially useful when analyzing media-rich sites.
• Approximate FCP and LCP that help understand when the user first sees the content and when the page appears to be fully loaded.

All this data is presented in one, clear report, which you can use as a basis for working on improving performance or as a quick benchmark after implementing changes to the website.

Time Budget Rendering Test

The optional rendering test uses a time budget that you set in seconds to simulate a situation in which the browser has a set amount of time to render a page, making it easier to see if heavy JavaScript, heavy CSS, or dynamic components are blocking content from appearing to the user.

If the rendering test is successful, the report will show information about the time needed to process the page and what budget was used, while in case of problems, the tool will show a message that the rendering could not be performed, which is also a signal that it is worth taking a look at the configuration of the environment and frontend.

Images and page size

• Check that the page is not several megabytes, especially if most of the weight is made up of large photos.
• Implement image compression and modern formats like WebP or AVIF to reduce size without losing quality.
• Use lazy loading for images at the bottom of the page so as not to block the first view.
• Remove unused banners, galleries and decorative elements that add a lot of weight to the page.

Every few hundred kilobytes less in the main view can noticeably speed up loading, especially on mobile connections.

Frontend, Scripting and CSS

• Verify that you are not loading several JavaScript libraries just to perform simple effects on the page.
• Combine and minify stylesheets and scripts to reduce the number of requests and their size.
• Move heavy scripting to the bottom of the document or use thedeferandasyncattributes when possible.
• Remove unused components and styles left from old modules or outdated templates.

Often it is the front end, not the server, that is the main cause of the website's perceived slowness in the eyes of the user.

Server, Cache and TTFB

• Pay special attention to TTFB, as a slow time to the first byte usually indicates a problem on the backend side.
• Use an application cache or reverse proxy to speed up the generation of repetitive subpages.
• Check that the database is not running too slowly, for example due to missing indexes or large, suboptimal queries.
• Consider upgrading your server or changing hosting if even simple sites take a long time to respond.

Even the most optimized frontend won't help if the server needs a few seconds to generate a basic response.

Network, CDN and mobile users

• If your website has users from all over the world, consider implementing a CDN to shorten the physical distance between the server and the recipient.
• Remember that mobile users often use unstable networks, so any savings in page size make a huge difference.
• Keep cache headers long for static resources to make subsequent visits much faster.
• Repeat the tests at different times of the day, as network infrastructure overload may affect the results.

Thanks to such activities, the website speedtest will show better and better results over time, and real users will feel a significant improvement in the comfort of using the website.