Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize orenda.net.in
CSS files are blocking initial page render by 2,070ms, preventing users from seeing content immediately.
Inline critical CSS for above-the-fold content directly in the HTML head. Defer non-critical CSS like chat.css using media='print' onload technique. Remove unused Bootstrap CSS (95% unused) or create a custom build with only needed components. Minify remaining CSS files to reduce payload size.
A score of 59 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 59/100, primarily due to extremely slow loading of the largest content element, which takes 13.2 seconds to appear on screen. The biggest culprit is oversized, unoptimized images (particularly a 1.3MB hero background image) that could be reduced by nearly 3MB through modern formats like WebP and proper compression. The site is also being slowed down by render-blocking CSS files that delay initial page rendering by over 2 seconds, and there's significant unused CSS and JavaScript that could be removed. Fixing the image optimization alone could improve the loading time by 3.5 seconds and dramatically boost the performance score.
Why It Matters:
Three large images (3MB total) are causing a devastating 13.2s LCP, directly blocking your largest contentful paint.
How to Fix:
Convert home-bg.jpg, priya-bg2.jpg, and ramesh-bg2.jpg to WebP format using tools like Squoosh or ImageOptim. Resize team images from 1080x1080 to their actual display size of 637x637. Implement responsive images with srcset to serve appropriately sized images for different devices.
Why It Matters:
The LCP element has a 4,194ms render delay due to JavaScript animations, severely delaying content visibility.
How to Fix:
Remove or defer GSAP animations on the hero title span until after LCP. Use CSS transforms instead of JavaScript for initial animations. Ensure the LCP element renders immediately without waiting for JavaScript execution. Consider making the hero text visible by default and enhancing with animations progressively.
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
Short cache lifetimes for 584 KiB of resources are causing unnecessary network requests and slowing repeat visits.
3.1 seconds of JavaScript execution time is blocking the main thread and preventing user interactions.
702 KiB of unused JavaScript is blocking LCP by 3.9 seconds and severely impacting page performance.
The LCP element has a 4,194ms render delay due to JavaScript animations, severely delaying content visibility.