Speed audit
We test key templates in PageSpeed Insights and Lighthouse and check Core Web Vitals field data in Search Console, when it is available.
We find what actually slows your site down – heavy images, trackers and widgets, a slow server response – and fix it in the code. Our own website scores 96 for mobile performance, and this page shows how we got there.
We work on causes, not on scores for a screenshot: every change has to cut the time it takes a visitor to see the page and start using it.
We test key templates in PageSpeed Insights and Lighthouse and check Core Web Vitals field data in Search Console, when it is available.
WebP copies, sizes that match the screen, lazy loading below the fold and high priority for the main image.
GTM, pixels, Clarity, chats and widgets start after the visitor’s first interaction, so they stay out of the way of loading.
We remove render-blocking resources and load only the font weights the site actually uses.
Page cache, compression, cache headers for static files. We cut the server response time (TTFB).
Images, banners and embeds get fixed dimensions, so the page doesn’t jump while it loads (CLS).
We turn off libraries where they aren’t needed and untangle heavy handlers that delay the response to a tap (INP).
A before-and-after comparison and advice on keeping new blocks and plugins from pushing the site back into the red.
The best example is the site you are reading right now. We built it ourselves and checked every release in PageSpeed Insights. Below are the scores for /locations/dubai/ on mobile and desktop.
Desktop, PageSpeed Insights, /locations/dubai/
We record the starting PageSpeed and Core Web Vitals scores for key pages: home, catalog, product page, article.
A list of causes, each with its impact and effort. Before any work starts, you see what each change will give.
We make the changes on a staging copy, check that nothing broke and then move them to the live site.
New measurements, a before-and-after comparison and advice on keeping the site fast.
You know in advance what you will get, what it costs and when it will be ready.
We sign a contract and a non-disclosure agreement before work begins.
The stage price does not change during work. New tasks only after approval.
A staging server you can access: see what's done without waiting for the finish.
We hand over the source code, documentation and all access. The project is not tied to us.
After launch, we fix bugs found within the delivered scope for free.
We stay in touch: improvements, updates and growth, monthly or per task.
Leave your name and e-mail – we’ll reply by e-mail within one business day.
The lab test runs on Google’s servers and depends on their load, the network and third-party scripts on the page. A few points of variation is normal. That is why we compare several runs and look at Core Web Vitals field data – real visitors to your site over the last 28 days.
Core Web Vitals are one of the signals Google uses in ranking, but not the main one: content matters more. Speed has a bigger effect on behaviour – people close a slow site before it loads, especially on a phone. More on rankings on our SEO page.
Yes. On WordPress, WooCommerce and OpenCart we work with the theme, plugins and server. On Shopify the server and cache belong to the platform, so we optimize the theme, images and third-party apps.
Not always. First we look at what makes up the server response time. If the server is slow because of the code or a missing cache, moving won’t help. If it is running out of resources, we’ll tell you and suggest options.
It depends on the platform, the number of templates and what exactly is slowing the site down. After the first measurements we give a fixed price and scope.
Speed drops when new plugins, widgets and heavy images are added. Optimization can be a one-off project, or we can take the site on development and support and check speed after each release.
↗13Improvements and supportWe take over projects from other contractors, implement SEO specialists' specs and provide monthly support.
↗11SEOTechnical audit, structure, content and links. Growth in organic traffic and rankings.
↗06CRO – conversion growthWe find where the funnel loses customers, rework the product page, cart and checkout, and verify with A/B tests.
↗01Online storesCatalogs with thousands of products, filters, online payment, delivery, feeds to marketplaces and price aggregators.Speeding up a website means working on what a visitor sees in the first seconds: how fast the first screen appears, when they can press a button and whether the layout jumps. Google measures this with Core Web Vitals – LCP, INP and CLS – and shows them in PageSpeed Insights.
We don’t chase a score of 100 for a screenshot. The goal is a page that opens quickly on an ordinary phone over mobile data. Our own site shows what that looks like: 96 for mobile performance and an LCP of 0.5 s on desktop.
How to find each of these causes in the report and fix it is covered in our guide how to optimize a page for PageSpeed, with a checklist at the end.
If you are planning a new site, it is easier to build speed in from the start than to fix it later. When migrating, it matters not to lose rankings – see our site migration checklist. The platform also affects what can be optimized: compare them in OpenCart, WooCommerce, Shopify or Laravel.
A fast site doesn’t sell on its own, but a slow one loses buyers before the first screen appears. That is why speed is one of the points in our CRO checklist for online stores and part of our conversion optimization work. If you rely on search traffic, it pairs well with SEO, and development and support helps keep the result.
Describe your task – within one business day we'll reply with questions and a rough timeline estimate.
We’ll reply within one business day with questions about the task and a preliminary timeline estimate.
We'll review your site or idea and tell you what to do first. We reply within one business day – by e-mail, Telegram or WhatsApp.