Previous work
Share with me your pagespeed optimizations so far. I will explain why it might not have led to results yet, despite Lighthouse saying so.
Pagespeed audits
improve Core Web Vitals
Let's stop you from focussing on the wrong metrics, start prioritizing real e-commerce optimizations instead.
Pagespeed audit in a nutshell
Unlike an in-house pagespeed training, a pagespeed audit is specific to your webshop, no matter the platform your webshop is running on.
Nowadays better known as Core Web Vitals. I will cover perceived performance to technical UX, including third party contents. For example:
Pagespeed audit usage
You will receive a PDF file containing real user monitoring (RUM) data as well as recommendations with code-examples.
- Highlighting UX bottlenecks that nobody noticed before;
- As a product owner, you can use this as technical proof of current imperfections;
- As a dev-team, you can use it to extend and prioritize your in-house roadmap;
- Indication of costs and benefits per recommendation is included.
A pagespeed audit
your webshop visitors will applaud it
For whom
Product owner, devs or CEO's of merchant and agencies wanting to have a full understanding of competition, history and current bottlenecks.
Learnings
In-depth recommendations from developer to (your) developers. Get right to the core of your bottlenecks and opportunities.
About the costs
Tens of thousands of Euros.. if you choose to not address pagespeed + UX issues. See below for costs per setup.
A pagespeed audit
won't be about
- stressing on perfect Lighthouse score
- loading time experience with your computer
- Core Web Vitals metrics only
- or just passing Google ranking
- which plugins or build-tool-features to use
A pagespeed audit
will be about
- optimal (mobile) UX for >75% of visitors
- real UX of your very own audience
- Beyond CWV, including third parties
- and improve bounce and conversion too
- understanding how browsers actually work
Pagespeed audit setups
- Valutas
sorry, no valutas found
- Prices are excluding VAT, which only applies to Dutch companies.
Frequently asked questions
Getting started
What do you need to get started?
There will be no doubt that I will find bottlenecks. Even a bol.com, coolblue and wehkamp are leaving money on the table. However, I would like to hear from you or your stakeholders where your bottlenecks are. If your team already started addressing pagespeed, send me an export of your backlog or roadmap as well.
How long does implementation take?
It depends on the platform, your team's knowledge of the platform as well as performance best practices. For example, excluding project management/communication overhead, within a clean Laravel shop, it could take one to two weeks.
When having a Magento 1, Lightspeed or Shopware 6 shop, this could become up to 3 weeks week. When using Shopify or Magento including its coding conventions, this could become 2 to 3 weeks. We all now that there is more overhead involved in e-commerce projects, but its hard to already make statements about that.
How long will it take before seeing results?
There are different factors in play. For example, do you have a seasonal webshop, does weather play a role? But also, what platform are you using and what is the sitespeed/performance knowledge of your team. To reduce lead time, let me train your developers as well.
When it comes to Core Web Vitals, it could take up to 28 days if optimizations correctly and depending on current scores.
Technical
Which aspects do you audit?
Historic data, frontend performance, covering TTFB, DNS lookups, cookies, redundant code, render blocking resources, resource hints, font loading strategy, (client side) caching strategy, image loading, used libraries, main thread blocking, code deduplication, third party widgets, loading on demand and maybe anti-patterns due to other optimizations. Obviously, Core Web Vitals -introduced in May 2020- is part of the audit as well.
Do you audit server side performance?
Partially. Making the right choice when it comes to server side performance (hosting + platform) is up to you. At the same time, when -for example- TTFB's are quite high, for example for API responses, it sometimes is possible to determine if their is a caching or SQL-query bottleneck.
However, most collaborations isn't covering a deep dive into server side performance. At the same time, while having build the fastest CMS out there, you can invite me to putting our heads together.
Do you audit native apps?
My work is only focussing on web performance and the work that is done between the code of your site or shop and the browser. Native Apple iOS or Android apps not running in a browser, isn't part of my expertise.
Can you talk us through your recommendations, afterwards?
Yes I can. That's even part of the 3-page template type audit. You can also schedule a single consult afterwards, when you've booked the 1-page template audit.
They have booked a pagespeed audit before:
Agencies speaking up:
In terms of SEO, I have a high standard. Working together with our devs, Erwin got us past Core Web Vitals and putting our SEO and UX high within our niche.
Erwin, the proud Groninger who conquered the Netherlands with all his (technical) page speed and UX optimizations. The collaboration is great!
Very satisfied with the update, Erwin knows what he is doing diving right into matters. This can also be seen in our new PageSpeed score of 90+ on mobile.
We enjoyed the in-house training. Erwin combined the session with a high level of knowledge and smart coding solutions! We started optimizing right after the session.
At first there was some doubt within the team about the necessity, but that doubt was completely gone after half an hour. I can only say that we have learned a lot from the training, lifting our team to a higher level.
