Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize goniyo.com
58KB of unused CSS delays First Contentful Paint by 150ms and blocks critical rendering.
Remove unused Bootstrap CSS or switch to a custom build with only needed components. Audit Font Awesome usage and load only required icons. Use PurgeCSS to automatically remove unused styles from your build process.
A score of 86 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
The Goniyo.com website shows good performance with a score of 86/100, but still has room for improvement in loading speed. The biggest issue is oversized images that are being downloaded at much larger dimensions than they're displayed on the page, wasting nearly 500KB of data and slowing down the user experience. The site also suffers from unused CSS and JavaScript code, particularly from Bootstrap and Facebook tracking scripts, which adds unnecessary bloat to page loads. Most critically, the Time to Interactive is quite slow at 10.1 seconds, meaning users have to wait that long before they can fully interact with the page, primarily due to inefficient caching and unoptimized third-party scripts.
Why It Matters:
Images are 486KB oversized, wasting bandwidth and slowing page load for mobile users.
How to Fix:
Resize homepage images (visa-home1.webp, tour-attraction1.webp, hotels-home1.webp) from 1121x1018 to actual display size of 385x385. Implement responsive images with srcset attribute. Use image optimization tools to compress without quality loss.
Why It Matters:
497KB of resources have no cache headers, forcing unnecessary downloads on repeat visits.
How to Fix:
Add long-term cache headers (1 year) for the web-lattice JavaScript bundle and static SVG assets. Set appropriate cache-control headers for Facebook Pixel script. Configure your CDN or server to automatically handle static asset caching.
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
Poor cache policies on external scripts force repeated downloads, slowing repeat visits by 248 KiB.
330 KiB of unused JavaScript delays LCP by 400ms and blocks the main thread for 2 seconds.
Font loading delays are causing 650ms delay to First Contentful Paint and creating invisible text periods.
Missing width and height attributes on images cause layout shifts that hurt user experience and CLS scores.