Enter your details below, we'll send you a free website performance report
You are permitted to generate up to 3 free reports per hour.
You have 3 credits remaining.
Require more credits?
Contact us to discuss your requirements.
The report process usually takes less than 30 seconds.
Page speed rating
Resources size in kilobytes
You don't have report credits, pls come back on or Contact us to discuss your requirements.
The report will check the following metrics
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network. This can typically be applied at the web server level, for example using NGINX compression options.
Render means loading. Therefore if something is described as render-blocking it means that it stops the page from loading as quickly as it could. Your Google search ranking is at risk if you do not optimise for this. If Google observes that your web page does not load quickly for certain devices (such as phones, iPads, etc.) there is a chance they will drop your website from the results listing. Google's policy is to not send users to slow pages, or pages where the user has to wait too long to download the content.
Properly formatting and compressing images can save many bytes of data. This can be achieved with NGINX compression options, but is also supported in other caching and web servers.
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Minification refers to the process of removing unnecessary or redundant data without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on.
Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single roundtrip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance.
If the amount of data required exceeds the initial congestion window (typically 14.6kB compressed), it will require additional round trips between your server and the user's browser. For users on networks with high latencies such as mobile networks this can cause significant delays to page loading.
Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. There may be variance from one run to the next, but the differences should not be too large. In fact, highly variable server response time may indicate an underlying performance issue.
Looking for help or have questions about optimising your website?