The Complete WordPress Performance Guide for Irish Businesses in 2024

Ireland's National Broadband Plan has connected over 100,000 homes and businesses to high-speed fibre by October 2024, transforming rural connectivity across 96% of the country's landmass. But faster internet only helps if your WordPress site can actually deliver content quickly. Many Irish businesses are getting gigabit connections while their websites still crawl along at 4-second load times, turning that €8.3 billion digital infrastructure investment into wasted opportunity. Your customers don't care how fast your broadband is if your checkout page takes forever to load.

data centre location impacts performance covers this ground in more detail. This is explored further in restaurant websites crashing under traffic. This is explored further in prepare your site for traffic spikes.

Why WordPress Performance Matters More in Ireland

WordPress performance isn't just about user experience anymore. It's revenue. A café owner on the Galway Quays found this out when their online ordering system started losing customers during the lunch rush. Pages that took 4 seconds to load meant hungry office workers gave up and walked to the competitor next door.

Google's Core Web Vitals became ranking factors in 2021, but the impact is accelerating. Sites that don't meet the benchmarks lose visibility in local search results. For Irish businesses competing for "near me" searches, performance directly affects whether customers find you at all.

The challenges here connect directly to WooCommerce performance issues affecting Irish eCommerce.

The numbers tell the story. Only 43% of websites meet Core Web Vitals benchmarks as of mid-2025, according to New Target research. That means 60% of WordPress sites fall short of Google's basic performance standards. Your site might look professional, but if it's slow, it's invisible. This is explored further in image optimization and modern formats.

Mobile performance matters even more in Ireland. Mobile accounts for 55% of all WordPress site traffic, and Irish users are particularly mobile-first in their browsing behaviour. A slow mobile experience doesn't just frustrate users. It kills conversions. Research consistently shows that every additional second of load time reduces conversions by roughly 7-10%.

The stakes get higher when you consider Ireland's digital commerce gap. With €8.3 billion in opportunity sitting on the table, performance becomes the difference between capturing that growth and watching competitors take it.

Understanding Core Web Vitals for Irish Market Context

Core Web Vitals measure three specific aspects of user experience: Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS). Each one directly affects how Irish customers interact with your site.

LCP measures loading performance. Google wants this under 2.5 seconds. The average WordPress website loads in 2.9 seconds, which fails the standard. For Irish businesses, this matters because local search results prioritise fast-loading sites. A Dublin estate agent competing for "houses for sale Dublin" searches needs LCP under 2.5 seconds or Google demotes their listings.

Traditional vs Headless WordPress performance comparison explores how this plays out for real businesses.

FID measures interactivity. How long before users can click buttons or submit forms? Google wants this under 100 milliseconds. E-commerce sites suffer most from poor FID. A customer trying to add items to their basket shouldn't wait for the page to respond. They'll abandon the purchase.

CLS measures visual stability. Pages shouldn't jump around while loading. Irish businesses often struggle with this because of third-party widgets: booking systems, social media feeds, advertising banners. Each one can cause layout shifts that hurt your Core Web Vitals score.

Who Needs This Most?

This ties directly into comprehensive performance monitoring strategy, which explores the practical implications.

• E-commerce businesses: Poor Core Web Vitals kill checkout conversions. A customer ready to buy sees a slow-loading payment form and assumes your site isn't secure. They leave. You lose the sale and never know why.

• Lead generation businesses: A solicitor's firm in Sligo discovered their contact form had a 3-second FID. Potential clients filled out the form, clicked submit, nothing happened immediately, so they clicked again. The form submitted twice, creating confusion and missed leads.

• Service businesses: Local search rankings depend heavily on Core Web Vitals now. A slow-loading site drops in "near me" searches, reducing foot traffic and phone calls.

The good news? WordPress sites optimised correctly can achieve loading times under 2 seconds, meeting all Core Web Vitals standards. The challenge lies in implementation.

Server Location and CDN Strategy for Irish Businesses

Server location affects performance more than most Irish businesses realise. Hosting your site on servers in Ireland versus London or Amsterdam creates measurable latency differences for Irish visitors.

Physics determines network latency. Data travelling from Dublin to London takes roughly 20-30 milliseconds. Dublin to Amsterdam: 40-50 milliseconds. Dublin to US East Coast: 100+ milliseconds. These delays compound with every resource your page loads: images, stylesheets, scripts, fonts.

