The creative Jamstack agency for teams that want to get the most out of their website

Your new UX & Jamstack agency - Skyward Digital

Look: Here’s where we share ideas, stories and opinions from the design, UX and development world we live in.

Here’s where we share ideas, stories and opinions from the design, UX and development world we live in.

Our thoughts: Skyward's Blog

We’ve been around the block and seen some things. Want to get the updates first?

Whether your goal is to sell more products, drive more conversions, or reach more customers, you won’t get there if you don’t have excellent user experience.

The Google Lighthouse audit offers recommendations for improving site performance. Optimize your Lighthouse performance score to improve UX and SEO.

Optimise your Lighthouse score and watch your site performance soar

If pages are slow loading, inaccessible, or poorly optimised for organic search, chances are UX is also performing poorly. 

In other words — people will be running away from your website, rather than flocking towards it.

You can get a good idea of your current user experience (UX) by analysing your website performance.

Google describes Lighthouse as an open-source, automated tool that improves the quality of web pages. You can run a Lighthouse report for pages that are public or that require authentication. Once done, you’ll get audits for performance, accessibility, progressive web apps, SEO, and more.

Side note: To access Google Lighthouse, open the web page you want to analyse in Chrome, then navigate to Developer tools, select the Lighthouse tab, and click “generate report”.

After running your site through Lighthouse, you’ll be presented with a performance snapshot showcasing a series of scores rated from 0 - 100. The metrics measured are:

If simple dashboard metrics weren’t helpful enough, Google takes this up a notch by colour-coding the scores to determine performance:

A score between 90 - 100 is considered to be a “good” score. You need to be striving towards a score of 90 if you want to make sure your site offers a good user experience. 

However, the higher the Lighthouse score is, the harder it is to achieve.  Achieving a “perfect” score of 100 will be challenging, but ensuring you’ve got at least “good” scores for every category will guarantee you’re getting the best results. 

And you’ll be able to feel the difference.

Before you roll your eyes and start thinking “Great, one more thing to add to my to-do list”, let me explain why optimising your Lighthouse score matters.

When ranking your website for lighthouse, on their search engine, or anywhere; google only cares about one thing. User Experience.

They want to ensure that the right users are finding and staying on your website long enough to get the information they need.

So by improving your lighthouse score, you’re not just making google happier, you’re working towards creating a better experience for your users overall.

And that, in turn, leads to numerous other benefits.

Google created Lighthouse. They also run the biggest search engine in the world. So if Lighthouse says your website needs improvement, Google’s Search Engine is going to be using that data too.

Your organic website rankings can change depending on how well your site performs on Lighthouse. If we spin this around, we can deduce that increasing your Lighthouse score will help you meet best practises for search engine optimisation (SEO).

If you aren’t familiar with Core Web Vitals, these are metrics that measure the loading, layout stability, and interaction readiness of your web pages. How you score on these metrics is an indication of how user-friendly your site may (or may not) be.

Lighthouse lets you easily measure site performance across these metrics so you see which areas of user experience need your attention most. You can then optimise site performance, accessibility and usability to enhance SEO.

Lighthouse is far from the only scoring factor, but if you have poor performance, seo and accessibility you’re going to struggle to rank regardless of how good the rest of your content is.

What if I told you that rather than guessing where, and what, the roadblocks on your site might be, you could see clear warning signs that told you exactly what those roadblocks were? You’d want to know, right?

That’s exactly what the Google Lighthouse report does. It doesn’t just tell you if your site is performing poorly. It tells you why. You can then use that information to implement solutions.

Google Lighthouse report identifies common problems and then provides recommendations on how to fix them. It’s a powerful tool for effectively monitoring website quality without having to do too much manual heavy lifting.

I know I’ve already mentioned the importance of Google Lighthouse for UX. But, it really is important.

The accessibility test within Lighthouse contains 35 audits. That’s 35 chances to improve your site’s accessibility and usability — two factors that are key for enhancing user experience for everyone.

Making changes to close the ring in the other reports will all help benefit UX too. From a performance point of view, a higher score will mean having faster loading pages and lower user frustration.

Google’s primary goal is to get search users exactly what they need, so Lighthouse gives you the ability to fix poor UX across all areas of your website to ensure it’s in its best shape.

Load speed can make or break your website. 

Slow websites are frustrating. But reducing loading time isn’t just about overcoming frustrations. It’s also about improving performance and skyrocketing success. 

