Performance Issues

This guide helps you troubleshoot slow loading times, high resource usage, and other performance-related problems with ShahiLandin landing pages.

Slow Page Load Times

Symptom

Landing pages take several seconds to load or timeout completely.

Solutions

Problem 1: Large Unoptimized Images

Symptom: Page loads slowly, especially on mobile. DevTools shows large image file sizes.

Solution:

1. Compress images before upload:

– Use tools: TinyPNG, ImageOptim, Squoosh
– Target: Under 200KB per image
– Format: WebP for best compression (with JPG fallback)

2. Enable lazy loading:

– Go to ShahiLandin → Settings → Performance
– Check Enable Lazy Loading for Images
– Save Changes

3. Use responsive images:

`html

`

4. Convert to WebP:

– Install “WebP Express” or “ShortPixel” plugin
– Automatically converts images to WebP
– Falls back to JPG for unsupported browsers

Problem 2: Too Many External Scripts


Symptom: Waterfall diagram shows many external JavaScript files loading.

Solution:

5. Audit loaded scripts:

– Open DevTools → Network tab
– Refresh page
– Sort by Size (largest first)
– Identify unnecessary scripts

6. Remove unused scripts:

– Edit landing page → HTML tab
– Remove or comment out unused



`

Problem 3: Excessive CSS


Symptom: CSS file size over 100KB, many unused styles.

Solution:

7. Enable CSS minification:

- Go to Settings → Performance
- Check Minify CSS
- Save Changes

8. Remove unused CSS:

- Use Chrome DevTools Coverage tab
- Identify unused CSS rules
- Remove from CSS editor

9. Inline critical CSS:

- Extract above-the-fold CSS
- Place in

`

Problem 4: No Caching Enabled


Symptom: Every page load is slow, even for repeat visitors.

Solution:

10. Enable browser caching via .htaccess:

`apache

ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType image/webp "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"

`

11. Install caching plugin:

- WP Super Cache (free, simple)
- W3 Total Cache (free, advanced)
- WP Rocket (paid, comprehensive)

12. Configure ShahiLandin cache settings:

- Go to Settings → Performance
- Enable Cache Landing Page Output
- Set cache duration (default: 1 hour)

Problem 5: Server Response Time (TTFB) High


Symptom: Time to First Byte over 600ms.

Solution:

13. Check hosting resources:

- Verify adequate RAM and CPU
- Contact hosting support if limits reached
- Consider upgrading hosting plan

14. Enable object caching:

- Install Redis or Memcached
- Enable in caching plugin
- Or use Redis Object Cache plugin

15. Optimize database:

- Install WP-Optimize plugin
- Clean up post revisions, spam comments
- Optimize database tables

16. Use CDN (see below)

Problem 6: No Content Delivery Network (CDN)


Symptom: Slow loading for international visitors.

Solution:

17. Set up Cloudflare (free option):

- Sign up at cloudflare.com
- Change nameservers as instructed
- Enable Auto Minify and Brotli compression
- Configure page rules for caching

18. Alternative CDNs:

- BunnyCDN: Fast and affordable
- KeyCDN: Pay-as-you-go pricing
- AWS CloudFront: Scalable enterprise option

19. Configure CDN with ShahiLandin:

- Most CDNs work automatically
- Ensure landing page assets are cached
- Test with: https://tools.keycdn.com/speed

High Memory Usage


Symptom


WordPress admin becomes slow, or you see "Memory limit exceeded" errors.

Solutions


Problem 1: Landing Page Too Complex


Symptom: Large HTML/CSS files consuming memory.

Solution:

20. Simplify landing page:

- Remove unnecessary HTML elements
- Reduce CSS complexity
- Minimize inline styles

21. Increase PHP memory limit:

- Add to wp-config.php:
`php
define('WPMEMORYLIMIT', '256M');
define('WPMAXMEMORY_LIMIT', '512M');
`
- Or contact hosting provider

22. Optimize assets:

- Compress images further
- Remove unused fonts
- Minimize JavaScript libraries

Problem 2: Too Many Landing Pages


Symptom: Admin dashboard slow when listing all landing pages.

Solution:

23. Archive old landing pages:

- Move to "Draft" status if not active
- Or delete permanently (after backup)

24. Increase pagination:

- Admin → Screen Options → Number of items per page
- Reduce from 20 to 10

25. Database cleanup:

- Delete auto-drafts and revisions
- Use WP-CLI:
`bash
wp post delete $(wp post list --posttype=shahilanding --post_status=auto-draft --format=ids) --force
`

