Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize git.tower.com
Render-blocking CSS and missing preconnect hints delay First Contentful Paint by 2.25 seconds.
Add <link rel='preconnect' href='https://rsms.me'> to your HTML head to establish early connections. Inline critical CSS for above-the-fold content directly in HTML. Load non-critical fonts asynchronously using font-display: swap in CSS.
A score of 61 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 has poor performance with a score of 61/100, primarily due to extremely slow loading times - it takes 12.5 seconds for the largest content to appear and become interactive. The biggest issues are oversized video files (over 6MB total) that lack proper caching, and render-blocking CSS files from external sources like Google Fonts that delay initial page rendering by over 2 seconds. The site could see dramatic improvements by implementing proper caching for video content, optimizing image sizes (currently serving images much larger than needed), and deferring non-critical CSS loading. Additionally, removing unused JavaScript from Google Analytics and other third-party scripts could save an estimated 209KB and reduce load times significantly.
Why It Matters:
Missing cache headers waste 5MB of bandwidth and delay LCP by 1.65 seconds on repeat visits.
How to Fix:
Configure your web server to set Cache-Control headers with long expiration times (1 year) for static assets like videos and images. Add versioning to filenames for cache busting when content changes. For the large MP4 files identified, set cache headers to max-age=31536000 (1 year).
Why It Matters:
209KB of unused JavaScript delays LCP by 900ms and wastes bandwidth on mobile users.
How to Fix:
Remove or defer Google Analytics and GTM scripts until after page load using async loading. Split JavaScript bundles to load only necessary code initially. Consider switching to Google Analytics 4's minimal implementation or use Partytown to run tracking scripts in a web worker.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
209KB of unused JavaScript delays LCP by 900ms and wastes bandwidth on mobile users.
Missing cache headers waste 5MB of bandwidth and delay LCP by 1.65 seconds on repeat visits.
Oversized images waste 351 KiB of bandwidth and slow down page rendering.
352 KiB of unused JavaScript blocks page loading and delays LCP by 750ms.
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.