What Is GTmetrix?
GTmetrix is a free page speed testing tool that analyses website performance using Lighthouse, reporting on Core Web Vitals, load times, and specific optimisation recommendations.
Last reviewed: 18 August 2026 · Reviewed by iNet Ventures Technical SEO Team
In plain English
You type in a URL and GTmetrix loads the page in a real browser, measuring how long it takes, how big each file is, and what is slowing it down. It gives you a performance score and a list of specific things to fix — compress images, minify CSS, reduce server response time. It is one of the standard tools SEOs and developers use to check whether a site is fast enough for Google's Core Web Vitals.
Technical definition
GTmetrix is a web-based performance testing platform that runs Google Lighthouse audits against a target URL and presents the results with additional context including waterfall charts, video playback of page loading, and historical performance tracking. It measures Core Web Vitals (LCP, CLS, INP), page load time, total page size, request count, and provides prioritised recommendations based on Lighthouse audit results. The free tier allows testing from one location (Vancouver, Canada) with limited options. Paid plans add multiple test locations, monitoring, and alerting.
Quick example
A client's site is loading slowly. Enter the URL into GTmetrix, select mobile testing, and the report shows a 4.2-second LCP (should be under 2.5s), a CLS of 0.15 (should be under 0.1), and three specific recommendations: serve images in next-gen formats, eliminate render-blocking resources, and minify JavaScript. Each recommendation includes the estimated savings — fixing the images alone would save 1.8 seconds.
Quick facts
| Meaning | A page speed and Core Web Vitals testing tool built on Lighthouse |
|---|---|
| Main category | Technical SEO and performance testing tools |
| Used by | SEO agencies, web developers, site owners, technical SEOs |
| Difficulty | Beginner |
| Importance | High |
| Common examples | Core Web Vitals testing, page speed audits, performance monitoring, waterfall analysis |
| Still relevant? | Yes. GTmetrix remains one of the most popular page speed testing tools. Since adopting Lighthouse as its engine, its recommendations align with Google's own performance standards. The free tier is sufficient for most one-off audits. |
Why GTmetrix matters
GTmetrix matters because page speed is a confirmed Google ranking factor, and Core Web Vitals are part of Google's page experience signals. If your site is slow, it ranks lower, converts worse, and provides a poor user experience. GTmetrix tells you exactly what to fix.
Core Web Vitals are ranking factors
Google uses LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint) as page experience signals. GTmetrix measures all three and tells you whether your pages pass or fail Google's thresholds.
Recommendations are specific and prioritised
GTmetrix does not just say "your site is slow." It tells you exactly what to fix — which images are too large, which CSS files are render-blocking, which JavaScript is unnecessary — and estimates the time savings for each fix. This gives developers an actionable work list.
The waterfall chart shows what loads when
The waterfall visualisation shows every request the browser makes, in order, with timing for DNS resolution, connection, download, and rendering. This is essential for diagnosing complex performance issues — like a third-party script blocking the entire page render.
Video playback shows what users experience
GTmetrix records a video of the page loading and shows a filmstrip of frames at intervals. You can see exactly when the first content appears, when layout shifts happen, and when the page becomes interactive. This is more intuitive than reading timing data alone.
Historical tracking shows whether fixes work
Paid plans include monitoring — GTmetrix tests your pages on a schedule and tracks performance over time. After implementing fixes, you can see whether scores improve and whether performance degrades over time as new content is added.
How it works
GTmetrix runs a Google Lighthouse audit against your URL in a controlled browser environment and presents the results with additional analysis.
- 1
You enter a URL and configure the test
Specify the URL, browser (Chrome or Firefox), device (desktop or mobile), connection speed, and test location. These settings affect the results — a mobile test on a 3G connection from London will show very different performance than a desktop test on cable from Vancouver.
- 2
Lighthouse runs in a controlled environment
GTmetrix loads the page in a real browser with Lighthouse enabled. Lighthouse performs a series of audits measuring performance, accessibility, best practices, and SEO. The browser records timing for every request and rendering milestone.
- 3
Core Web Vitals are measured
LCP (when the largest visible element renders), CLS (how much the layout shifts during loading), and INP (how quickly the page responds to user interaction) are measured from the actual page load. These are the same metrics Google uses.
- 4
Recommendations are generated
Lighthouse identifies performance issues and estimates the time savings for each fix. GTmetrix presents these in priority order — the fixes that would save the most time appear first.
- 5
Results are presented with visualisations
The report includes a waterfall chart (request-by-request timing), a video filmstrip (visual loading progress), and a summary of scores and metrics. Each recommendation links to detailed guidance on how to implement the fix.
Types and variations
GTmetrix is described by its key features and report sections.
Performance Report
The main report. Shows Lighthouse performance score, Core Web Vitals (LCP, CLS, INP), page load time, total page size, and request count. Includes prioritised recommendations with estimated savings.
Waterfall Chart
A visual timeline of every request the browser makes — DNS, connection, SSL, download, and rendering. Essential for identifying which requests are slow and which are blocking others.
Video Filmstrip
A series of screenshots showing how the page loads over time. You see when content first appears, when layout shifts happen, and when the page becomes visually complete.
Recommendations
A prioritised list of performance fixes based on Lighthouse audits. Each recommendation includes the audit name, the estimated time savings, and a link to detailed implementation guidance.
Structure Analysis
Shows the DOM size, page weight breakdown by content type (HTML, CSS, JS, images, fonts), and request count by type. Useful for understanding what is contributing to page weight.
Monitoring (Paid)
Scheduled testing that tracks performance over time. Includes daily or hourly tests, alerting when scores drop below a threshold, and historical performance graphs.
Lighthouse Structure
Since GTmetrix adopted Lighthouse as its engine, its audits and recommendations align with Google PageSpeed Insights. This means GTmetrix recommendations are the same ones Google would make.
Real examples
How GTmetrix gets used in practice.
Diagnosing a slow-loading product page
A product page takes 6 seconds to load on mobile. GTmetrix shows LCP at 4.8 seconds — the hero image is 2.3MB unoptimised. The recommendation says "serve images in next-gen formats" with an estimated saving of 2.1 seconds. Convert the image to WebP, retest, and LCP drops to 2.7 seconds — now passing Google's threshold.
Identifying a third-party script problem
A site's CLS score is 0.25 (well above the 0.1 threshold). The waterfall chart shows a chat widget script loading late and causing layout shifts. The video filmstrip confirms — the page renders, then shifts when the chat widget appears. Deferring the script load or reserving space for it fixes the CLS.
Testing only from the default Vancouver location
Running all tests from the default Vancouver location when your customers are in London. Network latency and CDN routing differ by location — a page that loads in 2 seconds from Vancouver might take 4 seconds from London. Always test from a location that matches your audience.
Chasing a perfect score instead of fixing real issues
Spending hours optimising to get the GTmetrix score from 92 to 100 when the Core Web Vitals already pass. The score is a summary — what matters is whether LCP, CLS, and INP pass Google's thresholds. A score of 85 with passing Core Web Vitals is better than a score of 95 that required removing functionality.
Best practices
GTmetrix is most useful when you test the right pages, from the right locations, and focus on the metrics that matter.
What to do
- Test from a location that matches your primary audience — not just the default
- Always test mobile separately — mobile performance is typically worse and more important
- Focus on Core Web Vitals (LCP, CLS, INP) — these are what Google measures
- Use the waterfall chart to identify blocking requests and slow third-party scripts
- Test your most important pages — homepage, top product pages, top blog posts — not just the homepage
- Re-test after implementing fixes to verify the improvement
- Use monitoring (paid) for ongoing tracking if you make frequent content changes
What to avoid
- Testing only from the default location when your audience is elsewhere
- Testing only desktop — mobile performance is typically the bigger problem
- Chasing a perfect score when Core Web Vitals already pass
- Ignoring the waterfall chart — it shows exactly what is slow
- Testing only the homepage — inner pages are often slower due to heavier content
- Treating lab data as field data — GTmetrix is a lab test; also check CrUX data in PageSpeed Insights
Common mistakes
Confusing lab data with field data
GTmetrix runs a simulated test in a controlled environment (lab data). Google's Core Web Vitals assessment uses real user data from the Chrome User Experience Report (field data). A page can pass in GTmetrix but fail in Google's field data, or vice versa. Check both — GTmetrix for diagnosing issues, PageSpeed Insights for Google's actual assessment.
Testing only from the default location
GTmetrix's free tier tests from Vancouver, Canada. If your customers are in Europe or Asia, the results do not reflect their experience. Network latency, CDN routing, and server distance all affect load time. Always test from a location that matches your audience, even if it requires a paid plan.
Ignoring mobile testing
Desktop performance is typically much better than mobile — faster CPUs, more memory, broadband connections. Mobile performance is what Google uses for mobile-first indexing and what most users experience. Always run mobile tests separately, and use a throttled connection speed (4G or slower) for realistic results.
Treating the overall score as the goal
The GTmetrix performance score is a weighted average of multiple Lighthouse audits. A score of 100 does not guarantee passing Core Web Vitals, and a score of 80 does not necessarily mean failing them. Focus on the individual metrics — LCP, CLS, INP — rather than the aggregate score.
Not testing inner pages
The homepage is usually the most optimised page on a site. Inner pages — product pages, blog posts, category pages — are often heavier and less optimised. Test the pages that matter for conversions and search rankings, not just the front door.
Forgetting that third-party scripts change
A page that passes Core Web Vitals today may fail next month because a third-party script (analytics, chat widget, ad network) was updated and now loads slower. Periodic re-testing catches regressions that would otherwise go unnoticed.
GTmetrix in the context of Core Web Vitals and page experience
Since Google made Core Web Vitals part of page experience signals, page speed testing has moved from a nice-to-have to a ranking factor. GTmetrix adapted by adopting Lighthouse as its engine, which means its recommendations now align with Google's own standards. However, the most important shift is the distinction between lab data (GTmetrix) and field data (Google's CrUX). GTmetrix is excellent for diagnosing problems — it shows you exactly what is slow and what to fix. But for knowing whether Google considers your page to pass Core Web Vitals, check PageSpeed Insights, which shows both lab and field data. Use both tools together: GTmetrix for diagnosis, PageSpeed Insights for the official assessment.
- Lab data (GTmetrix) is for diagnosis; field data (CrUX/PageSpeed Insights) is for Google's assessment
- Core Web Vitals thresholds are LCP < 2.5s, CLS < 0.1, INP < 200ms
- Lighthouse-based recommendations align with Google's own performance guidance
- Third-party scripts are the most common cause of performance regressions over time
How iNet Ventures approaches gtmetrix
We run GTmetrix on every client site as part of our technical SEO baseline. We test the homepage and top traffic pages from a location matching the client's audience, on mobile with throttled connection speed. We prioritise fixes by estimated time savings and traffic impact.
Performance baseline
We test the top 10 pages by traffic from the client's primary audience location, on mobile. We record LCP, CLS, INP, and the top three recommendations for each page. This establishes a performance baseline.
Fix prioritisation
We sort recommendations by estimated time savings and page traffic. A fix that saves 2 seconds on a page with 10,000 monthly visits is prioritised over a fix that saves 0.5 seconds on a page with 500 visits.
Verification
After fixes are implemented, we re-test in GTmetrix and also check PageSpeed Insights for field data. Both lab and field data should show improvement before we consider the fix complete.
Continue learning
Best SEO Link Building Tools
How GTmetrix fits into a technical SEO tool stack.
Link Building Plans
Monthly link building with no contracts.
Competitor Link Building
We turn competitor research into live link placements.
Best Blogger Outreach Services
Compare top outreach providers and their approaches.
Free Backlink Analyzer
Check a backlink profile without a paid subscription.
Frequently asked questions
Is GTmetrix free?
GTmetrix offers a free tier that allows unlimited tests from one location (Vancouver) with limited configuration options. Paid plans start at around £12 per month and add multiple test locations, monitoring, alerting, and more detailed analysis options. The free tier is sufficient for most one-off audits.
How does GTmetrix compare to PageSpeed Insights?
Both use Lighthouse as their engine, so their recommendations are similar. GTmetrix offers more visualisation tools (waterfall chart, video filmstrip) and configurable test settings (location, device, connection speed). PageSpeed Insights shows both lab data and field data (real user data from CrUX), which GTmetrix does not. Use GTmetrix for diagnosis and PageSpeed Insights for Google's actual Core Web Vitals assessment.
What are good Core Web Vitals scores?
Google's thresholds are: LCP (Largest Contentful Paint) under 2.5 seconds, CLS (Cumulative Layout Shift) under 0.1, and INP (Interaction to Next Paint) under 200 milliseconds. Pages that meet all three thresholds are considered to have "good" Core Web Vitals. GTmetrix shows whether each metric passes or fails.
Does GTmetrix use Lighthouse?
Yes. Since 2020, GTmetrix uses Google Lighthouse as its testing engine. This means GTmetrix recommendations align with Google's own performance standards. The same audits that run in PageSpeed Insights run in GTmetrix — GTmetrix adds visualisation and monitoring on top.
Can GTmetrix test mobile performance?
Yes. GTmetrix can simulate mobile devices and throttle connection speed to match 4G or slower networks. Mobile testing is essential because mobile performance is typically worse than desktop, and Google uses mobile-first indexing. Always test mobile separately.
Why do my GTmetrix scores differ from PageSpeed Insights?
GTmetrix and PageSpeed Insights both use Lighthouse, but they may run from different locations, with different device settings, or at different times. Performance varies by server load, CDN caching, and network conditions. Small differences are normal. Large differences usually indicate a configuration mismatch — check that both tests use the same device and location settings.
Written from daily use of GTmetrix alongside PageSpeed Insights and CrUX data for client site performance audits. Core Web Vitals thresholds and recommendations are checked against Google's official documentation.
- Written by:
- iNet Ventures Editorial Team
- Reviewed by:
- iNet Ventures Technical SEO Team
- Published:
- 18 August 2026
- Last reviewed:
- 18 August 2026
Sources and further reading
Spotted something out of date or incorrect? Tell us and we will review and correct it.
Need links that actually hold up?
White-label link building and digital PR, priced per placement. Every link comes with a live URL and the context behind it.