We Practice What We Do

Anyone can say their website is fast. Any web designer can tell you they build for performance, that speed is a priority, that your site will load quickly on any device.

Words are easy. So instead of asking you to take ours for it, we'd rather show you.

Test it yourself, right now

Go to pagespeed.web.dev, Google's free, public tool for measuring website performance. Paste in our URL: sitematestudio.com. Run the test.

You'll see our scores on both mobile and desktop. We consistently score above 90 on both, which means the technical foundation behind sitematestudio.com is in good shape by Google's own measurement.

That's not a screenshot we took on a good day. That's a live test you're running yourself, right now, on our actual website. No filters, no editing, no cherry-picking.

If we can't build a fast website for ourselves, why would you trust us to build one for you?

What those scores actually mean

Google PageSpeed Insights measures something called Core Web Vitals, a set of real-world performance metrics that reflect how a website actually feels to a visitor:

LCP (Largest Contentful Paint): how quickly the main content of your page loads and appears on screen. Google considers anything under 2.5 seconds good.

INP (Interaction to Next Paint): how quickly your site responds when someone taps a button or interacts with the page. A slow response here makes a site feel laggy and unresponsive.

CLS (Cumulative Layout Shift): whether elements on the page jump around while loading. Most people have had this happen on some website at some point, you go to tap something and it moves just as you tap it. Annoying for users, penalised by Google.

A score above 90 means all three of these are in the green. It means the site loads fast, responds instantly, and doesn't shift around on the screen.

Worth knowing: Google doesn't run this test under ideal conditions. PageSpeed Insights throttles the connection and simulates a mid-range mobile device, not the fastest phone on the fastest network. That's deliberate. If a site still loads fast under those constraints, real visitors on better devices and faster connections will see it load even quicker. A high score on a throttled test is a stronger signal than a high score would be on a perfect one.

That said, a good Core Web Vitals score doesn't automatically mean a website is "better" than another, or that it'll outrank competitors on its own. It means the technical foundation is sound. Google's ranking algorithm weighs hundreds of other signals too, content quality, backlinks, relevance, user experience signals beyond speed. Core Web Vitals is one input, not the whole scoreboard. Get it wrong and it can hold a good site back. Get it right and it stops being a liability, but it won't carry a weak site to the top on its own.

Why we're telling you this

We build websites for local businesses. Our whole pitch is that a fast, well-built website brings in more customers: better rankings, lower bounce rates, more calls and enquiries.

It would be pretty hollow to say all of that and then have our own website score a 65.

Every choice we made when building sitematestudio.com (the framework, the hosting, the way images are handled, the way fonts load, the structure of the code) was made with performance as a priority. Not as an afterthought once everything else was done. From the start.

That's exactly how we approach every client website we build. The same standards, the same attention to the details that most people never see but that Google and your visitors absolutely feel.

Now test your current website

If you already have a website, go back to pagespeed.web.dev and run the same test on your own URL.

If your score is below 90, your site is slower than it should be. If it's below 70, it's likely costing you customers and rankings right now, silently, every day. Read more on why load speed matters.

The good news is that performance issues are fixable. A rebuild with modern technology, proper hosting, and optimised images can take a site from the 50s to the 90s. The difference in how it feels, and how it performs in search results, is significant.

What we use to achieve this

Our own site, and every client site we build, uses the same core stack:

Next.js: a modern React framework that combines server-side rendering and static generation, so most pages are pre-built or rendered close to the visitor rather than assembled slowly in the browser.

Vercel: a global hosting network with edge locations spread across multiple regions worldwide, rather than a single server in one country. It routes each visitor to a nearby point on that network instead of sending every request across the world to one origin server, cutting down unnecessary distance and unnecessary latency.

Payload CMS: a headless CMS that keeps content separate from code. Pages load fast because the CMS isn't doing heavy lifting at the point of delivery, it's already done.

Optimised images: every image is compressed, converted to modern formats, and sized correctly for the screen it's being served to. A mobile visitor doesn't download a 4000px wide image designed for a desktop monitor.

None of this is magic. It's just good, modern web development done properly. The point of all of it isn't the tech itself, it's what it does for the visitor: pages that show up fast, feel responsive, and don't make someone give up and leave before they've even read what you do. A visitor who isn't waiting is a visitor who's more likely to call.

Don't take our word for it

Test our site. Test yours. Compare the numbers.

If yours isn't where it should be and you want to talk about what a properly built website could look like for your business, that's exactly what the free mockup is for.