Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize 28churchrow.pages.dev
91% of your CSS is unused, adding 150ms to LCP and blocking initial render for 1.5 seconds.
Use PurgeCSS or similar tools to remove unused styles from global.css, saving 27 KiB. Inline critical CSS for above-the-fold content directly in the HTML. Consider splitting CSS into route-specific bundles to reduce initial payload.
A score of 89 falls in the "Needs Improvement" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website achieves a good performance score of 89/100, but there are several optimization opportunities that could make it even faster. The biggest issue is render-blocking CSS and font resources that are delaying the initial page display by an estimated 1.5 seconds, particularly affecting First Contentful Paint. Image optimization presents another significant opportunity, with potential savings of 312 KiB by properly sizing images for their display dimensions and improving compression - some images are being downloaded at 1200x588 pixels but only displayed at 233x155 pixels. Additionally, the site's main hero image needs a `fetchpriority="high"` attribute to improve Largest Contentful Paint, and adding explicit width and height dimensions to images would help reduce layout shifts.
Why It Matters:
Images are oversized and poorly compressed, wasting 312 KiB and delaying LCP by 400ms.
How to Fix:
Configure your Sanity CDN to serve appropriately sized images using responsive parameters (w=412 for mobile, w=1200 for desktop). Enable better compression by adding quality parameters like ?q=80. Update your image components to use srcset with multiple breakpoints for optimal delivery across devices.
Why It Matters:
The hero brand image lacks fetchpriority=high, missing an opportunity to prioritize critical resource loading.
How to Fix:
Add fetchpriority='high' attribute to the home-hero__brand image element. Also add explicit width='298' and height='76' attributes to prevent layout shift. Consider preloading this SVG if it's critical for brand recognition on page load.
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Font files create a 423ms critical chain dependency that delays content rendering and impacts Speed Index.
JavaScript is causing 48.7ms of forced reflows, blocking the main thread and degrading user experience.
The portrait image is oversized by 87KB, wasting bandwidth and potentially impacting perceived load performance.
The hero brand image lacks fetchpriority=high, missing an opportunity to prioritize critical resource loading.