Every second counts when it comes to web page loading times, and the first 5 seconds can have the biggest impact. Conversion rates drop by an average of 4.42% with every additional second of loading time between those first 0 - 5 seconds.

Along with increasing conversations and reducing user frustrations, page speed is another important factor for SEO and getting your website to that number one spot in Google search results.

Google Lighthouse’s performance audit measures your site speed against seven different metrics so you can speed up web page loading times to help your users and organic rankings.

By now, you’ve probably realised that optimising your Lighthouse score is all about user experience and keeping your website visitors happy. 

By that notion, if you focus on increasing your Lighthouse score and making the recommendations presented, you’ll bring your website performance into closer alignment with user expectations. In turn, your users will have a more positive experience on your site and will be more likely to convert.

Both “big” and “small” brands can benefit from running a Lighthouse audit and improving their score.

If you’re the owner of a small business or start-up, the Lighthouse audit offers clarity over your website performance. You can then use the report to identify clear recommendations and opportunities for improvement. 

You might be able to implement some of these recommendations yourself. For example, the performance report might recommend that you “properly size images”. This is a change that you could execute, by taking images and resizing them in photoshop, to reduce loading time and improve website performance.

But some recommendations are best left to an experienced web developer, and you’ll find that as your site grows you’ll want to start automating some of those more manual tasks (which your developer can also help you with).

The Lighthouse audit gives you a good baseline understanding of your current performance before you engage the help of web developers. They can then guide you through which issues to tackle first to improve website optimisation.

For “big” brands and large-scale organisations, the Lighthouse report is a powerful accessory developers can use alongside current web optimisation activities. 

As your business grows, so does your website. Overtime, websites can become bloated or sluggish. Using data from lighthouse allows you to make better decisions, and maybe your time is better spent fixing your website performance than creating a new landing page this month.

Running a Lighthouse report is a great way to take things back to basics and remember the fundamentals of good UX when amending your website. Armed with a Lighthouse report, you can take large, complex websites and make them fast-loading and smooth-running.

Knowing how Lighthouse calculates your score is beneficial for knowing how to improve it. 

Lighthouse scores web pages across a series of five categories on a scale of 0-100. Within the Performance category, your final score is weighted based on metrics essential for organic search performance.

The metrics measured within the Performance audit on Lighthouse 8 are:

First Contentful Paint - 10% weighted average

Largest Contentful Paint - 25% weighted average

Time to Interactive - 10% weighted average

Total Blocking Time - 30% weighted average

Cumulative Layout Shift - 15% weighted average

The metric results are then converted to a score on a scale of 0-100 based on benchmark data held by Google. 

Optimise your Lighthouse score by paying attention to the Google best practices for UX and accessibility, and following the recommendation provided in Lighthouse reports.

The Lighthouse scoring calculator is the best place to start when looking to improve your Lighthouse performance score.

This calculator helps you understand the thresholds you should be aiming for if you are looking to achieve a particular score. 

Adjust the metric score for each datapoint to see what value you would need to achieve to get your desired performance score. Compare these numbers to your current performance to find opportunities for improvements.

After all that talk about why Lighthouse is important, how do you actually go about fixing poor lighthouse scores?

Working with an experienced web developer

If you want to get the best possible Lighthouse score for your site, you need to work with an experienced and knowledgeable web developer. 

Sure, you can DIY some elements, but working with an experienced developer will strengthen the long-term performance of your site. It isn’t about finding quick fixes. It’s about developing a website that performs as well as it possibly can.

Working with a developer means you’ll have access to someone who understands the finer details of performance, best practices for UX, and how to implement long-term solutions.

Sometimes, the only option is to do it yourself. If, for instance, you are facing strict budget limitations and aren’t in a position to invest in your web development support. 

We only advise going down the DIY route if you are already familiar with performing complex web development tasks. 

While we don’t advise doing it yourself, it is possible to improve your performance score with these tips.

Above anything else, you first want to focus on fixing the more severe issues. 

These are the issues that are having the biggest negative impact on your score. Focusing on these changes will, therefore, significantly increase your performance. The Google Lighthouse report uses a traffic light system to highlight the severity of issues. 

Any issues with a red triangle next to them are the most severe issues. These are followed by an orange square to indicate issues of a lower severity. Use these colour-coded symbols to identify the most severe issues on your web page and create a priority order based on severity.

One simple Lighthouse score improvement that anyone can implement is optimising on-site images. This also tends to be one of the most overlooked performance issues.

