Created September 10, 2025
Comprehensive overview of PageSpeed audit sections and key findings
Comprehensive overview of PageSpeed audit sections and key findings
Comprehensive overview of PageSpeed audit sections and key findings
PageSpeed Insights Report
This PageSpeed Insights audit was conducted on https://vitriturf.com/ using Lighthouse v10.0.0 on September 10, 2025. The audit evaluated Performance in detail across both desktop and mobile devices, while Accessibility, Best Practices, and SEO are summarized with overall scores. Core Web Vitals assessments are based on real user experience data collected over the past 28 days.
Provides a high-level benchmark of the site's overall health, highlighting key strengths and surfacing improvement opportunities. Serves as a baseline for tracking progress and ensuring the site continues to deliver a fast, accessible, and search-optimized experience.
Website Health Benchmark – Desktop
The scores shown above represent the Desktop Lighthouse audit results for Performance, Accessibility, Best Practices, and SEO. Performance reflects detailed metrics such as page load speed, interactivity, and visual stability. Accessibility, Best Practices, and SEO are summarized as overall scores. These values provide a quick benchmark of the site's technical health on desktop devices, following Google Lighthouse scoring standards.
▲ 0–49 (Poor) ■ 50–89 (Needs Improvement) ● 90–100 (Good)
Real User Experience Data - Desktop
This Core Web Vitals assessment is based on real user experience data collected over the past 28 days. It evaluates key metrics such as Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
These metrics provide insights into the site's loading performance, interactivity, and visual stability as experienced by actual users. Maintaining good Core Web Vitals is crucial for both user satisfaction and search engine ranking.
Largest Contentful Paint (LCP) – Measures loading performance. It reports how long it takes for the largest visible element (such as an image or headline) to appear on the screen. A good experience is ≤ 2.5 seconds.
Interaction to Next Paint (INP) – Measures interactivity. It tracks how quickly the page responds to user actions like clicks, taps, or keyboard input. A good experience is ≤ 200 ms.
Cumulative Layout Shift (CLS) – Measures visual stability. It tracks how much page elements unexpectedly shift during load. A good experience is ≤ 0.1.
First Contentful Paint (FCP) – Indicates perceived load speed. It measures how quickly the first text or image is rendered.
Time to First Byte (TTFB) – Measures server responsiveness. It shows how fast the server delivers the first byte of data to the browser.
Real User Experience Data – Desktop
0.0 s
0 ms
0.00
0.0 s
0.0 s
Real User Experience Data – Desktop
Status: Passed
| Metric | Field Data | Status | Target |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 0.0 s | Pass | ≤ 2.5s |
| Interaction to Next Paint (INP) | 0 ms | Pass | ≤ 200ms |
| Cumulative Layout Shift (CLS) | 0.00 | Pass | ≤ 0.1 |
| First Contentful Paint (FCP) | 0.0 s | Pass | ≤ 1.8s |
| Time to First Byte (TTFB) | 0.0 s | Pass | ≤ 0.8s |
Simulated load test in a controlled environment – Desktop
The following metrics are derived from Lighthouse Lab Data, which runs performance tests under controlled, simulated conditions. Unlike Core Web Vitals, which rely on real user field data, lab data provides reproducible diagnostics to identify specific performance bottlenecks. Each value is compared against Google's recommended thresholds to determine pass or fail status.
Raw values are converted into readable formats (e.g., milliseconds to seconds, CLS rounded to three decimals) and evaluated against Google's thresholds. If API data is unavailable, fallback values are used for consistency (FCP 1.2s, LCP 2.8s, TBT 150ms, CLS 0.05, SI 3.2s).
Lab data helps pinpoint the root causes of poor performance in a controlled setting, even if real-user data (Core Web Vitals) is not yet available or stable. Because the tests are simulated, results may not match every real-world user experience, but they are highly useful for identifying and prioritizing fixes.
Lab Data Performance Overview – Desktop
Simulated load test in a controlled environment – Desktop
| Metric | Lab Value | Status | Target |
|---|---|---|---|
| First Contentful Paint | 0.9 s | Pass | ≤ 1.8s |
| Largest Contentful Paint | 2.3 s | Pass | ≤ 2.5s |
| Total Blocking Time | 35 ms | Pass | ≤ 200ms |
| Cumulative Layout Shift | 0.006 | Pass | ≤ 0.1 |
| Speed Index | 1.5 s | Pass | ≤ 3.4s |
Lab Data & Optimization Opportunities – Desktop
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Eliminate render-blocking resources | Est savings of 560 ms | Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. (https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/). | High |
| Minify JavaScript | Est savings of 5 KiB | Minifying JavaScript files can reduce payload sizes and script parse time. (https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/). | Medium |
| Reduce unused JavaScript | Est savings of 163 KiB | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. (https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/). | High |
| Reduce unused CSS | Est savings of 124 KiB | Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. (https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/). | High |
Lab Data & Optimization Opportunities – Desktop
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Avoid serving legacy JavaScript to modern browsers | Est savings of 10 KiB | Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile (https://web.dev/baseline) features, unless you know you must support legacy browsers. (https://philipwalton.com/articles/the-state-of-es5-on-the-web/) | Medium |
| Avoid enormous network payloads | Total size was 4,674 KiB | Large network payloads cost users real money and are highly correlated with long load times. (https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/). | Medium |
| Serve images in next-gen formats | Est savings of 667 KiB | Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. (https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images/). | High |
Lab Data & Optimization Opportunities – Desktop
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Image elements do not have explicit `width` and `height` | — | Set an explicit width and height on image elements to reduce layout shifts and improve CLS. (https://web.dev/articles/optimize-cls#images_without_dimensions) | Medium |
| Minify CSS | Est savings of 8 KiB | Minifying CSS files can reduce network payload sizes. (https://developer.chrome.com/docs/lighthouse/performance/unminified-css/). | High |
| Ensure text remains visible during webfont load | — | Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. (https://developer.chrome.com/docs/lighthouse/performance/font-display/). | Medium |
| Properly size images | Est savings of 2,048 KiB | Serve images that are appropriately-sized to save cellular data and improve load time. (https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images/). | High |
Website Health Benchmark – Mobile
The scores shown above represent the Mobile Lighthouse audit results for Performance, Accessibility, Best Practices, and SEO. Performance reflects detailed metrics such as page load speed, interactivity, and visual stability. Accessibility, Best Practices, and SEO are summarized as overall scores. These values provide a quick benchmark of the site's technical health on mobile devices, following Google Lighthouse scoring standards.
▲ 0–49 (Poor) ■ 50–89 (Needs Improvement) ● 90–100 (Good)
Real User Experience Data - Mobile
This Core Web Vitals assessment is based on real user experience data collected over the past 28 days. It evaluates key metrics such as Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
These metrics provide insights into the site's loading performance, interactivity, and visual stability as experienced by actual users. Maintaining good Core Web Vitals is crucial for both user satisfaction and search engine ranking.
Largest Contentful Paint (LCP) – Measures loading performance. It reports how long it takes for the largest visible element (such as an image or headline) to appear on the screen. A good experience is ≤ 2.5 seconds.
Interaction to Next Paint (INP) – Measures interactivity. It tracks how quickly the page responds to user actions like clicks, taps, or keyboard input. A good experience is ≤ 200 ms.
Cumulative Layout Shift (CLS) – Measures visual stability. It tracks how much page elements unexpectedly shift during load. A good experience is ≤ 0.1.
First Contentful Paint (FCP) – Indicates perceived load speed. It measures how quickly the first text or image is rendered.
Time to First Byte (TTFB) – Measures server responsiveness. It shows how fast the server delivers the first byte of data to the browser.
Real User Experience Data – Mobile
0.0 s
0 ms
0.00
0.0 s
0.0 s
Real User Experience Data – Mobile
Status: Passed
| Metric | Field Data | Status | Target |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 0.0 s | Pass | ≤ 2.5s |
| Interaction to Next Paint (INP) | 0 ms | Pass | ≤ 200ms |
| Cumulative Layout Shift (CLS) | 0.00 | Pass | ≤ 0.1 |
| First Contentful Paint (FCP) | 0.0 s | Pass | ≤ 1.8s |
| Time to First Byte (TTFB) | 0.0 s | Pass | ≤ 0.8s |
Simulated load test in a controlled environment – Mobile
The following metrics are derived from Lighthouse Lab Data, which runs performance tests under controlled, simulated conditions. Unlike Core Web Vitals, which rely on real user field data, lab data provides reproducible diagnostics to identify specific performance bottlenecks. Each value is compared against Google's recommended thresholds to determine pass or fail status.
Raw values are converted into readable formats (e.g., milliseconds to seconds, CLS rounded to three decimals) and evaluated against Google's thresholds. For mobile testing, Lighthouse simulates slower device hardware and a 4G network connection, which may result in higher (slower) values compared to desktop. If API data is unavailable, fallback values are used for consistency (FCP 1.2s, LCP 2.8s, TBT 150ms, CLS 0.05, SI 3.2s).
Lab data helps pinpoint the root causes of poor performance in a controlled setting, even if real-user data (Core Web Vitals) is not yet available or stable. Because the tests are simulated, results may not match every real-world user experience, but they are highly useful for identifying and prioritizing fixes.
Lab Data Performance Overview – Mobile
Simulated load test in a controlled environment – Mobile
| Metric | Lab Value | Status | Target |
|---|---|---|---|
| First Contentful Paint | 4.2 s | Fail | ≤ 1.8s |
| Largest Contentful Paint | 18.0 s | Fail | ≤ 2.5s |
| Total Blocking Time | 88 ms | Pass | ≤ 200ms |
| Cumulative Layout Shift | 0.000 | Pass | ≤ 0.1 |
| Speed Index | 7.3 s | Fail | ≤ 3.4s |
Lab Data & Optimization Opportunities – Mobile
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Eliminate render-blocking resources | Est savings of 3,100 ms | Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. (https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/). | High |
| Minify JavaScript | Est savings of 5 KiB | Minifying JavaScript files can reduce payload sizes and script parse time. (https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/). | Medium |
| Reduce unused JavaScript | Est savings of 162 KiB | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. (https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/). | High |
| Reduce unused CSS | Est savings of 124 KiB | Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. (https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/). | High |
Lab Data & Optimization Opportunities – Mobile
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Avoid serving legacy JavaScript to modern browsers | Est savings of 10 KiB | Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile (https://web.dev/baseline) features, unless you know you must support legacy browsers. (https://philipwalton.com/articles/the-state-of-es5-on-the-web/) | Medium |
| Avoid enormous network payloads | Total size was 4,701 KiB | Large network payloads cost users real money and are highly correlated with long load times. (https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/). | Medium |
| Serve images in next-gen formats | Est savings of 692 KiB | Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. (https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images/). | High |
Lab Data & Optimization Opportunities – Mobile
| Issue | Estimated Savings | Action | Priority |
|---|---|---|---|
| Image elements do not have explicit `width` and `height` | — | Set an explicit width and height on image elements to reduce layout shifts and improve CLS. (https://web.dev/articles/optimize-cls#images_without_dimensions) | Medium |
| Minify CSS | Est savings of 8 KiB | Minifying CSS files can reduce network payload sizes. (https://developer.chrome.com/docs/lighthouse/performance/unminified-css/). | High |
| Properly size images | Est savings of 1,799 KiB | Serve images that are appropriately-sized to save cellular data and improve load time. (https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images/). | High |
Test Environment & Final Notes - Desktop & Mobile
This report reflects the status of https://vitriturf.com/ as of September 10, 2025. The Core Web Vitals assessment is based on real user data over the past 28 days, while lab data provides controlled environment metrics for development optimization. Focus on addressing high-priority performance issues to improve user experience and search engine rankings.
This comprehensive PageSpeed Insights audit has identified key areas for improvement to ensure your website meets high performance standards. The findings presented in this report provide a clear roadmap for enhancing performance and creating a more efficient digital experience for all users.
We recommend prioritizing the critical and serious issues identified, as these have the most significant impact on user performance. The moderate issues, while less urgent, should also be addressed to achieve optimal performance.