Most international hosting providers use their closest European data centre, typically London. For Irish businesses targeting Irish customers, this creates an unnecessary performance penalty. Every page load starts with extra latency that better server placement could eliminate.

Content Delivery Networks (CDNs) help, but they're not magic. CDNs can increase website speeds by up to 68%, according to Kinsta research, but only if configured properly. Many Irish WordPress sites use CDNs incorrectly, creating more round trips instead of fewer.

The strategic reality: Irish-based hosting provides a performance advantage that compounds with proper optimisation. Web60's Dublin-based servers eliminate the London detour entirely, starting every page load 20-30 milliseconds faster than UK-based competitors.

The Ireland-First Performance Strategy:

1. Choose Irish hosting for your primary server location
2. Configure CDN caching for static assets (images, CSS, JavaScript)
3. Optimise database queries to reduce server processing time
4. Implement proper caching layers to minimise database hits
5. Monitor real user metrics from Irish locations specifically

If you're running enterprise e-commerce with customers across multiple continents and need 200+ CDN edge locations worldwide, Kinsta's global infrastructure genuinely suits that workload better. But most Irish businesses serve primarily Irish customers and benefit more from local hosting with targeted CDN support.

WordPress Caching: The Complete Implementation Guide

Caching transforms WordPress performance more dramatically than any other single optimisation. Properly configured caching can reduce WordPress load times by up to 50%, according to performance research. But most Irish businesses implement caching wrong.

WordPress generates every page dynamically by default. Each visitor triggers database queries, PHP processing, and HTML generation. For a brochure site getting 100 visits per day, this works fine. For an active business site, it creates unnecessary server load and slower response times.

Page Caching: The Foundation

Page caching stores the final HTML output and serves it directly to subsequent visitors. Instead of regenerating the same "About Us" page 50 times per day, the server generates it once and serves the cached version 49 times.

Web60's FastCGI page caching handles this automatically at the server level. Most shared hosting providers require plugins like WP Rocket or W3 Total Cache, which add complexity and potential conflicts.

Object Caching: The Performance Multiplier

Object caching stores database query results in memory. When WordPress needs the same data repeatedly, navigation menus, widget content, user permissions, object caching serves it from RAM instead of querying the database.

Redis object caching, included in Web60's managed stack, can improve database-heavy sites by 30-70%. E-commerce sites with complex product catalogues see the biggest gains.

Browser Caching: The Visitor Experience

Browser caching tells visitors' browsers to store certain files locally: images, stylesheets, JavaScript files. Return visitors load these from their local cache instead of downloading them again.

Property configured browser caching can reduce page load times by 40-60% for return visitors. But it requires correct HTTP headers, expiry times, and cache-busting for updated files.

The Dead Simple Caching Workflow

Step 1: Verify. Check your current cache hit rate using your hosting provider's tools or plugins like Query Monitor. Aim for 80%+ cache hits on most pages.

Step 2: Configure. Enable page caching, object caching, and browser caching. Set appropriate expiry times: 1 hour for dynamic content, 1 week for images, 1 month for rarely-changed assets.

Step 3: Test. Use GTmetrix or PageSpeed Insights to measure before and after performance. Look for improvements in TTFB and overall load times.

Step 4: Monitor. Cache systems occasionally show logged-in customers stale content. Set up monitoring to catch this before customers report it.

The Cache Reality Check:

Aggressive caching occasionally shows logged-in customers outdated product pages or pricing. It's rare, happening roughly 1-2% of the time with complex e-commerce setups. When it happens, a cache flush fixes it in seconds. Worth knowing before a customer reports it first.

Database Optimisation for High-Traffic Irish Sites

WordPress databases accumulate performance-killing bloat over time. Post revisions, spam comments, transient data, and plugin leftovers slow down every page load. A café in Temple Bar discovered their database had 15,000 post revisions from menu updates, adding 200 milliseconds to every page load.

Database optimisation isn't glamorous, but it's essential for sites handling significant traffic or content updates. Irish businesses running WooCommerce, membership sites, or high-content blogs need proactive database maintenance.

The Performance Killers:

• Post revisions: WordPress saves every draft and update. A blog with 100 posts might have 500+ revisions.
• Transient data: Temporary data that should expire but sometimes doesn't, especially from poorly-coded plugins.
• Spam and trash: Deleted comments and posts that remain in the database.
• Orphaned metadata: Plugin data that remains after plugins are deactivated.
• Autoloaded options: Data WordPress loads on every page request, including inactive plugin settings.