Problem 3: Analytics Database Growing Large


Symptom: Database size increasing rapidly, queries slowing down.

Solution:

26. Enable automatic cleanup:

- Go to Settings → Analytics
- Set Data Retention Period: 90 days (or as needed)
- Old data automatically deleted

27. Manual cleanup via WP-CLI:

`bash

Delete analytics data older than 90 days


wp db query "DELETE FROM wpshahilandinanalytics WHERE createdat < DATESUB(NOW(), INTERVAL 90 DAY)"

Optimize table


wp db query "OPTIMIZE TABLE wpshahilandinanalytics"
`

28. Archive old data:

- Export to CSV before deletion
- Store in external analytics platform
- Keep database lean

Performance Score Issues


Symptom


PageSpeed Insights or GTmetrix shows low scores for landing pages.

Solutions


Problem 1: Render-Blocking Resources


Error: "Eliminate render-blocking resources"

Solution:

29. Defer non-critical CSS:

`html
`

30. Defer JavaScript:

`html

`

31. Enable ShahiLandin optimization:

- Settings → Performance
- Check Optimize CSS Delivery
- Check Defer JavaScript Loading

Problem 2: Largest Contentful Paint (LCP) High


Error: "LCP takes 4+ seconds"

Solution:

32. Optimize hero image:

- Compress aggressively
- Use WebP format
- Preload hero image:
`html `

33. Reduce server response time (see TTFB solutions above)
34. Remove animation delays:

- Reduce or remove entrance animations
- Load visible content immediately

Problem 3: First Contentful Paint (FCP) Slow


Error: "FCP over 3 seconds"

Solution:

35. Inline critical CSS (see above)
36. Minimize HTML size:

- Remove whitespace
- Enable minification: Settings → Performance → Minify HTML

37. Preconnect to external domains:

`html `

Problem 4: Cumulative Layout Shift (CLS)


Error: "Elements shift during loading"

Solution:

38. Set image dimensions:

`html

`

39. Reserve space for dynamic content:

`css
.ad-container {
min-height: 250px; / Reserve space before ad loads /
}
`

40. Use font-display: swap:

`css
@font-face {
font-family: 'CustomFont';
src: url('font.woff2');
font-display: swap; / Prevents layout shift /
}
`

Problem 5: Total Blocking Time (TBT) High


Error: "JavaScript blocks main thread"

Solution:

41. Remove heavy JavaScript libraries:

- Replace jQuery with vanilla JS where possible
- Use lightweight alternatives (e.g., Alpine.js instead of Vue)

42. Code splitting:

- Load JavaScript only when needed
- Example: Load form validation only when form is visible

43. Use Web Workers for heavy computations

Asset Loading Issues


Problem 1: Fonts Loading Slowly


Solution:

44. Self-host fonts:

- Download from Google Fonts
- Upload to WordPress uploads folder
- Reference locally instead of CDN

45. Subset fonts:

- Only include characters you need
- Use Google Fonts with subset parameter:
`html`

46. Preload key fonts:

`html `

Problem 2: Too Many HTTP Requests


Solution:

47. Count current requests:

- Open DevTools → Network tab
- Reload page
- Check total number (aim for under 50)

48. Combine files:

- Merge multiple CSS files into one
- Merge multiple JavaScript files into one
- Use CSS sprites for small icons

49. Use data URIs for small images:

`css
.icon {
background-image: url('data:image/svg+xml;base64,PHN2ZyB3aWR0aD0...');
}
`

Problem 3: External Assets Timing Out


Solution:

50. Mirror external assets locally:

- Use asset mirroring in HTML import wizard
- Or manually download and upload to WordPress

51. Set timeout fallbacks:

`html

`

Mobile Performance Issues


Symptom


Landing page loads fast on desktop but slow on mobile.

Solutions


Problem 1: Not Using Responsive Images


Solution:
Use srcset to serve appropriate image sizes:
`html

`

Problem 2: Heavy JavaScript on Mobile


Solution:
Conditionally load features based on screen size:
`html

`

Problem 3: Mobile Redirects


Symptom: Unnecessary redirects detected on mobile.

Solution:

52. Ensure landing page is responsive, not separate mobile version
53. Remove mobile detection redirects
54. Use responsive design instead of separate mobile site

Caching Issues


Problem 1: Changes Not Appearing


Symptom: Edit landing page but old version still displays.

Solution:

55. Clear ShahiLandin cache:

- Edit landing page
- Click Clear Cache button (if available)
- Or go to Settings → Performance → Clear All Caches

56. Clear WordPress cache:

