Most slow sites that reach us have the same story: a 60-dollar template with twenty-three plugins on top. We code the theme for your site, write whatever plugins are needed and leave the site passing Core Web Vitals. If you already have WordPress, we migrate it preserving what you earned on Google.
Nobody buys "WordPress development". They buy it to fix one of these five things.
It is almost always three culprits together: a heavy theme loading libraries you do not use, 4 MB images uploaded straight off the camera, and a dozen plugins tripping over each other. It gets fixed, and the number shows in the same week.
No, as long as every old address points to the new one.
The way in is almost never the server: it is a plugin that has not been updated in two years. We clean up, close the entrance and put someone in charge of the updates, which is what was missing.
A calculator, an ERP integration, a form that checks stock. A plugin of our own is written and it stays yours, with no annual licences.
We look at which premium plugin can be replaced with code of our own.
Multilingual with its own menu, addresses and search per language.
It happens often. Control of the domain, the hosting and the panel is recovered, and from then on the credentials stay in your name.
LCP is how long the big thing on screen takes to appear. INP, how long it takes to respond when someone taps a button. CLS, how much the elements jump around while it loads. All three are fixed with work, not with a magic plugin.
The thresholds are the ones Google publishes. The times on the bars are an example of the kind of site that reaches us most: your real number depends on the theme, the plugins and the weight of your images, and we measure it before quoting.
You start with whatever gives the most result per hour of work. Often the first half of the list solves the problem and the second half is never needed.
A bought template brings features for a hundred different businesses and your site uses four. Everything else still loads, and when the author abandons the product you are left with a site nobody updates any more.
We design in Figma and code that design. There is no "the template will not do that", because there is no template.
Two rounds of adjustment before codingEvery editable block has its own field, not a free-form editor where one stray return breaks the home page. Your team edits without fear.
Custom fields per templateWhen what you need does not exist: an instalment calculator, a stock lookup against your ERP, a search by part number.
Our own code, no annual licenceEach language with its own menu, addresses and content, declared so Google knows which to show in each country.
Spanish, English and whichever you addYape, Plin, Culqi or Izipay, shipping zones by region and the receipt filed with SUNAT through Fastura.
See online shopWordPress's REST API towards your system, or the other way round. If your ERP has an API, the site can read prices and stock without anyone copying anything.
REST · webhooksWhether you come from Wix, from Joomla, from a hand-built site or from another WordPress. The important thing is not copying the content: it is that every old address still leads somewhere.
We export the full list of current addresses and cross-check which receive traffic from Google. That list is what governs everything: without it, a migration is a gamble.
Posts, pages, categories, files and mailboxes. If you are coming from a closed platform, we rescue whatever can be exported and tell you what cannot, before we start.
Every old address points to its new equivalent. Those with no equivalent go to the closest section, never to the home page and never to a 404.
After the switch we check Search Console every day: crawl errors, pages dropped from the index and broken links. The first fifteen days are when you see whether anything shifted.
A 301 tells Google the move is permanent and to carry over to the new address what the old one had earned. A 302 says "back soon" and carries nothing over. And sending everything to the home page is the fastest way to lose rankings that took years.
Four measures that close most of the doors. None of them is expensive; what is expensive is not having them the day the red warning appears on Google.
The reason almost nobody updates is fear, and it is a reasonable fear: a new version of a plugin can take a section apart. That is why updates are applied with a backup first and the site is checked afterwards, not the other way round.
The administrator account the intern used in 2021 is still active on half the sites we review. It gets pruned, anyone who only drafts is demoted, and two-factor is put on whoever remains.
Having the file is no use if nobody has ever restored it. In the monthly maintenance we restore a copy in a separate environment to confirm it opens, the database goes in complete and the images are there.
What we do not invent: the retention of the backups the shared server takes depends on the node. If you need a specific policy in writing, we set it out in the maintenance contract.
The site is checked every few minutes from outside. If it stops responding or the certificate is about to expire, the alert goes to the team and it is looked at without waiting for someone to call and say the site will not open.
A measured average across Búho's platform, not a brochure promise.
We do not publish the price because it depends on the size of the site and on whether it is a corporate site or a shop taking orders every day. What we do publish is exactly what is included.
With a backup first and a check of the site after applying. If something breaks, we roll back the same day.
Files and database, with a copy off the server. And a test restore to confirm it works.
If the site stops responding, the alert goes to the team. We do not wait for a customer to write to you before telling you.
They renew before expiry, without you having to remember. The notice arrives anyway, in case you want to keep track.
The form that stopped sending, the image that shifted on mobile, the broken link. Design changes or new features are quoted separately.
What was updated, what was backed up, how long it was online, which links broke and what we recommend for next month. One sheet, no padding.
We say it before signing, so nobody argues about it by email later.
All of that can be done: it is quoted as separate work and you approve it first.
It can stay as it is, we just need the credentials. That said, if the server is part of the problem — and on a slow site it often is — you are better off bringing it over: the migration is free and the site ends up on LiteSpeed, NVMe disk and self-renewing SSL.
When the site goes down on a Friday night, the classic problem is that the agency says it is the hosting and the hosting says it is the site. Here there is nobody to point at: the server, the email, the domain and the code are all ours, and you write to one WhatsApp.
Wix is not a bad tool: it is a tool with a ceiling. The table says where that ceiling is and when each route makes sense.
| WordPress with its own theme | Wix | Bespoke development | |
|---|---|---|---|
| Who it's for | A company that publishes often and wants control | A simple site you need this week | When the business logic is what matters |
| Where it lives | On your hosting, on your domain | On Wix's platform | Wherever you decide |
| Monthly platform fee | It has none: you pay for the hosting | Monthly subscription | It has none: you pay for the hosting |
| The code is yours | |||
| You can take it to another provider | Yes, in full | No: you export content, not the site | Yes, in full |
| Control of technical SEO | Total | Limited to whatever the panel exposes | Total |
| Features that do not exist yet | With a plugin of our own | Only if the platform allows it | No limit |
| Who updates and backs up | You or the monthly maintenance | The platform | You or the monthly maintenance |
| A shop with Yape and receipts filed with SUNAT | It depends on the available gateway | ||
| Multilingual with its own addresses | Basic | ||
| Typical delivery timescale | 15–25 days | 5–10 days | 45 days or more |
| What we deliver most | Useful to get started | Let's talk it through → |
The clock runs from when we have credentials, content and the approved design. That is how it is written in the proposal, with the start date conditional on it.
| Work | What is included | Total in business days |
|---|---|---|
| Speed optimisation | Audit, images, cache, plugins and database | 5 days |
| Migration to our hosting | Cloning, a test on a temporary domain and the DNS switch | 2 days |
| Migration from another platform | Content, images and a map of 301 redirects | 10 days |
| Bespoke theme 5 to 7 sections | Design in Figma, templates, editable fields and training | 20 days |
| WooCommerce on a theme of our own | Catalogue, Peruvian payment gateways, shipping and Fastura | 25 days |
| A bespoke plugin | By scope, with a specification signed beforehand | From 8 days |
| Second language | Menu, addresses and content per language | +5 days |
Fixing the speed of a ten-page site and rebuilding the theme of a site with a 400-post blog are nothing alike. Tell us in five fields and within 48 hours we will send you the scope, the timescale and what is out of scope. If your site is already online, we measure it before proposing anything.
In the meantime, these are the four WordPress commissions that reach us most. No invented figures.
Audit, plugin cleanup and server cache. It is the most frequent commission.
Content, images and 301 redirects so no rankings are lost.
A new theme respecting the addresses that already get traffic.
Updates, backups, monitoring and a report you can actually read.
If your site is already online, we measure it before quoting: speed, versions, plugins and SSL status. Within 48 hours the proposal arrives with the scope and the timescale, and with what we think is not worth touching.
Five fields and your site's address, if you already have one.