Database Maintenance Tasks:

1. Limit post revisions to 3-5 per post maximum
2. Clean expired transients monthly
3. Remove spam and trash permanently, don't just mark as deleted
4. Optimise database tables quarterly using phpMyAdmin or WP-CLI
5. Review autoloaded options and remove unnecessary data

WooCommerce sites need additional attention. Product variations, order data, and customer information create complex queries. Regular database optimisation becomes critical as the store grows.

WooCommerce-Specific Optimisation:

• Index frequently-queried columns like product IDs and order dates
• Archive old order data rather than deleting it
• Optimise product variation queries using dedicated plugins
• Clean up abandoned carts older than 30 days
• Remove expired coupon codes and promotional data

The biggest database performance gain comes from reducing autoloaded data. WordPress loads this data on every single page request. Inactive plugins often leave autoloaded options behind, slowing down the entire site even after deactivation.

A Limerick accountancy firm reduced their Time To First Byte from 800ms to 300ms just by cleaning up autoloaded options left behind by old plugins. The difference was immediately noticeable to visitors.

Image Optimisation and WebP Implementation

Images typically account for 60-70% of total page weight on WordPress sites. Unoptimised images kill performance faster than any other factor. A gift shop in Killarney during tourist season learned this when high-resolution product photos made their mobile site unusable.

Image optimisation isn't just about file size. It's about delivering the right image format, dimensions, and quality for each visitor's device and connection speed.

WebP: The Modern Standard

WebP images are 25-35% smaller than equivalent JPEG files while maintaining the same visual quality. All modern browsers support WebP, making it the optimal format for web delivery. Yet many Irish WordPress sites still serve only JPEG and PNG files.

WordPress 5.8+ supports WebP uploads natively, but most sites need conversion tools for existing image libraries. Plugins like Imagify or EWWW Image Optimiser can convert entire media libraries automatically.

Responsive Images: Critical for Mobile

Serving desktop-sized images to mobile users wastes bandwidth and slows loading. WordPress generates multiple image sizes automatically, but themes must implement them correctly using srcset attributes.

A properly optimised responsive image system serves:

• Mobile: 400-600px wide images
• Tablet: 800-1000px wide images
• Desktop: 1200-1600px wide images
• Retina displays: 2x resolution variants when necessary

Lazy Loading: Load What's Visible

Lazy loading defers image loading until users scroll to them. WordPress 5.5+ includes native lazy loading, but it's basic. Advanced lazy loading with placeholder images and fade-in effects requires dedicated plugins or custom implementation.

Lazy loading can reduce initial page load times by 30-50% on image-heavy sites. E-commerce product pages and photo galleries see the biggest improvements.

The Complete Image Optimisation Workflow

Step 1: Audit. Use PageSpeed Insights to identify oversized images and missing WebP formats. Look for images larger than 100KB or serving desktop images to mobile users.

Step 2: Convert. Enable WebP generation for all new uploads and convert existing images using bulk optimisation tools. Maintain JPEG/PNG fallbacks for older browsers.

Step 3: Resize. Ensure responsive image sizes match your theme's layout. Remove unnecessary large image variants to save server storage.

Step 4: Deploy. Implement advanced lazy loading with proper placeholder images and smooth loading transitions.

Step 5: Monitor. Track Largest Contentful Paint improvements and image-related Core Web Vitals metrics.

One limitation to understand: aggressive image optimisation occasionally reduces visual quality more than expected, especially on high-DPI displays. The sweet spot is typically 80-85% quality for JPEG files and WebP equivalents. Test on actual devices rather than relying solely on automated tools.

Plugin Performance Auditing and Management

WordPress plugins are both the platform's greatest strength and its biggest performance liability. The average WordPress site runs 20-25 plugins, according to Plugin Audit research. Each plugin adds code, database queries, and potential conflicts.

I recommended a popular page builder to a client in Cork three years ago. Their PageSpeed score dropped 20 points the week after launch. Took me a while to connect the dots. Would not make that call again.

The Plugin Performance Hierarchy

Not all plugins affect performance equally. Understanding which types cause the most damage helps prioritise optimisation efforts.

High Impact (Avoid or Replace):

• Page builders (Elementor, Divi, Visual Composer)
• Social media feed plugins
• Real-time chat widgets
• Comprehensive SEO plugins with excessive features
• Slider and carousel plugins

