WordPress
Sokkelund
Menus, booking and gift cards in one place
A WordPress website for the restaurant with booking, menus and gift cards gathered in one place.
Visit sokkelund.dkIf you need WordPress help right now, you are in the right place. I have debugged WordPress sites since 2010, and most urgent problems, from white screens to hacked installations, are ones I have solved many times before. Write or call, and the same day you will know when I can look at it.

star reviews
Read every reviewThe more precisely the issue is described, the easier it is to investigate. Send the relevant information first. We agree access to administration, hosting or code afterwards through an appropriate channel.
First I find out what happened, and only then do I fix it. A surprising share of the help people have received elsewhere consists of switching things off until the error disappears. Then it comes back three weeks later.
I ask for hosting and WordPress access, take a backup before touching anything, and note everything I change. Afterwards you get a short message on what was wrong, what I did, and how to avoid it going forward.
It is more urgent than people think. Not because of the site but because of the domain's reputation: Google flags quickly, and the flag takes longer to shed than it took to earn.
I clean the files, check the database for injected scripts, rotate all keys and passwords and read access logs to find the way in. If it was an outdated plugin, I will say so, even if it is one somebody paid for.
WordPress help is the debugging and repair of a live site: white screens, hacked installations, slow pages, forms that do not send, and updates gone wrong. It differs from ordinary web development in that the problem is already there and usually urgent.
Most people looking for WordPress help do not have a regular developer attached. The site was built by an agency or a freelancer a few years ago, it has looked after itself, and now a problem has appeared that nobody in the company can solve.
Good debugging requires having seen the error before. WordPress errors follow patterns: the same handful of plugin conflicts, hosting changes and security holes recur across thousands of sites. After 16 years in the trade I recognise most problems by their symptoms, which makes the fix faster and cheaper.
My approach is fixed: backup first, then diagnosis, then the fix, and finally a short written summary. You do not need a subscription or a punch card. Once the error is fixed, we are done, unless you want more yourself.
If the site says "There has been a critical error on this website", or the screen is simply white, the cause is almost always a PHP error in a plugin or the theme. The most important thing in the first minutes is not to make it worse. Do not reinstall WordPress, and do not delete plugins blindly. Take a backup of files and database through your hosting instead, so there is a way back whatever happens next.
Next, check the inbox of the email address set as the administration email in WordPress. On a critical error, WordPress sends an email with a link to recovery mode, where you can log in even though the site is down and see which plugin or theme triggered the error. From there you can deactivate it. If the email does not arrive, the plugin can be switched off by renaming its folder under wp-content/plugins via FTP or the hosting file manager.
If it is not clear what triggered the error, think about what changed most recently: an automatic update, a new plugin or a new PHP version at the hosting provider. You get the actual error message by setting WP_DEBUG and WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false in wp-config.php. The errors are then written to the file wp-content/debug.log without being shown to visitors. Switch it off again and delete the file afterwards, because by default it can be read from outside.
Most slow WordPress sites suffer from one or more of the same five things, and they can be found without guesswork. Start by measuring the front page and a typical subpage in PageSpeed Insights, which shows both data from real visitors and a lab test. Also look at the Core Web Vitals report in Search Console, which sorts pages into good, needs improvement and poor, separately for mobile and desktop.
The first three causes sit in the site itself. A heavy page builder such as Elementor or Divi that loads a lot of JavaScript and CSS on every page. Too many plugins, especially ones that load their code on every page, including where they are not used. And images uploaded at full resolution straight from the camera or phone and never compressed. Those are the ones I find most often when I am asked to look at a slow site.
The last two are about the server. Cheap shared hosting with an outdated PHP version and a server shared with hundreds of other sites gives a long response time before the page even starts loading. And without caching, WordPress has to build every page from scratch on every single visit. If it is the admin rather than the site itself that is slow, the culprit is often a bloated options table in the database or a plugin waiting for a reply from an external service.
Once the cause is found, the order is nearly always the same. Images and caching first, because it is quick and gives the most for the money. Then a review of plugins, where the unused ones go. The big decisions about changing hosting or rebuilding pages without a page builder come last, because they cost the most and should only be made if the rest is not enough.
A new web host is often the right next step when the current hosting is slow, support does not answer, or the PHP version is so old that plugins stop working. The move itself is not hard, but it has a few pitfalls that can cost both email and Google rankings if they are overlooked. That is why it pays to do it in the right order.
First a complete backup of files and database. Then a copy goes to the new host, and the site is tested there before the domain is pointed over, so you can click around and check that forms, login and any webshop work. The PHP version should be the same or newer. If the site changes address at the same time, the addresses in the database must be replaced with a tool that handles WordPress' serialised data, or settings and widgets break.
The pitfall most often overlooked is email. If your mailboxes sit with the same host, they do not follow on their own when the domain moves, and if DNS is pointed over without accounting for them, email stops working. The MX records and mailboxes therefore need to be in place before the domain moves. Finally, the SSL certificate must work on the new server, and the old host should only be cancelled once everything has run stably for a while. I am happy to help with moves like these.
Debugging requires access, not physical presence. That is why I help WordPress clients across the whole country, from Copenhagen and Aarhus to Odense, Aalborg and smaller towns, without anyone waiting for a consultant to drive out.
I am based in Glostrup in the Copenhagen area, but an outage in Aalborg is handled exactly like an outage in Østerbro: you send access, I take a backup and get started, and you can follow along by email or phone.
For urgent problems a freelancer is often faster than an agency, because there is no case flow. You write to the person who will solve the problem, not to a support queue where the ticket first has to be assigned. Call +45 22 51 31 79 if the site is down now.
There is a fixed order. First a copy of everything is taken as it stands, even infected. You need to be able to examine it afterwards and roll back if the cleanup removes too much.
Then the files are cleaned. The WordPress core and plugins are replaced with clean copies from source rather than patched, because otherwise you cannot be certain. The theme and uploads are reviewed by hand, because that is where it usually hides.
Then the database: injected scripts in posts, unknown administrator accounts and scheduled tasks that recreate the whole thing once you think you are done. That last one is what people most often miss, and the reason a site gets hacked again three days later.
Finally all keys, salts and passwords are rotated, and the access logs are reviewed to find the way in, so the hole gets closed rather than just cleaned around.
Concrete deliverables, not a report of recommendations someone else has to find time for.
An error that only gets hidden comes back, and it is more expensive the second time. So I look for the cause.
Files and database are secured before I touch anything, so there is always a way back.
What was wrong, what I changed, and what prevents a repeat. A couple of paragraphs, not a report.
Most urgent jobs are one-offs, and I do not sell a service contract on the back of an error.
WordPress
Menus, booking and gift cards in one place
A WordPress website for the restaurant with booking, menus and gift cards gathered in one place.
Visit sokkelund.dkWordPress
Design focused on conversion
A new WordPress website for private and business customers with design, tracking and a simpler booking flow.
Visit 3x34.dkWordPress
WordPress built to keep up
A custom theme with flexible templates for Dinero's product pages, pricing and guides.
Read about my work for DineroVisit dinero.dkWordPress
From class schedule to booking
A WordPress website for the studios with class schedules, pricing and a clear route to booking.
Visit energii.dkWordPress
10 museums gathered in one website
A WordPress website bringing together museums, experiences and visitor information from across Ringkøbing Fjord.
Visit ringkobingfjordmuseer.dkFour steps. You know what happens when, and you can stop after any of them.
A 20-30 minute call where you describe what needs to be built or repaired. I ask about platform, access and deadline, and tell you honestly if the job sits outside what I am good at.
Small jobs get a price after a short clarification. If a larger existing project needs a technical review first, we agree the price and scope of that review before I open the code.
You get a firm agreement on what is included, what is not, and when it will be ready. If the scope changes along the way, we deal with it openly instead of letting it drift.
I work in your own repository and your own hosting and deliver in pieces you can see and approve. When we are done, you have the code, the access and documentation that makes you independent of me.
It depends on the type of error, whether the site is down or just misbehaving, and how messy the installation is under the hood. Describe the problem, ideally with a screenshot, and I will state a concrete price before starting. You will hear from me the same day.
WordPress offers free courses and guides at learn.wordpress.org, and they cover most of the basics. What they cannot do is show you your own site, where the theme and plugins often make things work differently from the guide. If you are stuck on something specific, it is usually faster to have it shown once in your own installation.
If the site is down, I prioritise it, and you get a same-day answer on whether I can take the job today or tomorrow. I do not promise what I cannot keep.
Yes, that is by far the most common case. By now I have seen most themes and plugins on the Danish market, so finding my way around an unfamiliar site rarely takes long.
No. I work on the hosting you have today, and since I do not sell hosting myself, I have no interest in moving you. If the debugging shows the hosting is part of the problem, for example an outdated PHP version or an overloaded server, I say so and explain why. Then it is your decision whether to move to a new host.
Yes. I do not build new sites in page builders, but I am glad to help with ones already running on Elementor, Divi or WPBakery. The typical problems are layouts that break after an update, conflicts with other plugins and pages that have become slow. I fix that in the page builder you have, and I do not propose a rebuild unless you ask or it is the only lasting fix.
No. Most urgent jobs are one-offs, and that is how it should be. If it turns out something more fundamental is wrong I will say so, but the decision about further work is yours.
Administrator access to WordPress and access to your hosting or FTP. If you do not have the credentials, I will help figure out where to get them.
Yes, all debugging happens remotely, so I regularly help companies in Aarhus, Odense, Aalborg and the rest of the country. Distance makes no difference to how fast the error gets fixed.
Backup first, then surfacing error messages and logs without exposing them to visitors, followed by systematically narrowing down the cause. The fix comes last, and you get a short summary of it all.
Yes. After each job you get a short written summary of what was wrong and how to avoid it, and I am happy to show you how to take the first steps yourselves next time, such as a backup and troubleshooting with the debug log. If you want more than that, I also run WordPress courses in your own installation, so the editors learn the site they actually work in.
Send your website URL, what you need solved and your desired deadline. I will assess the next step and describe what the quote includes. Larger investigations are agreed separately before work begins.
Describe your taskYour next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.