Large images that have not been adapted to suit the web page presentation can negatively affect website loading time. Resizing images can improve load time and save data.

Before uploading images, compress them and use a smaller file format such as JPEG.

There are ways to automate this process. Most headless frameworks (Like NextJS or Gatsby) offer an Image tool that resizes your images for you. You could also use a service like imgix or cloudinary, that resize images and give you a ton of other controls too.

While compressing images, I recommend also improving any image file names and alt text for accessibility purposes. It’s a good habit to get into, and one that will help accessibility and search engine optimisation.

Having a large number of packages or plugins on your site can reduce loading time, especially if they’re barely used.

Only install packages that are absolutely necessary. Make a habit of checking through them often and removing any that are redundant or no longer needed.

Lighthouse scores are determined on a page-by-page basis. When improving your Lighthouse score, focus on the most important pages first.

To find high impact pages, analyse your website traffic to see which pages people typically visit. For a SaaS company, the sign-up page will likely be one of their high impact pages. Whereas, a B2B service provider might consider their services pages to be the high impact pages.

Improving your Lighthouse performance score is about improving UX. So it makes sense to prioritise the web pages where users spend the most of their time. Fixing the performance of these pages will positively impact the user journey, meaning you can start creating a positive user experience then focus on fixing the lower impact pages next.

Not everything on your site is necessary. Along with removing redundant packages, remove any other unnecessary elements on your site. This can include unused CSS and JavaScript, or even parts of your webpage if they’re not providing any value.

These elements will be dragging down your site loading time, causing them to load far slower than necessary. You can fix this by removing unnecessary elements, or if you can’t remove them instead splitting them up and loading them only when necessary.

If you, like us, love headless frameworks then they often have a lot of these performance boosting methods built in, though newer frameworks are moving away from hydrating your entire page.

Finally, prioritise accessibility at every stage of your website build, development and maintenance.

Accessibility metrics make sure your web pages are usable for people who might interact with your content differently. Accessibility should be a facet of user experience rather than a box-ticking exercise. 

Look at the Accessibility report within your Lighthouse audit and work through the recommendations in order of severity. While some recommendations will require the support of an experienced web developer, you might be able to action some of the other recommendations yourself.

Improving your accessibility score makes it easier for people to access your on-site content and perform the actions they intended. 

Work with us and take your site performance Skyward

In a nutshell, the Google Lighthouse audit is a powerful tool for assessing your website’s UX performance.

Optimise your Lighthouse performance score to tap into improved UX, faster site speeds and more conversions. Plus, you’ll naturally improve organic performance.

Here at Skyward, we are an experienced web development and design team with a specific UX focus. Our eye for UX paired with our deep understanding of web development means who can map out a clear path to resolving site issues and skyrocketing your performance.

So, get in touch and let’s talk about optimising your website performance.

User experience (UX) isn’t a single item on a checklist. Rather, it’s a structure that runs through every aspect of your business. 

User experience impacts everyone using your site. Learn these UX best practices to improve usability for customers, developers and marketers.

UX, DX, CX - How experience is a core component for your website's long-term success

Think of UX as an umbrella (ideally one of those ridiculously large golf umbrellas) that covers multiple aspects of your website build. UX covers everything from your site’s visual design to the information architecture, usability, content strategy, user research, business analysis, and frontend development — you get the idea, it covers pretty much everything.

UX focuses on how people interact with and experience a product, system, or service. When I say people, I mean anyone — not just your customers. 

Under the UX umbrella we have developer experience (DX), customer experience (CX) and employee experience (EX). Today, we’re going to look at optimising the on-site experience for each of those users and, in turn, strengthening your long-term success.

Let’s explore how UX impacts the success of your site, and how you can use it to improve the online experience for your:

UX affects everyone that engages with your site. It impacts the experience of your customers. If the UX of your site is poorly optimised, you are basically handing customers over to your competitors.

Not only that, but UX also impacts how your team works. Poor UX could mean reduced productivity and efficiency and increased frustration for your team. All of which are ingredients of poor outcomes. If you want the best out of your team, you need to create the best environment for your team — and yep, you guessed it, that includes optimising UX.

UX is about providing solutions to enhance the experience for everyone. Users, Customers, Developers - everyone.

Good UX is invisible. The user experience should be so seamless that people hardly even notice it. You don’t see good UX, you feel it on a subconscious level. Trust will naturally strengthen, sales will increase, and they’ll feel good when they think of your company.

