Your vision. Our Dezyn.
Vitals
Benchmark
Google considers
< 2.5s
The page feels ready. People stay.
2.5 to 4s
Usable, but the main content is still catching up.
> 4s
People leave. Rankings usually follow.
If the first screen takes too long, people go back. You lose the visit, and Google notices. A site that appears quickly feels better to use and is more likely to show up when someone searches for what you do.
LCP is Google's name for the moment the biggest thing on the screen actually appears: the hero, the headline, the block you meant them to see. We aim for under 2.5 seconds on an ordinary phone. If a preview build misses that, it does not ship until we bring it back.
On a marketing page that is usually the hero image, the main heading, or the poster for a video. On a product page it is often the showcase photo or the pricing block. Whatever it is, we treat it as the priority: the right size, the right format, fetched first, on every build.
How we implement LCP
The hero photo is sized for the screen it lands on, then compressed. We use WebP or AVIF so the file is smaller without looking worse, and we tell the browser that this is the image to fetch first.
Whatever you see first gets the first request: the headline, the hero, the main block. Scripts, tracking, and pictures further down the page wait. Nothing below the fold should hold up the first impression.
We ship only the JavaScript the page needs, split the rest by route, and keep the path to first paint short. If code is not helping the screen the visitor is on, it does not load yet.
Search
Search is part of the build, not a plugin we switch on the week before launch. Pages are written, titled, and linked so Google can read them from day one.
The work is practical: the words on the page, the address in the bar, the map of the site, and a report you can actually use.
Titles, headings, internal links, and markup a search engine can actually read. Each important page gets its own title and description, not the same company line copied everywhere.
Meta tags · Heading hierarchy
Speed
We do not sit the site on a page builder or a pile of extra plugins. Extra weight is extra wait. The pages are written to ship only what they need, so the first screen can open quickly, even on a phone using mobile data, not only on studio wifi.
A full-size camera file will stall a page. We shrink each photo to the size it actually shows, compress it, and load pictures below the fold after the first screen is already up. The visitor sees the offer first, not a spinning wait for a gallery they have not reached yet.
We keep the number of fonts small and load them so words appear at once, not as a blank gap that later jumps into place. Headings and body copy should be readable the moment the page lands. If type is late, the whole site feels late.
We cache what can be reused: the layout, the fonts, the files that do not change every hour. A second visit should feel instant, not like starting from scratch. The host is set up to serve those files fast, so the wait is not the road between the visitor and the site.
QA
We open the site on a phone, a tablet, and a large monitor. Most people will visit on a phone, so that is where we start. Buttons are large enough to tap. Type is readable without pinching. Nothing important is cut off or hidden behind a menu. If a layout only works on our laptop, it is not finished.
We walk the site the way a customer would: home, the offer, then the quote, contact, booking, or checkout. We fill the form ourselves and check that the message actually arrives. If someone skips a field or mistypes an email, they get a clear note, not a dead end. Success should feel obvious too.
Colour contrast is checked so type still reads in bright light. Every control has a label. You can move through the site with a keyboard if a mouse is awkward. Headings follow an order a screen reader can follow. If a visitor cannot complete the main action, we treat that as a bug and fix it before launch.
We check current Chrome, Safari, Firefox, and Edge so the site does not only work in one window. We also try the awkward cases: a missing page, a slow connection, a form that fails to send. The visitor should get a clear page, not a blank screen. What we find, we fix, then we check again.
Hardening
Locked down before launch: the connection, the forms, the keys, and the server. A quote form should not become a way in.
Every visit is forced onto a secure connection, so a login, a quote, or a card detail cannot be read on the way to the server. Certificates renew on their own, and old http links are sent to the secure address. The live URL is the one you own. Test links and leftover preview URLs are closed before launch, so nobody is poking at a half-finished copy that still talks to real data.
Measurement
Search
Google's search report is connected from the first day the site is live. You see the phrases people actually typed, how many of those became a visit, and whether each important page is listed. If a new service page is missing from Google, we catch it in days, not after a quiet quarter. The figures are people looking for your work, not a pile of searches that will never call.
Sample month
18 / 18
Pages listed
386
Visits from search
Weekly visits from search
Actions
We count the steps that lead to a job: a quote sent, a call from the number on the site, a booking that finished. You get those few numbers each week, not a long list of clicks with names nobody uses. If a new page brings more quotes, it shows on the same chart. If a form goes quiet, we start with that page.
Sample month
48
Quotes
4.2%
Visit to quote
48
Quotes
31
Calls
12
Bookings
Privacy
We do not add extra hidden trackers for ads or heatmaps unless you asked for them. The report uses one small tool that loads after the page is already on screen, so a visitor is not waiting on it. Where the law asks for a choice, the message is plain: keep the numbers, or turn them off. You still know how the site is used. Nobody is followed around the rest of the web for a chart you will never open.
This build
24 KB
Analytics file
0
Ad trackers
After launch
After handover you can run the site yourself. If you would rather we stay on, we offer maintenance as an extra. It is not bundled into the build. We quote the work, you decide, then we do it.
What we build
Interfaces with purpose. Layouts that are clean, intentional and on-brand.
Clean code. Smooth experiences. Built to perform on every device.
Fast is part of the design. Optimised for speed, Core Web Vitals and UX.
Built to be found. Structured, semantic and search engine ready.