16 questions on performance, each with an explanation. Free, no signup.
Page speed is a ranking factor, a conversion factor and the thing most audits flag first. This track tests the mechanics behind a fast page: what the browser has to download before it can paint, which resources block rendering, and which optimisations actually move the numbers.
Questions range from the basics (what a CDN does, why images are compressed) to the techniques a performance engineer uses (preloading, priority hints, lazy hydration, HTTP/2 multiplexing).
This track has 16 questions. Learning mode asks 10 at a time with the explanation after every answer; the timed challenge asks 16 in 100 seconds. Free, no signup, and a different draw every time you retake it.
8 of the 16, with the answer and the explanation hidden until you open each one.
Answer: B. Lazy loading defers loading of non-critical resources (like images below the fold) until they're needed, improving initial page load time and Core Web Vitals.
Answer: D. A CDN (Content Delivery Network) distributes your content across multiple servers worldwide, serving files from the location nearest to users for faster load times.
Answer: B. Browser caching stores static files locally on users' devices, so they don't need to be downloaded on repeat visits, significantly improving load times.
Answer: B. TTFB should ideally be under 600ms. It measures the time from the request to when the first byte of the response is received. Good server performance is crucial for TTFB.
Answer: B. WebP is a modern image format developed by Google that provides superior lossless and lossy compression. WebP images are typically 25-35% smaller than JPEGs, improving page load times.
Answer: A. The critical rendering path is the sequence of steps the browser goes through to convert HTML, CSS, and JavaScript into pixels on the screen. Optimizing it improves page load performance.
Answer: D. HTTP/2 improves performance through multiplexing (multiple requests per connection), header compression, and server push. This results in faster page loads compared to HTTP/1.1.
Answer: B. Priority hints (importance attribute) let developers indicate resource priority to browsers. Values like 'high', 'low', or 'auto' help browsers make better loading decisions for optimal performance.
The full SEO quiz draws from all 93 questions. Or pick a topic:
Page Audit scores one URL on performance, SEO, accessibility, best practices and security with the elements responsible for each issue. Free account, no card. The AI Access Checker and the Schema Validator need no account at all.
Run Page Audit