Medium Impact (Use Carefully):

• E-commerce plugins (WooCommerce is well-optimised, many extensions aren't)
• Form builders with complex styling
• Analytics and tracking plugins
• Security plugins with real-time scanning

Low Impact (Generally Safe):

• Simple contact forms
• Basic SEO plugins (Yoast, RankMath)
• Code snippet plugins
• Backup plugins (if configured properly)
• Simple caching plugins

Plugin Auditing Process

1. Identify performance impact using Query Monitor or P3 Profiler
2. Remove unused plugins completely, don't just deactivate
3. Replace heavy plugins with lighter alternatives
4. Optimise remaining plugins by disabling unnecessary features
5. Test performance before and after each change

The biggest mistake Irish businesses make is accumulating plugins over time without ever removing them. Each "small" plugin adds 50-200 milliseconds of load time. Ten plugins equal 1-2 seconds of additional loading.

Common Plugin Conflicts:

• Multiple caching plugins running simultaneously
• SEO plugins with overlapping features
• Security plugins with conflicting rules
• Form plugins that load scripts on every page
• Social sharing plugins with external API calls

A Cork hair salon trying to compete with chain franchises discovered they were running three different contact form plugins, two SEO plugins, and a page builder they'd stopped using six months earlier. Cleaning up plugins improved their mobile PageSpeed score from 42 to 78.

Strategic Plugin Selection:

Choose plugins that solve multiple problems rather than single-purpose tools. WooCommerce handles e-commerce, payments, and inventory in one plugin. Yoast SEO manages meta titles, sitemaps, and structured data together. ConvertKit handles email marketing, forms, and landing pages.

Avoid plugins that duplicate WordPress core functionality. WordPress 5.5+ includes native lazy loading, 5.0+ includes a block editor, 4.4+ includes responsive images. Many "optimisation" plugins solve problems WordPress already handles.

Mobile Performance for Irish User Behaviour

Mobile performance matters more in Ireland than global averages suggest. Irish users are particularly impatient with slow mobile sites, often abandoning pages within 2-3 seconds if they don't start loading immediately.

Irish Mobile Context:

• 55% of WordPress traffic comes from mobile devices
• Mobile users have zero tolerance for slow checkout processes
• "Near me" searches are predominantly mobile
• Rural areas still have variable mobile connectivity despite NBP improvements

Mobile Performance Challenges:

Mobile devices have less processing power and memory than desktop computers. JavaScript that runs smoothly on desktop can freeze mobile browsers. Images that look crisp on desktop consume excessive mobile bandwidth.

The biggest mobile performance killer is render-blocking resources. CSS and JavaScript files that prevent the page from displaying until they finish loading. Mobile users see blank screens while desktop users see partial content.

Mobile-First Optimisation Strategy:

1. Test on actual devices, not just browser dev tools
2. Prioritise above-the-fold content loading first
3. Eliminate render-blocking resources or defer them
4. Reduce JavaScript execution time on mobile CPUs
5. Optimise touch targets and interaction delays

Critical Rendering Path Optimisation:

The critical rendering path determines how quickly mobile users see content. Optimising this path involves:

• Inline critical CSS for above-the-fold content
• Defer non-critical JavaScript until after initial render
• Preload essential fonts to prevent text flashing
• Eliminate unnecessary third-party scripts that block rendering

A Waterford manufacturer with a trade catalogue site reduced mobile bounce rates from 68% to 31% by optimising their critical rendering path. The site looked the same but loaded content 2.3 seconds faster on mobile devices.

Mobile Performance Testing:

Desktop performance tools don't accurately reflect mobile experience. Use mobile-specific testing:

• Google PageSpeed Insights mobile score (separate from desktop)
• WebPageTest on actual mobile devices (not emulated)
• Chrome DevTools mobile throttling with CPU slowdown enabled
• Real user monitoring from mobile visitors specifically

The performance gap between desktop and mobile often reveals optimisation opportunities. Sites that score 85+ on desktop PageSpeed but 45-60 on mobile typically have render-blocking resources and oversized images.

Monitoring and Measuring Performance Improvements

Performance optimisation without measurement is guesswork. Irish businesses need consistent monitoring to understand their site's real-world performance and catch issues before customers notice them.

The Monitoring Stack:

1. Google PageSpeed Insights: Free baseline measurement
2. GTmetrix: Detailed waterfall analysis and historical tracking
3. Real User Monitoring (RUM): Actual visitor experience data
4. Server monitoring: Resource usage and response times
5. Uptime monitoring: Availability and response tracking

Key Metrics to Track:

• Time to First Byte (TTFB): Server response speed
• First Contentful Paint (FCP): When users see content
• Largest Contentful Paint (LCP): Main content loading
• Cumulative Layout Shift (CLS): Visual stability
• Total Blocking Time (TBT): JavaScript execution delays

Setting Performance Baselines:

Measure current performance before making changes. Document:

• PageSpeed Insights scores (mobile and desktop)
• GTmetrix load times and page sizes
• Core Web Vitals field data from Search Console
• Bounce rates and conversion rates from Analytics

A Dublin-based estate agent tracked these metrics for three months before optimisation, then monitored improvements over six months afterward. The data showed direct correlation between LCP improvements and increased contact form submissions.

Performance Monitoring Best Practices:

1. Test from multiple locations, not just Dublin
2. Monitor during peak traffic periods as well as quiet times
3. Track mobile and desktop separately
4. Set up alerts for performance regressions
5. Review monthly trends, not just daily snapshots

The monitoring reality: performance can degrade gradually without obvious symptoms. Plugin updates, theme changes, increased traffic, and database growth all affect speed over time. Monthly performance audits catch issues before they become customer problems.

Interpreting Performance Data:

Good performance monitoring reveals patterns:

• Gradual slowdowns: Usually database or plugin-related
• Sudden drops: Often caused by plugin updates or server issues
• Peak-hour problems: Server resource or caching limitations
• Mobile-specific issues: Render-blocking resources or oversized images

Web60's built-in performance monitoring dashboard tracks these metrics automatically, alerting customers when performance drops below acceptable thresholds. This proactive approach prevents performance problems from affecting revenue.

Advanced Performance Techniques for Enterprise Sites

High-traffic WordPress sites need enterprise-level performance techniques beyond basic caching and image optimisation. These advanced strategies handle thousands of concurrent visitors and complex functionality demands.

Edge-Side Includes (ESI) for Dynamic Content

ESI allows caching static page portions while keeping dynamic elements fresh. User-specific content like shopping carts or personalised recommendations stay current while navigation, headers, and product information come from cache.

Implementing ESI requires advanced hosting infrastructure and careful cache configuration. Most shared hosting providers don't support ESI properly, making it unsuitable for smaller sites.

Advanced Database Strategies

Query Optimisation:

• Index frequently-searched columns
• Eliminate N+1 queries in theme and plugin code
• Use persistent database connections
• Implement query result caching

Database Scaling:

• Read/write splitting for high-traffic sites
• Connection pooling to handle concurrent users
• Query monitoring and slow query optimisation
• Scheduled maintenance during low-traffic periods

Content Delivery Network (CDN) Optimisation

Advanced CDN configuration goes beyond basic static file delivery:

• Dynamic content caching at edge locations
• API response caching for AJAX-heavy sites
• Image processing at CDN edge (resizing, format conversion)
• Geo-targeting for region-specific content
• Mobile-specific optimisations at CDN level

Performance-First Development Practices

Enterprise WordPress sites need development workflows that prioritise performance:

1. Performance budgets for each page type
2. Automated performance testing in deployment pipelines
3. Code reviews focusing on performance impact
4. Asset bundling and minification workflows
5. Critical CSS generation automated processes

Load Balancing and Redundancy

High-availability WordPress setups distribute traffic across multiple servers:

• Application-level load balancing with session affinity
• Database replication for read scaling
• File synchronisation across web servers
• Failover mechanisms for server outages
• Geographic load distribution for international audiences

These techniques require significant technical expertise and infrastructure investment. They're justified for sites handling 100,000+ monthly visitors or mission-critical e-commerce operations.

When Enterprise Techniques Are Overkill:

Most Irish SMEs don't need enterprise-level performance infrastructure. A well-optimised WordPress site on quality managed hosting handles 10,000-50,000 monthly visitors without advanced scaling techniques.

The ROI calculation matters: enterprise performance infrastructure costs €500-2000+ monthly. Basic performance optimisation on managed hosting costs €60-200 monthly and handles most business requirements effectively.

To see how this works in practice, explore Web60's built-in performance stack handles advanced caching, database optimisation, and monitoring automatically.

Conclusion

WordPress performance optimisation transforms Irish businesses' online success. From Core Web Vitals compliance to mobile-first design, every element affects revenue and customer experience. The National Broadband Plan creates unprecedented opportunity for Irish businesses, but only those with fast-loading websites will capitalise fully.

Start with the foundations: reliable hosting, proper caching, and image optimisation, and remember that a comprehensive WordPress security and backup strategy for Irish businesses is equally essential to protect the performance gains you achieve. Monitor performance consistently and address issues before customers notice them. Advanced techniques matter for high-traffic sites, but most Irish businesses achieve excellent results with fundamental optimisations implemented correctly.

Web60's performance-optimised WordPress hosting eliminates the technical complexity while delivering Dublin-server speeds and automatic optimisation. Your business deserves infrastructure that works as hard as you do.

Frequently Asked Questions

What are Core Web Vitals and why do they matter for Irish businesses?

Core Web Vitals are Google's user experience metrics that became ranking factors in 2021: Largest Contentful Paint (loading), First Input Delay (interactivity), and Cumulative Layout Shift (visual stability). For Irish businesses, poor Core Web Vitals scores reduce visibility in local search results, affecting 'near me' searches and local competition. Sites meeting these standards rank higher and convert better.

How much can WordPress caching improve my site's performance?

Properly configured caching can reduce WordPress load times by 40-50% according to performance research. Page caching eliminates database queries for repeat content, object caching stores frequently-accessed data in memory, and browser caching reduces repeat visitor load times by 40-60%. The improvement depends on your current setup and traffic patterns.

Does server location really matter for Irish website performance?

Yes, server location creates measurable performance differences. Dublin to London adds 20-30ms latency, Dublin to Amsterdam adds 40-50ms. While this sounds minimal, it compounds with every resource your page loads. Irish hosting eliminates this latency entirely, providing a performance advantage for sites targeting Irish audiences.

Which WordPress plugins hurt performance most?

Page builders like Elementor cause the biggest performance impact, often adding 1-2 seconds to load times. Social media feed plugins, real-time chat widgets, and comprehensive SEO plugins with excessive features also significantly slow sites. The key is auditing plugin performance impact and replacing heavy plugins with lightweight alternatives.

How do I know if my WordPress site needs performance optimisation?

Test your site using Google PageSpeed Insights and GTmetrix. Scores below 70 on mobile or load times above 3 seconds indicate optimisation needs. Also watch for high bounce rates, low conversion rates, and customer complaints about slow loading. Core Web Vitals data in Google Search Console shows real user experience metrics.

What's the difference between mobile and desktop WordPress performance?

Mobile devices have less processing power and memory, making JavaScript-heavy sites much slower on mobile than desktop. Mobile users also have less patience, abandoning sites within 2-3 seconds. Render-blocking resources that barely affect desktop can freeze mobile browsers completely. Always test and optimise specifically for mobile performance.

Can I optimise WordPress performance myself or do I need technical help?

Basic optimisation, installing caching plugins, optimising images, removing unused plugins, can be done without technical expertise. Advanced techniques like database optimisation, server configuration, and CDN setup typically require technical knowledge. Managed WordPress hosting handles most optimisation automatically.

How often should I monitor my WordPress site's performance?

Check performance monthly for trending changes and immediately after any major updates, plugin installations, or theme changes. Set up automated monitoring to alert you when performance drops below acceptable levels. Performance can degrade gradually from database growth, plugin updates, and increased traffic without obvious symptoms.

Sources

DiviFlash - WordPress Statistics (January 2026): https://diviflash.com/wordpress-statistics/

New Target - Core Web Vitals Statistics (September 2025): https://www.newtarget.com/web-insights-blog/core-web-vitals/

BeBusinessed - WordPress Performance Statistics (September 2024): https://bebusinessed.com/statistics/50-wordpress-statistics-and-facts/

National Broadband Ireland - 100,000 Connections Milestone (October 2024): https://nbi.ie/news/events/2024/10/25/national-broadband-ireland-has-connected-100000-homes-and-businesses-nationwide/

Government of Ireland - National Broadband Plan Evaluation (November 2024): https://www.gov.ie/en/department-of-climate-energy-and-the-environment/press-releases/national-broadband-plan-benefits-outlined-in-independent-evaluation-report/

Kinsta - WordPress CDN Performance Research (July 2022): https://kinsta.com/blog/wordpress-cdn/

Perfmatters - GZIP Compression Statistics (June 2020): https://perfmatters.io/wordpress-performance-checklist/