- If using caching plugin, clear cache
- WP Super Cache: Settings → Delete Cache
- W3 Total Cache: Performance → Empty All Caches
- WP Rocket: Clear Cache button in admin bar

57. Clear CDN cache:

- Cloudflare: Caching → Purge Everything
- Other CDNs: Check their documentation

58. Clear browser cache:

- Hard refresh: Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)
- Or use incognito/private window

Problem 2: Stale Content Served


Symptom: Old version of landing page cached for too long.

Solution:

59. Reduce cache duration:

- Settings → Performance → Cache Duration
- Set to 1 hour instead of 24 hours during active development

60. Auto-clear cache on update:

- ShahiLandin automatically clears cache when page updated
- If not working, check for plugin conflicts

Problem 3: Analytics Not Working Due to Caching


Symptom: Cached pages don't track views.

Solution:

61. Exclude from page cache:

- Add landing page URLs to cache exclusions
- Caching plugin → Settings → Exclusions

62. Use edge-side includes (ESI) if CDN supports it
63. Switch to server-side tracking:

- Custom development required
- Track views at server level before cache

Database Performance


Problem 1: Slow Queries


Symptom: Database queries taking multiple seconds.

Solution:

64. Add indexes (if missing):

- ShahiLandin should auto-create indexes
- Verify in phpMyAdmin:
- Table wpshahilandinanalytics
- Indexes on: postid, createdat, goal

65. Manual index creation (if needed):

`sql
ALTER TABLE wpshahilandinanalytics ADD INDEX idxpostid (post_id);
ALTER TABLE wpshahilandinanalytics ADD INDEX idxcreatedat (created_at);
ALTER TABLE wpshahilandinanalytics ADD INDEX idx_goal (goal);
`

66. Optimize tables regularly:

`sql
OPTIMIZE TABLE wp_posts;
OPTIMIZE TABLE wp_postmeta;
OPTIMIZE TABLE wpshahilandinanalytics;
OPTIMIZE TABLE wpshahilandinexperiments;
`

Problem 2: Large wp_postmeta Table


Symptom: Slow queries due to bloated postmeta table.

Solution:

67. Clean up post meta:

- Remove orphaned meta data:
`sql
DELETE FROM wppostmeta WHERE postid NOT IN (SELECT ID FROM wp_posts);
`

68. Delete old revisions:

`bash
wp post delete $(wp post list --post_type=revision --format=ids) --force
`

69. Limit revisions in wp-config.php:

`php
define('WPPOSTREVISIONS', 3);
`

Measuring Performance


Tools to Use


70. Google PageSpeed Insights:

- https://pagespeed.web.dev/
- Tests mobile and desktop
- Provides actionable recommendations

71. GTmetrix:

- https://gtmetrix.com/
- Detailed waterfall diagrams
- Historical performance tracking

72. WebPageTest:

- https://www.webpagetest.org/
- Advanced testing options
- Multiple test locations

73. Chrome DevTools:

- Built into Chrome browser
- Press F12 → Lighthouse tab
- Run performance audit

Performance Benchmarks


Target metrics for landing pages:

| Metric | Good | Needs Improvement | Poor |
|--------|------|-------------------|------|
| Largest Contentful Paint (LCP) | ≤ 2.5s | 2.5s - 4s | > 4s |
| First Input Delay (FID) | ≤ 100ms | 100ms - 300ms | > 300ms |
| Cumulative Layout Shift (CLS) | ≤ 0.1 | 0.1 - 0.25 | > 0.25 |
| Time to First Byte (TTFB) | ≤ 600ms | 600ms - 1000ms | > 1000ms |
| Total Page Size | ≤ 1MB | 1MB - 3MB | > 3MB |
| HTTP Requests | ≤ 30 | 30 - 50 | > 50 |

Performance Checklist


Use this checklist to optimize landing pages:

• [ ] Images: Compressed, WebP format, lazy loading enabled
• [ ] CSS: Minified, critical CSS inline, unused rules removed
• [ ] JavaScript: Minified, deferred, async where appropriate
• [ ] Fonts: Subset, preloaded, font-display: swap
• [ ] Caching: Plugin installed, browser caching enabled, CDN configured
• [ ] Database: Optimized, indexed, old data cleaned
• [ ] Server: Adequate resources, object caching enabled
• [ ] Mobile: Responsive images, reduced JavaScript
• [ ] Monitoring: Regular performance tests, metrics tracked

---

Related Articles:

• Performance Optimization Feature Guide
• Cache and Plugin Conflicts
• Display and Rendering Issues