We audit slow websites, find what actually delays each page, and fix it: images, scripts, fonts, caching and server response, measured before and after.
What does website speed optimization include?
Website speed optimization includes measuring how your key pages load, tracing each delay to its cause and fixing it. Cairo Studio audits Lighthouse and real-user Core Web Vitals, then resizes images, loads fonts properly, splits code, delays third-party scripts and sets up caching, finishing with a before and after report on the same pages.
Audit and measurement
Lighthouse lab testing
Core Web Vitals field data
Search Console review
Network waterfall analysis
JavaScript bundle analysis
+
Loading performance
Image sizing and modern formats
Lazy loading below the fold
Font subsetting and preloading
Code splitting by route
Critical CSS
+
Stability and responsiveness
CLS fixes with reserved space
INP and long task reduction
Third-party script audit
Deferred tag managers and pixels
+
Server and delivery
Cache headers
CDN setup
Server response time
CMS and API response caching
Redirect chain cleanup
=Website Speed Optimization and Core Web Vitals
Overview
Website speed optimization that starts with real measurements
Website speed optimization is the work of finding why a page loads slowly and removing the cause, not chasing a single score. A slow site costs you twice: visitors leave before the page appears, and Google uses Core Web Vitals as one of the signals in how it ranks pages. Few changes help SEO and conversions at the same time, and speed is one of them.
This is for businesses whose site feels sluggish on mobile, whose landing pages lose visitors in the first seconds, or whose Search Console report flags poor URLs. It applies to custom builds, WordPress, Shopify and headless sites alike. In Egypt and the Gulf many visitors browse on phones over mobile data, so a page that feels fine on office Wi-Fi can be slow for the people you are paying to reach.
01 / 04
What a page speed audit looks at
We test on real phones over mobile data.
We start with lab data from Lighthouse and real-user data from the Chrome UX Report and Search Console, because the two often disagree. Lab tests show what a page can do under controlled conditions; field data shows what your visitors actually experience. Then we trace each slow page to specific causes.
Largest Contentful Paint (LCP): oversized hero images, late fonts, slow server response
Cumulative Layout Shift (CLS): images without dimensions, banners and embeds that push content down
Interaction to Next Paint (INP): heavy JavaScript that delays taps and clicks
Third-party scripts: chat widgets, tag managers, pixels and trackers loading on every page
Server and caching: uncached HTML, no CDN, slow database or CMS queries
02 / 04
How we fix LCP and CLS
Every fix is timed before and after.
Most LCP problems come down to the main image or heading arriving late. We resize and compress images to the size they are actually displayed at, serve modern formats such as WebP and AVIF, preload the hero image and lazy load everything below the fold. Fonts are subset, self-hosted where possible and loaded so text shows immediately.
Layout shift is fixed by reserving space: explicit width and height on images and video, fixed slots for embeds and banners, and fallback fonts matched in size so text does not jump when the custom font arrives. Arabic fonts get the same treatment, since they are often the heaviest files on a bilingual page.
03 / 04
Code splitting, caching and third-party scripts
Caching and hosting are checked, not only the code.
On JavaScript-heavy sites we split code by route so each page loads only what it needs, defer animation libraries until they are used and remove dead dependencies. We set cache headers properly, serve static assets from a CDN and, where the stack allows, cache rendered pages and CMS responses so the server answers quickly. Every third-party script gets a hard look: it is kept, delayed or removed based on what it is worth to the business.
04 / 04
How Cairo Studio approaches website speed optimization
We test on real phones over mobile data.
We build sites in SvelteKit, Next.js and Astro with Prismic, and we audit our own site with Lighthouse, so the same discipline goes into client work. We fix what moves the numbers for real users first, avoid changes that would damage the design or the way your team edits content, and report before and after on the same pages so you can see exactly what changed and why.
A speed project is measured at the start and the end, with fixes ranked by impact in between.
A→B
How we work
01
Baseline measurement
We pick the pages that matter most, usually the homepage, top landing pages, product or service templates, and checkout or contact flows. We record Lighthouse results on mobile and desktop alongside real-user Core Web Vitals, so every later change is compared against the same baseline.
A→B
02
Root cause audit
For each slow page we read the network waterfall, the JavaScript bundle and the rendering timeline. We list every cause we find, from a heavy hero image to a chat widget that blocks the main thread, and rank them by impact on real users and the effort needed to fix them.
03
Low-risk fixes first
We start with changes that carry little risk and pay off quickly: resizing and converting images, adding dimensions, lazy loading, font loading, cache headers and removing unused scripts. These often clear the worst problems without touching the design or the way your team edits content.
04
Structural fixes
Deeper problems need code: splitting bundles by route, moving rendering to the server, caching API and CMS responses, or replacing a heavy plugin with lighter code. When a site is slow by design, we may recommend rebuilding templates, and we explain why before you commit to it.
05
Verify and monitor
We measure the same pages again in Lighthouse and wait for field data to catch up, since real-user numbers take weeks to reflect changes. You get a before and after report, and we can set up ongoing checks so new scripts, images or features do not quietly slow the site down again.
Selected work0123/ 03
Web Development, UI/UX Design, E-commerceWeb Development, UI/UX Design, E-commerceUI/UX Design, Web Development, Creative Direction
It depends on what is causing the slowness. An audit with fixes to images, fonts and caching is a contained piece of work. If the problems sit in the theme, a page builder or the site's architecture, the fixes take longer and sometimes mean rebuilding templates. We scope the cost after the audit, once the causes are known.
141516---
1718
#
Phones have slower processors and often slower connections, so heavy JavaScript and large images hurt far more there. Lighthouse tests mobile with throttling for that reason. Much of the gap comes from scripts that take time to run on the device, not from the download itself, so that is where we look first.
192021---
22
#
Yes. They are part of Google's page experience signals, though relevant content still matters more. Speed rarely lifts a weak page to the top, but between pages of similar quality it can make the difference. The bigger effect is often on conversions: faster pages keep more of the visitors you already rank for.
232425---
262728
#
Usually, yes. On WordPress we look at plugins, theme weight, image handling and caching. On Shopify we audit apps, theme code and third-party scripts, since apps often inject code on every page. If the platform itself is the limit we will tell you, but most sites have room to improve before that point.
293031---
3233
#
No. Lighthouse scores vary between runs and devices, and a perfect lab score does not always mean a fast experience for real users. We commit to finding the causes, fixing them and showing before and after measurements on the same pages, using both Lighthouse and real-user data.
343536---
37
#
Lab results change as soon as fixes are deployed. Real-user Core Web Vitals in Search Console are averaged over a rolling 28-day window, so they take several weeks to fully reflect the changes. Rankings, if they move, follow after that. We report at each stage so you know what to expect and when.