Bad UX is remembered — and not in a good way. Poor UX increases churn, costs and frustration while reducing sign-ups and sales.

So, what kind of experience do you want to create for your users? An invisible yet positive experience? Or a memorable yet bad experience?

My guess is that you want to create the former — and the only way to do that is to invest in your UX.

Let’s take a moment to reflect on who your users actually are when it comes to your website.

The obvious answer is your customers. Your customers will interact with your site throughout their entire journey, from finding your landing pages to making a purchase to using your software on a regular basis. Any UX frameworks focused on improving how customers engage with your site are known as customer experience (CX).

Next up, we’ve got the developers. These people put their life and soul into building your site, keeping it well-maintained and running optimally. So, you want to return the favour by ensuring they have the best possible experience when doing so. Any strategies focused on improving the site implementation are known as developer experience (DX).

You’ve also got your content marketers and editors. These users edit the website content, run campaigns and finetune the messaging of your site. So, it makes sense that you want to make sure their job is as easy to do as possible.

You’ve also got your customer service teams and sales reps. Supporting people through online chat software and making orders on behalf of customers — User experience design that aims to improve usability for your team is called employee experience (EX).

And those are just a few of the users impacted by your site’s UX. More people use your site than you think.

Improving experience for different types of users

Every user wants something different. So, how do you improve the experience for all these different people?

Think of UX as professional people-pleasing (in a good way). Dig deep into your user’s needs, motivations, and challenges to create powerful, invisible experiences that they will love. 

Now, I’m not saying to make changes just because you think someone might like it. Be strategic in your method. Make changes based on evidence. Run tests, experiment with changes (and measure the results) and talk to your users to see what does and doesn’t work.

And follow the best practices below to understand how to improve the experience for your users.

The success of your website relies on customer experience.

Think about it, if you visit a website and get annoyed by the experience, you probably won’t rush to go back again. That experience might even tarnish your thoughts of the brand and drive you away for good — straight into the arms of the brand’s competitors.

Customers want to easily find what they’re looking for. They don’t want to search high and low for a simple answer to their questions. 

You can help customers find what they’re looking for by:

Developing intuitive navigation that makes it easy for them to move from page to page

Adding a search function so they can look for more niche results that they can’t find by briefly browsing the navigation menu

Clearly displaying pricing on any transactional pages including eCommerce product pages, SaaS subscription pages, and service pages

Making sure the Contact or Support features are easy to find (and use) — we live in the 21st century where people don’t want their only contact option to be calling a random 0800 number between the hours of 9 am - 5 pm


These are just a few general examples, but each brand will have their own unique users who each have their own goals to account for.

Your online customers want to know they can trust your site too. Build a site with visual designs and elements that strengthen trust. Satisfying visuals, strong brand identity, and consistent design all help build trust and customer loyalty.

And they definitely don’t want to be confused. Optimise the customer flow of your site. Clear confusion by improving your user interface. Do buttons go where they say they will? Can people easily navigate between pages? Can users get support quickly? Question everything then simplify it. 

Finally, your customers don’t want to be unnecessarily hassled. Garish pop-ups and overbearing ads will drive down UX and ramp up customer frustration. Just look to the eBay community forum where there are over 1,000 posts by members expressing their pop-up anger.

Limit the number of pop-ups and “noisy” elements on your site. Add a delay or, even better, a context trigger before pop-ups appear (like a discount code when an item is added to a basket). Minimise disruption. Keep forms simple and easy to understand.

Note that we’re not saying to remove all promotions, subscriptions or anything that could potentially cause poor UX. You just need to be smart about how you implement them.

Simply, put yourself in your customers’ shoes and see things from their perspective.

Developers probably spent the most time on your website than any other type of user. They’re in the nitty-gritty details, getting up close and personal with your site’s functionality as they make changes.

We’ll give an honourable mention to Managers here too. Managers want your site to work seamlessly. They want to reduce friction and increase efficiency. Make your developers happy and you will no doubt be making the senior management teams happy too.

Here are some ways you can make your developers happy by prioritising UX — or should we say, DX…

Firstly, make sure it is easy for developers to make changes and add new features. They don’t want to go round in circles or have to complete (or repeat) hundreds of steps to perform one simple action.

Your developers and managers likely don’t want to deal with the tediousness of performing repetitive tasks. Build a site that is easy to update with reusable components so you can spend more time on the work that actually matters.

