Performance
—
Display and response speed, under the test conditions.
Speed optimization for your site, measured before and after
Your site is slow, Search Console flags your Core Web Vitals, or your PageSpeed score no longer moves. We fix the cause at the source, then compare the same pages.
A slow site is felt before it is measured
The problem
The page takes a while to appear. A tap on the menu doesn’t react right away. Google Search Console sends an alert about Core Web Vitals. A caching plugin sometimes pushes the score back up, but it can break some features, and the gain fades as the site evolves.
Our approach
Website speed optimization fixes what really weighs the site down: the code, the images, the fonts, the third-party scripts, the server. It also improves perceived speed, what appears first and how the page reacts to a click, for smoother browsing. A layer of caching on an already heavy site only hides the problem.
Measure a page right now
The test uses Google’s PageSpeed tool. It gives a lab score. Real visits, when Google has them, appear separately.
The address is sent to Google (PageSpeed Insights) for the measurement. This site also loads the page once to read its technical headers (CMS, cache, CDN). Each result is kept for 90 days behind its own link, so you can share it. Nothing is stored in an account or tied to your name.
Results are kept for 90 days.
Mobile
Accessibility
—
Automated checks only. A WCAG audit also needs manual tests.
Technical SEO
—
Tags, indexing and technical basics seen by the tool. Not your rank in Google.
Best practices
—
HTTPS, console errors, libraries at risk.
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Delay before the page responds to a click. Mostly a real-user metric. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Time scripts keep the page busy and unable to respond. Lab only. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the first content is displayed. Good: 1.8 s or less.
What Google flags
Computer
Performance
—
Display and response speed, under the test conditions.
Accessibility
—
Automated checks only. A WCAG audit also needs manual tests.
Technical SEO
—
Tags, indexing and technical basics seen by the tool. Not your rank in Google.
Best practices
—
HTTPS, console errors, libraries at risk.
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Delay before the page responds to a click. Mostly a real-user metric. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Time scripts keep the page busy and unable to respond. Lab only. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the first content is displayed. Good: 1.8 s or less.
What Google flags
What we would look at
Fill out the form to get a quote
“*” indicates required fields
Fix speed where it is lost
The PageSpeed score is a good benchmark, not the only one. We aim for faster pages for your visitors, starting with the ones that bring in inquiries or sales.
Optimize without rebuilding
We start from the site as it is, page builder included, and optimize it as far as it goes: unneeded plugins removed, scripts deferred, animations lightened, theme settings reviewed. The problem is fixed, not hidden.
Score and real visits
Lighthouse simulates a phone and a connection. Real-world data (CrUX, the Core Web Vitals report) describes your visitors. The two are read together.
Responsiveness, not just loading
A page can appear quickly and still be slow to react when you tap a menu or a button. Google measures that delay with INP (Interaction to Next Paint). Script-heavy sites often suffer from it, even when the display looks fine.
Server and Cloudflare
Images, fonts, HTTP caching and hosting are part of the project. With a page builder, a caching plugin is often necessary: we configure it after the fixes, making sure it doesn’t break anything. If your IT team allows it, Cloudflare adds a CDN (content delivery network) and protection in front of the site.
What you get
A short project, with the same pages measured at the start and at the end.
Starting measurement
Lighthouse and, if available, real-world data for the agreed pages.
Fixes at the source
Theme, images, fonts, third-party scripts, headers, hosting. Each fix is named.
Final measurement
The same pages, the same conditions, after the fixes.
Features checked
Forms, cart, menus and tracking tools are tested after each fix: the site gets faster without breaking anything.
Your site, your access
Nothing is installed on our side. You keep the hosting and the accounts.
Possible next step
A maintenance plan keeps the site healthy after the optimization: updates, monitoring and performance tracking.
Speed we have already worked on
PageSpeed optimization carried out during the Peripharm redesign.
Peripharm
Bilingual redesign, audit before launch, speed optimization and SEO in both languages.
- WordPress
How an optimization works
-
Pages and access
The pages to measure, the host, what must not change.
-
Measurement
Lab and real-world data, recorded before any fix.
-
Fixes
At the source, on staging, then checked.
-
Comparison
The same measurements, afterwards. You see the difference, not just a score.
Questions about speed
No. The Lighthouse score changes with the device, the connection and the third-party scripts. We measure the same pages before and after, and we deliver the difference.
Not to make it faster. Most slowdowns come from the theme, the images and the scripts. A redesign is only proposed if the site cannot be fixed.
PageSpeed is a lab test you can run again at will. The Core Web Vitals in the Search Console report describe real Chrome visitors, over 28 days. A site with little traffic often has no real-world data.
From 5 hours, or $625. The final price is a quote based on the starting point: a site that starts far behind often gains a lot in a few hours, while an already optimized site needs fine-tuning, which takes longer.
