LCP
Largest Contentful Paint
7.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS Resources
How to optimize swaminarayanuniversity.ac.in
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimated
Why It Matters
Render-blocking CSS delays First Contentful Paint by 2.56 seconds, preventing users from seeing content quickly.
How to Fix
Inline critical CSS for above-the-fold content directly in the HTML head. Defer non-critical CSS like FontAwesome (99.5% unused) using media='print' onload='this.media="all"'. Remove unused CSS rules from Bootstrap and custom stylesheets to reduce payload by 141 KiB.
0Poor
What This Score Means
A score of 40 falls in the "Poor" 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
99ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.87
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This university website has poor performance with a concerning score of 40/100, indicating significant issues that hurt user experience. The biggest problem is extremely high layout shift (0.87 CLS score), where page content jumps around as images load without proper dimensions, making the site feel unstable and difficult to use. Additionally, the site suffers from a very slow Largest Contentful Paint of 7.8 seconds due to oversized images that could save over 3MB through modern formats like WebP and proper sizing. Fixing image dimensions to prevent layout shifts and optimizing the massive image files would dramatically improve both stability and loading speed, potentially boosting the performance score by 30+ points.
Other Optimization Recommendations
Fix Cumulative Layout Shift Issues
High Impact+25 points estimatedWhy It Matters:
Your CLS score of 0.87 is extremely poor (needs <0.1) causing major visual instability that hurts user experience.
How to Fix:
Add explicit width and height attributes to all images, especially the About Image and Exchange Idea Icon. Preload the Yantramanav fonts using <link rel='preload'> to prevent font swap layout shifts. Reserve space for dynamic content with CSS aspect-ratio or min-height properties.
Optimize Image Delivery and Compression
High Impact+18 points estimatedWhy It Matters:
Images waste 3,101 KiB and delay LCP by 2.65 seconds due to oversized files and poor formats.
How to Fix:
Convert testimonial images from PNG/JPG to WebP format for 50-70% size reduction. Resize images to match display dimensions (testimonials should be 110px not 800px). Add fetchpriority='high' to the hero image and implement responsive images with srcset attributes.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Fix Layout Shift Issues
CLS score of 0.299 indicates significant content jumping, mainly from carousel and banner loading.
Optimize LCP Image Discovery
The LCP image has an 8.3 second resource load delay because it's not discoverable in the initial HTML.
Remove Unused JavaScript Code
2,134 KiB of unused JavaScript is delaying LCP by 7.95 seconds and blocking the main thread.
Optimize Font Loading Strategy
Missing font-display properties cause 35ms of render blocking and potential layout shifts.