Better yet, build a website that other team members can use! UX doesn’t just apply to the frontend of your site. Make sure the backend is just as user-friendly so non-developer team members can edit the areas they need to. Whether it’s content managers uploading new blogs or eCommerce administrators editing product information, prioritise simplicity when building your entire site.

And don’t forget to add automated testing as part of your site build. Automated testing cuts down on the number of manual tests — fewer manual tests equals less risk of human error. These automated tests will also make sure that developers won’t accidentally break one element of the site when updating another. As your site gets bigger, you’ll thank yourself.

Editors and marketers will likely be the next most involved in updating and maintaining your site. The ones who deal with the words and write content that keeps visitors clicking through every single page (all the way to conversion).

They need to be able to easily update and add new content, without having to email the developer when a simple content change is needed. Trust me.

Plus, they want to know they can change the page structure without breaking the design. Coding likely isn’t their first language, so make sure the user interface is easy for non-developers and designers to make changes quickly. Your marketing team wants to be able to effortlessly craft new pages and on-site content, (and your developers don’t want to be expensive content editors either).

Build UX into every stage of your site and you will make it easy for editors and marketers to create new on-site campaigns and content oozing with great user experience.

Believe it or not, getting UX right isn’t rocket science, though the bigger you go the more complicated it can get (like most things).

Great user experience boils down to just a few simple ground rules. Remember these general rules for UX and you will be way on to building websites that all your users love:

Allow all users to have the autonomy to do what they want or need

Don’t rush things. Be slow and deliberate when working on UX design. Think about the needs, motivations and challenges of every user. Then build the solutions to those questions into your site UX. 

And remember to build a collaborative site. You want everyone to be able to use your site. Create efficient systems between your teams so they can all do their part without coming up against any roadblocks.

Focus on creating better experiences for all users and you will create an impactful experience overall. Make small changes now and your users will begin applauding you in no time.

And if you’re looking for more help on how to improve UX across your entire team, get in touch and see how we can generate amazing results for your business.

A short guide and a small addition that massively improves how your users will interact with your content

I’ve been spending a lot of time recently recreating the Skyward website and one of the coolest but also most underrated features that I’ve created is the table of contents on blog posts.

The best part? Once built, it requires no effort to maintain - it automatically finds the headings in your blog, turns them into links and creates the Table of Contents for you.

When you’re reading blog posts (like this one) how do you go about reading it? Most people will typically scan the page to get an understanding of if the page they’ve landed on is what they’re looking for.

Then they’ll dive deeper into the content, read through it, jump back and forth (especially if it’s a tutorial)

And finally, if the article is good enough, they might share it.

By providing links to headings throughout the blog post, a table of contents seamlessly covers everything a user might need, without being intrusive and blocking their ability to read the article.

Why do we need to create contents automatically?

Going through and manually adding a table of contents is slow and prone to errors.

If you regularly add new content to existing blogs, it would be very easy to forget to manually update a table of contents.

Creating a table of contents also improves how easy it is to share links to specific parts of blog posts, helping more users and making your content more relevant.

Without a Table of Contents, you’re relying on your users doing all this on their own - so why not help them out?

In order to achieve the results we desire, we’ll need to do a few things.

Create a blog post with content 
undefined

Create a sidebar for our Table of Contents

Create our Table of Contents 
undefinedundefined

To get started, you’ll need to create your blog post with some content.

I’m using Prismic here. Prismic works based off of an internal architecture called Slices. These allow content to be automatically added to the page in the order determined by the CMS - which is great for updating content without having to make code changes.

Here’s a basic blog post in Prismic, this is the page we’re starting with

import { SliceZone } from "@prismicio/react";
import { createClient } from "../../prismic";
import { components } from "../../slices";

export default BlogPost = ({ data }) => (
  <Layout>
    <article>
      // Our blog content built up using one or more slices, though you could switch this for a single rich text field too
      <SliceZone slices={slices} components={components} />
    </article>
    <BlogSidebar slices={slices} /> //we'll get to this later
  </Layout>
)


// fetch data for our page
export const getStaticProps = async ({ params, previewData }) => {
  const client = createClient({ previewData });

  const post = await client.getByUID("blogPost", params.uid, {});

  return {
    props: post,
  };
};

// Statically generate our paths
export const getStaticPaths = async () => {
  const client = createClient();
  const documents = await client.getAllByType("blogPost");

  const paths = await documents.map((document) => ({
    params: { uid: document.uid },
  }));

  return { paths, fallback: false };
};

