Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize learn.mce.eu
Multiple redirects are adding 750ms delay to both LCP and FCP before the page even starts loading.
Update your WordPress site URL and home URL in wp-config.php or WordPress admin to use the canonical https://learn.mce.eu/wp-login.php directly. Remove the intermediate redirect from the root domain to avoid the 751ms penalty. Check your .htaccess file for unnecessary redirect rules.
A score of 92 falls in the "Good" 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 WordPress login page has good performance with a score of 92/100, but there are still some significant optimization opportunities. The biggest issue is document request latency, which could be improved by nearly a full second (960ms) by reducing server response time and avoiding redirects. The site is also wasting bandwidth by serving 349KB of resources with inefficient cache settings, particularly for JavaScript files like jQuery and CSS files that could be cached much longer. Additionally, there are render-blocking resources that delay the first paint by about 1.5 seconds, which could be resolved by deferring non-critical JavaScript and CSS files.
Why It Matters:
Poor cache lifetimes are wasting 349 KiB and delaying FCP/LCP by 600ms on repeat visits.
How to Fix:
Configure your WordPress hosting or use a plugin like W3 Total Cache to set cache headers for static assets to 1 year (31536000 seconds). Focus on the zxcvbn.min.js (270KB), dashicons.min.css (25KB), and jquery.min.js (22KB) files which currently only cache for 4 hours. Add cache-control headers via .htaccess or your CDN settings.
Why It Matters:
Render-blocking CSS and JavaScript are delaying First Contentful Paint by 1.46 seconds.
How to Fix:
Use a WordPress optimization plugin like Autoptimize or WP Rocket to defer non-critical CSS like buttons.min.css and admin-schemes.min.css. Move the Wordfence login JavaScript to load asynchronously after page render. Inline critical above-the-fold CSS directly in the HTML head.
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 WordPress Speed Tests
Render-blocking CSS and JavaScript are delaying First Contentful Paint by 1.46 seconds.
Poor cache lifetimes are wasting 349 KiB and delaying FCP/LCP by 600ms on repeat visits.
FontAwesome fonts cause 50ms delay in FCP due to missing font-display declarations.
Multiple CSS files block initial page render, delaying FCP by 4.8 seconds.