Largest Contentful Paint
How quickly the main visible content appears.
Look at: hero images, server response, critical Cascading Style Sheets (CSS), fonts and render-blocking resources.
A practical guide to understanding website speed, accessibility, security and quality. Learn what to measure, how to investigate the results and what to improve.
Website performance is the quality of the experience while a page loads and responds. It is not just “how fast the homepage opens” and it is not a single Lighthouse score.
Looks at loading speed, responsiveness, visual stability, page weight, browser work, server response and caching.
Checks Hypertext Transfer Protocol Secure (HTTPS)/Transport Layer Security (TLS), security headers, software maintenance, unsafe configuration, exposed information and basic browser protections.
Checks keyboard use, semantics, contrast, labels, zoom, screen-reader support and other Web Content Accessibility Guidelines (WCAG)-related barriers.
Includes broken links, Search Engine Optimisation (SEO)/indexing, analytics, console errors, forms, responsive behaviour, content quality and third parties.
Users experience a sequence: something appears, the page becomes understandable, controls respond, and the layout stays stable. Every avoidable delay or jump adds friction. Our job is to measure that experience, identify the cause, and recommend a proportionate fix.
The browser has to find the server, establish a secure connection, download resources, build the page and run code before the user can fully interact.
A site can load quickly but still feel poor if buttons lag, content jumps around, or a huge script locks the browser. That is why a good audit uses multiple signals.
How quickly useful content becomes visible. Largest Contentful Paint (LCP) is one key signal.
How quickly the page reacts after a click, tap or key press. Interaction to Next Paint (INP) is the Core Web Vital.
Whether content unexpectedly shifts while the user is reading or trying to interact. Cumulative Layout Shift (CLS) measures this.
How much data and how many resources the browser has to download and process.
Response time, caching, compression, Content Delivery Network (CDN) behaviour and connection overhead.
How much JavaScript, layout and rendering work occupies the browser and delays interactions.
Use several types of evidence together. Automated tools are quick and repeatable; real-user data and manual investigation tell you whether the problem is genuine and why it happens.
A performance score without context is hard to reproduce. Test representative page types, capture the device and test state, and compare like-for-like.
Homepage, landing page, content page, search/form, and any heavy or interactive page.
Mobile is usually the stricter baseline. Repeat on desktop for comparison.
Record anonymous/logged-in state, cookie banner, Virtual Private Network (VPN)/location and whether cache is cold.
Lab results vary. When practical, run 3 times and use the median rather than the best result.
Save screenshots, the Lighthouse report, URLs and the issues that explain the score.
Lighthouse is an automated lab audit. Use it to spot performance opportunities and broader quality signals, then investigate the underlying cause.
Core Web Vitals focus on loading, responsiveness and visual stability. For field assessment, Google evaluates the 75th percentile of page visits.
How quickly the main visible content appears.
Look at: hero images, server response, critical Cascading Style Sheets (CSS), fonts and render-blocking resources.
How quickly the page responds after a user interacts.
Look at: long JavaScript tasks, event handlers, rendering work and heavy third-party code.
Whether content unexpectedly moves while the page is loading.
Look at: missing image dimensions, late banners, font swapping and injected content above existing content.
Lab data is a controlled test on one run. It is excellent for debugging, but it is not the same as what every real user experiences.
Lighthouse / DevToolsA Lighthouse result is a clue. Use the Network and Performance panels to understand what actually delayed the page or blocked an interaction.
Check request count, transferred size, Time to First Byte (TTFB), blocking, large assets, third parties, caching and compression.
Record an interaction and look for long main-thread tasks, scripting bursts, rendering and layout work.
These checks identify common configuration and maintenance risks. Anything intrusive, authenticated or exploit-focused should follow an authorised security testing process.
A useful audit also looks for accessibility barriers, broken functionality, poor indexing, tracking problems and content issues. Performance should not be assessed in isolation.
Pick a safe test website or one of our own non-production environments. Complete the checklist and be ready to explain one high-priority finding and the evidence behind it.
Do not try to find the worst score. Find a meaningful user or risk issue, gather evidence, and describe a practical remediation.
Our report should explain what happened, why it matters and what should be done next. The score is evidence, not the recommendation.
What is happening? Be specific – page, component, asset or configuration.
Metric, screenshot, waterfall, console entry, header result or repeatable steps.
Who is affected and how – speed, usability, search visibility, reliability or security risk.
What should change, who likely owns it, and whether it needs development, content or hosting support.
Blocks users, exposes material security risk, or has strong measurable impact. Fix now.
Meaningful degradation or hygiene gap. Plan into the next remediation cycle.
Needs field data, trend monitoring or confirmation after a deployment.
Polish or low-impact improvement. Do not let it distract from user-impact work.