Restaurants
Thin margins and high rent mean the menu page has to convert on a phone, not sit inside a PDF nobody can read.
Restaurants hosting
San Francisco is an expensive place to run a small business, and that changes how you look at every recurring charge. Web hosting in San Francisco, CA, is a small line on that statement, and the site behind it either brings in work you can point at or gets cut in a quiet quarter.
We are not in San Francisco. AldoMedia is in Buffalo, New York, and there is no California office, no local number and nobody who can come by. Setup, migration and support all happen remotely, which for hosting is simply how it works.
In a technology, finance and tourism economy with costs this high, the thing that kills a small business website is rarely a crash. It is a review meeting. Somebody prints the card statement, works down the recurring charges, and asks what each one is for. The website has to have an answer.
Most do not. The site was built years ago, nobody has edited it since, and the only evidence it does anything is that it exists. Meanwhile the bill arrives every month and grows quietly at renewal. That is a charge waiting to be cancelled, and cancelling it is usually the wrong call for the wrong reason.
Before you spend anything on redesign, spend an hour making the website measurable. If you cannot tell whether it produced a single enquiry last quarter, you are guessing, and guessing is how good sites get cut and bad ones get kept.
A website that cannot show its work will lose the argument to a rent increase every single time. Fix the measuring before you touch the design.
Send us the address. We will tell you what the page weighs, how fast it loads on a phone, whether the contact form still delivers, and what you are paying for that you do not need.
When a site is not pulling its weight, the pitch you get is usually a rebuild. Sometimes that is right. More often the site is fine and three specific things are broken, and fixing them costs a fraction of starting over.
The pattern repeats across trades. The page is slow because nobody resized the photographs. The contact form stopped delivering eight months ago and no one tested it. The hours or the service list are out of date, so the site quietly contradicts what you tell people on the phone. None of that needs a new website.
Check those three before you agree to anything larger. If the form has been dead since spring, no redesign was ever going to help, and no redesign will keep it alive next spring either. Someone has to test it on a schedule.
Send yourself a test enquiry through your own contact form today. A surprising number of these fail, and the failure is silent by design.
Most businesses that come to us are not launching something new. They are leaving: a host that got slow, a developer who stopped replying, a plan that tripled at renewal without anyone noticing until the card was charged.
The order of operations is what keeps it uneventful. Copy the site to the new server first. Test it there while the old one is still live. Only then point the domain across. Done that way the site never goes dark, because the old server keeps answering until each visitor's connection catches up.
The part that goes wrong is email, and it goes wrong the same way every time. Somebody rebuilds the DNS from scratch on the new host and leaves out the mail records, and a day of enquiries disappears before anyone realises. Write the existing records down before touching anything. The full order is on the website migration page, and moving mailboxes has its own steps on the email migration page.
Server location matters far less than people expect. The distance between a visitor in California and a server elsewhere in the country is measured in milliseconds, and it is swamped by the weight of the page itself. A homepage carrying eight megabytes of unresized photographs will feel slow from across the street.
So the useful work is almost always the same: resize images before uploading, turn caching on so the server hands out a finished page instead of assembling one on every visit, and remove third-party widgets that load before your own content does. That is where the seconds are.
Backups belong in the same conversation. They are the cheapest insurance on the list and the one people skip, until the day a plugin update takes the site down. Keep them off the server they are protecting, and check once that restoring actually works. There is more on website backups.
Copy, test, switch the domain, keep the mail records intact. You keep working while it happens, and afterwards there is somebody to call.
In a high cost city the instinct is to buy the serious-sounding option, on the theory that cheap things fail. For hosting that instinct costs money and buys very little.
Spending more is worth it when the site takes bookings or payments, when it carries a large gallery or a document library, or when a day of downtime costs you billable work. Visitor numbers on their own almost never justify it.
If you want the whole picture, including the parts that are not hosting, the running costs page lays it out. Current pricing for plans is on the hosting pages rather than here, because it changes.
This is the fair objection and it deserves a straight answer rather than a slogan. Hosting is not a local service. Your website does not live in San Francisco today and it will not afterwards. It lives in a data centre somewhere, and which state that is in makes no practical difference to somebody loading the page in California.
What you are actually choosing is who answers when something is wrong. That varies enormously between companies and has nothing at all to do with distance. We are in Buffalo, we work Eastern time, and we have been building and looking after websites since 1999. We are an independent authorised reseller, not the operator of the underlying platform, and we will tell you when the plan you are already on is the right one.
The time difference is worth naming. We are three hours ahead of you, so we are available early in your day and gone earlier in your evening. For most hosting questions that is fine. If you need somebody physically in the room within the hour, hosting support is not that, and no host is.
If you inherited a site and nobody knows where anything is registered, start with taking over a website. That situation is more common than people admit and it is fixable.
The genuinely local part of your online presence is your Google Business Profile, and it is free. Get that right before you spend anything else.
Three kinds of business whose websites carry real weight in an expensive city, each with a page of its own.
Thin margins and high rent mean the menu page has to convert on a phone, not sit inside a PDF nobody can read.
Restaurants hostingOne matter can be worth more than a decade of hosting, so a dead contact form is the most expensive thing on the site.
Law firms hostingThe portfolio has to look expensive and load fast at the same time, and that tension is entirely about image weight.
Photographers hostingEvery trade we cover is on hosting by industry, and every city on our locations page.
Skyline photograph: Basil D Soufi, CC BY-SA 4.0, via Wikimedia Commons. Cropped.
Test it the way a customer does. Turn wifi off on your own phone, use mobile data, and load the site cold from a search result rather than a bookmark. Time how long it takes before you can read something and tap something. Office wifi and a cached browser hide almost every real problem, so a page that feels instant at your desk can crawl on a phone half a mile away.
Because hosting is not work anyone does in your room. Everything we touch, the server, the records, the backups, the certificates, is reached remotely, and a local firm reaches it the same way from their own desk. Our office is in Buffalo, New York, and support is remote. Hire us for the answers you get, not the postcode. If a local firm serves you better, use them.
Whoever is listed as registrant on the domain record controls it, and in this city that is often somebody who left for another company long ago. Look your domain up in a public whois lookup and read the registrant and admin contact. If it is not you or your business, ask for the registrar login and get the contact changed to an address you will still hold in five years. Do that before you rebuild anything.
The visible part is short. We build the site on the new server, test it privately, then change where the domain points, and that change spreads over roughly a day. What breaks is almost always the parts nobody listed: the contact form handler, an old redirect, a certificate, or mail records rebuilt from scratch instead of copied. We write those down first and check each one after the switch.
Tell us what your site runs on and what you are paying for it. We will tell you what to fix, what to cancel, and whether the plan you are on is already the right one.
Get Your Web Hosting Plan Get help choosing
Or call 716-771-2536. We are in Buffalo, New York, so we answer Eastern time.