Your page size can be significantly reduced.

Page size shows how big your page is, including all elements like JavaScript, CSS, images, etc. Apart from directly affecting page speed and user experience, page size is an important ranking factor. Make sure your page loads quickly and doesn't include too many components that can increase its load time.

Your server response time could be improved. Look into possible causes (slow application logic, slow database queries, slow routing, frameworks, libraries, resource CPU starvation, memory starvation) and try to fix them.

Server response time is an important user experience factor, as it contributes to the page's overall load speed.

Good job! Your page has no redirects, or there is only one redirect that doesn't slow the page down.

Too many redirects can significantly increase your page's load time, thus negatively impacting user experience.

Congratulations! The size of compressible resources on your page is minimized properly.

GZIP compression of text resources (HTML, JavaScript, CSS) can significantly reduce page size and improve page speed. GZIP compression is configured on the site's server and applied to all site's resources.

There are uncompressed images on your page. Compressing them will save you 18.3 KB (8% of page size) with no drop in image quality, which will ensure that the page loads quicker.

Using uncompressed images or images with unnecessarily high resoultion on your pages will have a negative impact on page speed. Optimizing images can yield the largest byte savings and performance improvements. Using PNG and JPEG formats for photos and GIF for smaller images is recommended. Using CSS sprites also helps improve page speed, as it reduces the number of images the browser has to load.

There are static resources on your page that are not being cached or are only being cached for a short time. To make sure resources are cached properly, configure caching on your server (it will be applied to all site resources).

Browser caching is an important page speed factor. Caching makes the page load faster when the user revisits it, and speeds up the loading of the site's other pages that use the same resources.

Some resources on your page are not minified. Minifying those will let you save 19.4 KB (9% of current page size) and improve page speed. You can download an archive with your page's JavaScript and CSS readily minifed here: https://developers.google.com/speed/pagespeed/insights/optimizeContents?url=http://www.last.fm/events&strategy=desktop.

Minifying resources means getting rid of unnecessary spaces, empty lines, and line breaks in the page's HTML, JavaScript, and CSS. Optimizing resources in this way results in improved page speed.

There is render-blocking JavaScript and/or CSS on your page that affects the load time of the above-the-fold part of your page.

This factor shows whether there are JavaScript or CSS issues on your page. The JavaScript code and CSS resources used for loading the above-the-fold part of your page need to be inlined, while the scripts and styles that are not critical to initial render should be performed after the first render.

The above-the-fold part of your page is not fully optimized. After the HTML code of the page is loaded, only 33% of the content of the above-the-fold portion of the page is displayed.

Prioritizing the above-the-fold part of your page ensures that the page's visible portion loads quickly. If large amounts of data are required to load the page's above-the-fold portion, additional round trips between your server and the user's browser will need to be made.

Well done! Your viewport meta tag is configured properly, and the part of the page defined by it adapts well to different screen sizes. This means that your page is user-friendly on any device.

A viewport controls how a webpage is displayed on mobile devices. Without a viewport, mobile browsers will render the page at a typical desktop screen width, scaled to fit the device's screen size. This will likely lead to readability and navigation issues on mobile devices.

Congrats! The font size and line height on your page make your text easy to read on mobile devices.

This factor shows whether there is text on your page that can be hard to read due to its small size. This can occur if the page hasn't been optimized for mobile devices (e.g. there is no viewport tag on the page, or the viewport is configured to use a fixed width). As a result, mobile browsers will automatically scale the page to fit the screen, making the text smaller and harder to read.

Some of the tap targets on your page are too small and/or tightly packed. These links and buttons can be hard to click on touchscreen devices.

Tap targets are elements on your page that you expect users to click on, such as links and buttons. Small or tightly packed tap targets are difficult to press on touchscreen. This can occur if the page hasn't been adjusted for mobile devices (e.g. the viewport meta tag is missing or not configured properly). As a result, mobile browsers will automatically scale the page to fit the screen, making page elements and the space between them smaller.

Good job! Your page adapts to different screen sizes well, with all its elements fitting within the viewport. There is no horizontal scrolling on the page.

Page content that falls outside the viewport is content that does not fit the user's screen width, thus forcing the user to scroll horizontally to view it.

No plugins are used on the page, so its content is equally accessible to all users browsing your site from mobile devices.

Plugins help browsers process certain types of web content, such as Flash, Silverlight, and Java. Most mobile devices do not support plugins; in those that do, plugins are a leading cause of hangs, crashes, and security incidents. Desktop browsers are also restricting plugins increasingly.