export default BlogPost;

We’ll also need a slice that can handle page content

import { PrismicRichText } from "@prismicio/react";

// This just outputs the rich text content of the prismic field
const Content = ({ content }) => (
  <PrismicRichText field={content} />
);

export default Content;

In order to be able to link to our headings, we need to create headings with IDs.

By default, Prismic simply outputs your headings, so to add IDs to them you’ll need to use the HTML serializer.

Side note: The HTML serializer is great for using custom <Link> or <Image> components in your content

Here, we just want to take our <h1> and replace it with <h1 id={someID}>

To add an ID to our heading components we need to first create the ID.

export const createID = (string) => (
  string
    .toLowerCase() //lowercase for consistency
    .replace(/[^\w\s]/gi, "") //remove special chars
    .replace(/\s+/g, "-"); //replace spaces with hyphens
)

Using the function above, we’ll turn a string like this!  Into an ID safe string like-this. Note that we’ll reuse this function later, so let’s save it in a global place.

Now we have the ID we can figure out how to add it to our content component.

In Prismic, we can specify exactly what we want to return from our Rich Text fields by passing a components function to our PrismicRichText component, like so

import { PrismicRichText } from "@prismicio/react";
import { createId } from "../utils/createId";

const Content = ({ content }) => (
  <PrismicRichText field={content} components={components} />
);

// we need to figure out what goes here so we can limit what's returned to only the links we need
const components = () => {} 

export default Content;

PrismicRichText uses our components function every time if finds a component. Behind the scenes it is effectively doing this.

// we don't need to add this code anywhere, it's just pseudo code
for (element in your_custom_rich_text_field) {
  return element
}

Where it loops through every element you’ve used in your Rich Text field, like p strong h1 h2 image etc and returning the relevant content in the appropriate format.

If you want to dig deeper into the HTML serializer you can read how to do that here - what we need to know for now is that we can override what we get returned.

So now we know how it works, we can create our serializer to return exactly what we need

// Add our custom HTML serializer for our page content
const components = (type, element, content) => {
  if(type === Element.heading1) {
    // we overwrite the default functionality, returning a h1 with an id
    return <h1 id={`#${createId(content)}`}>{content}</h1>
  }

  if(type === Element.heading2) {
    return <h2 id={`#${createId(content)}`}>{content}</h2>
  }

  if(type === Element.heading3) {
    return <h3 id={`#${createId(content)}`}>{content}</h3>
  }

  if(type === Element.heading4) {
    return <h4 id={`#${createId(content)}`}>{content}</h4>
  }

  //returning null at the end falls back to the default behaviour
  return null
}

With this in place you should now be able to inspect your blog headings and see that ids are present.

This also allows you to link to your headings! If you copy the generated id and add it to the end of your url, you should jump to that section of the page.

It’s not very useful without real links though, so let’s create those too!

This can be as simple or as complex as you’d like - I went for a simple sidebar that shows just the table of contents and a newsletter form (if there’s space).

I plan on making this sidebar sticky, so it follows us down the page. That limits how much vertical space we have to work with, so I can’t add in much more than this.

Our general sidebar layout is pretty straightforward

export const BlogSidebar = ({ slices }) => (
  <aside>
    <h2>Table of Contents</h2>
    // Our contents will go here
    // We still need to build this component
    <Contents slices={slices} />
  </aside>
)

The hard part is figuring out our contents…

We’ve had some thoughts

Optimise your Lighthouse score and watch your site performance soar

UX, DX, CX - How experience is a core component for your website's long-term success

How to create a Table of Contents Automatically using Prismic & NextJS

Refocus, refine, results: Why we’ve decided to refocus our approach

Yearly round-up - 2022

Strategically improve your website with UX design

Website rebuild checklist: Do these 12 things before you rebuild your website

How UX can add value to your business and your customers

What is the Jamstack?

When should you rebuild your website?

We’ve had some thoughts

Optimise your Lighthouse score and watch your site performance soar

UX, DX, CX - How experience is a core component for your website's long-term success

How to create a Table of Contents Automatically using Prismic & NextJS

Refocus, refine, results: Why we’ve decided to refocus our approach

Yearly round-up - 2022

Strategically improve your website with UX design

Website rebuild checklist: Do these 12 things before you rebuild your website

How UX can add value to your business and your customers

What is the Jamstack?

When should you rebuild your website?

Hear from us first