Ikone Textile customizes clothing, accessories, promotional items, and communication materials for businesses, associations, and events. Its WooCommerce store features a large catalog, product pages with variations, and an online quote request form.
On mobile, however, the homepage scored 34/100 on PageSpeed Insights, and the main image took nearly 14 seconds to appear in a lab measurement. In a single intervention, without a redesign, without changing the theme or the page builder, the mobile score rose to 95 and the desktop score from 62 to 97. Here is how we proceeded.
The starting point: a complete but heavy site
The site is built on WordPress, WooCommerce, and Elementor Pro, with a cache plugin (Litespeed) and a CDN already in place. The foundation was sound. What weighed it down was the accumulation of resources loaded on every page, from the very first second:
- 1.2 MB of stylesheets to download before anything could be displayed, regardless of the page visited;
- 85 JavaScript files, totaling 2.4 MB, executed as soon as the page opened;
- external services (chat, email marketing, customer reviews) accounting for around 750 KB on their own;
- background images loaded immediately, even when they were far below the fold.
On desktop, the display remained acceptable, but the browser was occupied for more than one second by scripts (1,240 ms of blocking time): during that time, the page does not respond to clicks.
Our method: measure, fix, verify
- Audit of the homepage, then of the key templates: category, product page, and sales funnel.
- Identification of what blocks rendering and what occupies the processor.
- Fixes applied one by one, each reversible and documented.
- Visitor testing after each step, on mobile and desktop: mobile menu, quote popup, product variations, cart, login.
- Repeated measurements on PageSpeed Insights, with preloaded cache, to compare reliable results.
Each change is recorded in an intervention log, with the rollback procedure. The client remains in control of their site at all times.
What we optimized
Load only the CSS useful for each page
Instead of imposing 1.2 MB of styles before displaying anything, each page receives only the rules needed for its initial rendering, calculated on the server. The volume drops to around 476 KB, i.e. 53 KB actually transferred thanks to compression. The rest of the styles then arrive without blocking rendering.
Start JavaScript at the first interaction
The site’s scripts start as soon as the visitor scrolls the page, touches the screen, or moves the mouse, and at the latest after a few seconds. A click made before this startup is replayed automatically: no action is lost. The cart, checkout, and customer account are not affected and work exactly as before.
Defer external services
The chat, email marketing tool, and customer review widget load after the first interaction. Google Tag Manager, and with it the consent banner, starts right after the first render instead of delaying it.
Speeding up the hero image
The main image is the element that determines the LCP (Largest Contentful Paint), the most penalizing metric at the start. It is now preloaded at the correct size (a 768 px version on mobile) and served from the main domain, without waiting to open an additional connection to the CDN.
Lightening everything else
- off-screen background images loaded as the visitor approaches them: about 900 KB less on the initial load;
- unused libraries removed from pages that do not use them (tables, video player);
- fallback font adjusted to prevent any layout shift when the site font loads;
- fonts and icons that no longer delay text display.
The results
PageSpeed Insights measurements for the homepage, before and after the intervention.
| Mobile | Before | After |
|---|---|---|
| Performance score | 34 | 95 |
| First Contentful Paint | 4.2 s | 1.5 s |
| Largest Contentful Paint | 13.8 s | 2.4 s |
| Total Blocking Time | 1,320 ms | 100 ms |
| Speed Index | 8.4 s | 4.0 s |
| Desktop | Before | After |
|---|---|---|
| Performance score | 62 | 97 |
| First Contentful Paint | 0.7 s | 0.4 s |
| Largest Contentful Paint | 1.2 s | 0.6 s |
| Total Blocking Time | 1,240 ms | 150 ms |
| Speed Index | 2.4 s | 0.5 s |
The other page templates follow: 93 on mobile for a category page and 81 on mobile, 97 on desktop for a product page, the site’s richest page. PageSpeed scores vary by a few points from one run to another: we always use several measurements rather than a single flattering result.
What about real visitor data?
PageSpeed Insights also displays field data from Chrome visitors. It is calculated over a rolling 28-day period: immediately after the work is done, it still partly reflects the old site and improves over the following weeks. This is the data Google uses to assess Core Web Vitals, so we monitor it until it stabilizes.
Next avenues to go further: an even lighter mobile homepage image and a reduced server response time.
Key takeaways
A WooCommerce store built with Elementor can achieve excellent scores without a redesign. The key: load only what is necessary, at the right time, and test like a real visitor after each change. This is the approach we apply in our WordPress performance optimization projects.
Is your WordPress site slow? We optimize it without a redesign.
Frequently asked questions
Do you need to rebuild your site to improve your PageSpeed score?
No. For Ikone Textile, the theme, Elementor Pro, and all the store’s features were kept. The improvement comes from the way resources are loaded: what is useful for the initial display is prioritized, while the rest waits its turn.
How long does it take to see results?
PageSpeed Insights lab measurements improve as soon as the optimizations go live. Real visitor data, used by Google for Core Web Vitals, is calculated over a rolling 28-day period: it improves gradually over that time.
Can deferring JavaScript break functionality?
Yes, if it is done without testing. That is why each step is followed by a full acceptance test as a visitor, on mobile and desktop, and sensitive pages such as the cart, checkout, and customer account are excluded from deferral.
Does a better PageSpeed score improve SEO?
Core Web Vitals are among the signals taken into account by Google, among many others. Their primary effect is mainly seen in the visitor experience: a page that loads quickly retains more prospects and buyers.
