Start with the reason for change
A website may rely on external services for presentation, measurement and protection. Before replacing a tool, decide what you want to achieve: fewer third-party requests, managing data within your own infrastructure or a simpler visitor experience.
List the services actually loaded in the browser, including those added by extensions and a tag manager. For each, record its purpose, the data sent and who is responsible for configuration. An alternative is useful if it meets that need without creating a larger maintenance problem.
Locally hosted fonts
You can keep a downloadable font and serve it from your website's infrastructure within its licence terms. You change the file source, not necessarily your visual identity.
Keep only the weights and characters you need, configure caching and check accented characters. Compare loading before and after: local hosting alone does not guarantee a faster website.
Traffic analytics: what do you need to measure?
Before choosing a platform, define your questions: where do visitors come from, which pages help them and where do they stop before contacting you or buying? Not every website needs a complex tracking setup.
Matomo offers privacy settings that need to be configured for the project. Self-hosting does not automatically mean no personal data is involved: check anonymisation, identifiers and retention periods.
When comparing tools, separate the subscription from implementation, hosting and maintenance costs. Ask for a demonstration of the reports you need instead of choosing by feature count alone.
Spam protection continues on the server
For a form, you can evaluate an alternative such as Cloudflare Turnstile. The on-page widget is only the first part: the server must validate the token before sending email or performing the requested action.
Turnstile tokens are single-use and expire after five minutes. The interface should allow verification to restart without losing the message. Also test what happens when verification is unavailable.
Change one service, check the whole journey
Start with an integration in a test environment. Check the appearance, network requests, collected data and key functions. Document the configuration and keep a rollback path.
Choosing a provider does not replace assessing how you use data. At Verosea, our approach is practical: we choose tools based on business requirements and check their effects on the actual website.
Sources and documentation
Revised edition of the article originally published on Verosea in 2025.
