Recommended Agency

text controls: text only | A A A

Excited to put into practise some of the advice @ValuableContent gave at their workshop for @Bristol_Media yesterda… https://t.co/25ATyDykJC, posted 2 months ago

RSS feed icon What is RSS?

blog.

articles tagged with: ux


Displaying articles 1 - 10 of 17 in total

The 3 U's in designing for the user

The 3 U's in designing for the user

You could be forgiven for thinking usability, user experience (UX) and user centred deisgn (UCD) are all pretty much the same thing. Kind of like Ant & Dec: You're not sure which is which but understanding the difference matters very little. Well you'd be wrong! (In terms of design I mean - not whether or not Dec is the shortest).

Understanding the user is an absolute requisite for successful design. Here's a very simple breakdown of the 3 U's you may have heard being thrown around:

Usability is how easily a user can do what they set out to do.

User Experience is a combination of usability and and how much the user will enjoy themselves along the way.

User Centred Design is a case of keeping usability and user experience in mind from the very start of the design process.

There are various requirements of a succcessful product, these include:

Learnability - it should be intuitive so that there's essentially nothing to learn.

Efficiency - it should serve a purpose or assist in achieving a goal.

Memorability - it should encourage visitors to return. Popularity grows through word of mouth, people talk about what they remember.

Errors - it should have a low error rate. Evaluate and test the design, especially on the intended user.

So next time you tune in to 'I'm a celebrity get me out of here' you might not be able to tell which one stands on the left but at least you can confidently create a user focused product that will get people talking!

Jordana Jeffrey
Jordana

Created on Tuesday June 20 2017 10:05 AM


Tags: website ux ucd usability


Comments [0]








7 ways to maximise online donations

7 ways to maximise online donations

When I was asked to write an article about UX for the Fundraiser – the publication from Charity Choice providing practical advice and insight to the third sector – I wondered how on earth I was going to take such a huge topic turn it into something bite size.

UX and UI are expansive subjects, so rather than try to cram them into a side of A4, I decided instead to compile a list that would hopefully get the readers to try out some simple UX testing methods for themselves. 

For charities, encouraging visitors to donate and to keep donating is paramount, and ultimately good UX = more conversions which means more donations. Good UX really is as important for charities as it is for ecommerce.

The list is by no means exhaustive, but hopefully it will inspire some readers from the third sector to think more about UX, to utalise its potential and to try out some simple UX tests for themselves.

7 ways to maximise online donations

Jenny Corfield
Jenny

Created on Thursday September 22 2016 01:23 PM


Tags: website charity technology web-design userexperience ux usability


Comments [0]








Bad UX can cost you

Bad UX can cost you

Last year bad User Experience (UX) reportedly cost LInkedIn over £9 million.
Attention to detail is imperative when it comes to producing great design with a smooth UX. But with so much involved in the design process, there is a risk of things going unnoticed.

It doesn't take much to damage the users experience so here are some things worth checking before a design is signed off and deemed good to go...

 

Don't rely on colour to convery a purpose, heierarchy or content

We are big on accessibility here at focus so to us producing a website that is accessible is not considered a nice-to-have but a must-have. People with visual disabilities for example colour blindness, would not be able to use your site effectively if you were to rely on colour, they would therefore become an excluded demographic.

Test it: colorfilter.wickline.org will let you put a color filter on top of your webpage and test it for different kinds of color blindnesses.

 

Avoid / reduce repetitive actions where possible

An example of a repetitive action is filling in a form that asks for your address more than once, you may have seen this being tackled with a tickbox you can select to say your billing adddress is the same as your shipping address. If you're not careful, users will grow tired and search for an alternative option (like a competitor!) where they can achieve their goals better and faster.

Test it: Make sure there is a way of facilitating repetitive actions such as an option to use previously entered information.

 

Accessing help does not get in the way of progress

Users ask for help when they're stuck so of course It is important for help to be an extension of what they are already doing, they should be able to easily return to that once they have received the help they need.

Test it: Put yourself in the place of the user, consider where they will ask for help, and see whether their progress are interrupted.

 

Consistent navigation

Users have to be able to find their way around and achieve their goals no matter what page they find themselves on.

Test it: Make sure that navigation is reachable on every page and that your pathways are as intuitive as possible.

 

Foreground and background are sufficiently contrasted

This is especially important for people with visual disabilities. It also improves a user’s understanding. Clear distinction aids with navigation, draws more attention to buttons and increases usability.

Test it: You could capture the screen, apply a gaussian blur to a Radius of around 3px to 5px then see if you can easily tell what’s in the foreground and what’s in the background. Then alter accordingly.

 

Don't use much more than two distinct font families

Although this isn’t a strict rule it is best for accessibility. For usability and visual purposes, sticking to two simplifies your typographic hierarchy, which improves comprehension.

Test it: Simply check that your design isn’t mixing more than two type families. You should also make sure that the ones you choose are properly matched, you can find out more on this.

 

Text fonts are no smaller than 12 pixels

Again, it’s not a fixed rule but generally speaking readability is severely reduced for sizes below 12 pixels. Ideally a minimum of 14px is said to be better for accessibility.

Test it: Pretty obvious I suppose, check all of your content to ensure all fonts used are at least 12px.

 

Reserve uppercase words for labels, headers, or acronyms

Limiting the use of uppercase words is less visually heavy and easier for the user to digest. It should be used specifically for emphasis or very restricted cases such as acronyms.

Test it: A thorough content check to make sure that uppercase words are kept to a minimum and only used where necessary.

 

You're stil wondering what LinkedIn did so wrong aren't you? A settlement in California resulted in LinkedIn dishing out over £9 million to compensate users who were manipulated by the site’s deceptive UX into handing over their address books, which LinkedIn then used to spam their contacts with connection requests.

See, bad UX can cost you!

Jordana Jeffrey
Jordana

Created on Monday May 09 2016 02:14 PM


Tags: website ux accessibility


Comments [0]








Designing for Accessibility

Designing for Accessibility

Guesswork can only get you so far before it becomes a problem. My 'genius' theory of 'If in doubt choose B' served me well in my multiple choice French exam. It proved less useful in my oral exam when I told my teacher I keep a large duck in my kitchen every other day.
Yet it's come to light that many people with disabilities are navigating websites with the help of good guesswork, such as assuming the 'Contact' button will be the last link in the navigation bar.

A website should be intuitive to anybody who chooses to use it. Nobody should have to guess their way around and risk missing much of it's content. Accessibility enables people with disabilities to perceive, understand, navigate, interact with, and contribute to the web.

Alastair Campbell oversees both usability and development aspects at Nomense, a company that believes, just as we at focus do, that everybody has the right to access inclusive design, regardless of ability. He spoke with us about the importance of considering accessibility right from the start of the design process. We want to share a few of those things with you.

Skip links
The main content is often not the first thing on a web page. Keyboard and screen reader users tend to have to navigate a long list of links, sub-lists, corporate icons and more before ever arriving at the main content. So these users will thank you for enabling them to bypass or 'skip' over repetitive web page content. You can press the tab key on the Nomensa site for an example of a skip link http://www.nomensa.com/

Keyboard test
You should be able to achieve everything with keyboard controls alone.

• tab key to progress through links and controls
• shift-tab to reverse
• enter to follow links
• space to select form controls (e.g. tick boxes)
• cntl-f / cmd-f to find a link or text

Have a go on the BBC website for a good example http://www.bbc.co.uk/ and the Zoopla one where you'll get lost the moment you reach the first drop down menu http://www.zoopla.co.uk/

Zoom view
On many sites, the closer you zoom in, the more of the site's content is lost off-screen. Not with the Microsoft website: https://www.microsoft.com/en-gb/ this responsive site behaves as if you are viewing it on a smaller device each time you zoom, so eventually you are looking at a mobile view with all content still easily accessible.

User input
Make sure the results of user input happens close to where they perform the action. To experience the difficulties that incur if you don't, zoom in on this website https://www.overclockers.co.uk/index.php and add something to the basket. When you do, you're left wondering as nothing appears to change, unless of course you navigate all the way to the top right of the screen and view your basket. Do the same on amazon and an 'Added to Basket' notice immediately appears within view. Yes, that ab-cruncher I'll never use is mine all mine!

Alistair, photographed above, says there are 4 questions to ask yourself:

• Can you use it with a keyboard?
• Can you see it when zoomed?
• Does it provide appropriate information to
screen readers?
• Is it easy to understand?

Yes, it's a lot to take in and on the surface it may seem that this will limit your creativity. If anything, these guidelines will push these limits as you discover visually pleasing designs that improve the online experience for a wider set of users. And that's a fact. Even in French.

Jordana Jeffrey
Jordana

Created on Friday October 16 2015 11:42 AM


Tags: website technology web-development accessibility ux


Comments [0]








Web Testing on real phones & tablets

Web Testing on real phones & tablets

There are so many ways a website can be rendered on screen. Not only is there a huge variety of phone shapes and sizes but all of these can have multiple browsers (e.g. Chrome, Firefox, Safari, Opera and Internet Explorer). Then there's the fact that they can display in landscape or portrait mode. Users aren’t using a mouse but are instead using their fingers (some with 'digits' a little less delicate than others!).

It’s difficult for us developers and designers at web design agencies to predict just how our latest website might look online. There are of course websites that are meant to emulate how it will look but they're not always accurate.

This is where Open Device Lab steps in to make life that little bit easier. We headed over to their offices at Aardman to test one of the responsive website designs we're currently working on. We were able to test it on multiple popular devices from the iPad to a Blackberry. In doing this we could avoid the on-line emulators, we didn't have to pester friends with a different phone to ours to "borrow it for a second".
At ODL we could use a pretty handy piece of kit called 'Ghostlab'. Ghostlab synchronises browser testing. It scrolls, clicks, reloads and form inputs across all connected clients. So what you're testing is not the simple page load, but the full user experience. We also had the option to abandon that and fiddle with each device individually which is good for spotting usability issues that could possibly go unnoticed otherwise.

ODL Bristol are sponsored by the digital marketing agency 'Noisy Little Monkey', these guys made us feel super welcome and we were comfortable knowing we had coffee and support at hand (if required). More importantly, we left feeling we had done a thorough job of testing for our client.

So what did this cost us?... absolutely nothing. We're not sure if that's ever due to change but at the moment so long as you book ahead, you're welcome to pay them a visit. A the moment this gem feels like our little secret but you know what we're like at Focus, we promise to keep you guys updated with all things digital and this is definitely worth 'whispering' about.

Jordana Jeffrey
Jordana

Created on Monday December 01 2014 04:42 PM


Tags: website technology web-development mobile-internet web-design ux responsive


Comments [0]








Come and join team Focus

We're looking to increase the technical team at Focus with the addition of an experienced front-end web developer, who will work on projects and campaigns big and small across a range of sectors for the likes of Bristol City Council, The Multiple Sclerosis Society of Ireland, Scottish and Southern Energy and the Department of Health.

As well as technical excellence we're looking for bags of enthusiasm and a genuine passion for digital and for creating usable and innovative web sites and applications. The right person will have real input into the technology we use and the solutions that we create.

Candidates should have a good few years commercial experience in building accessible and responsive web sites, with an impressive portfolio of work. This is a technical position rather than design-based, so skills and experience should include:

- solid HTML5 / CSS3.
- Bootstrap and full knowledge of building responsive web sites using semantic HTML and CSS.
- Javascript including JQuery.
- experience of integration with back-end code – ideally any MVC database backed framework (we use Ruby on Rails).
- full understanding of cross-browser and cross-device testing and fixes.
- excellent communication skills: you’ll be meeting clients and talking them through projects.

Nice to haves:
- SASS and SCSS.
- UX / wireframing experience and the ability to create a clean, functional interface.
- SVN / Git.
- knowledge of W3C-WAI Accessibility guidelines.

Salary will be between £24k and £30k dependent on experience and skills.
Other benefits include great location in modern office facilities, subsidised restaurant, flexible working including work from home, minimum 23 days holiday and Christmas shutdown.

Applications should be sent by email to include your background and lots of information about yourself! Any work you can point to as your own would be appreciated as well.

Strictly no agencies please - we operate a 'name and shame' policy on those agencies that can't take 'no' as an answer :-)

Closing date for applications: 26th Sept 2014.

 

Simon Newing
Simon

Created on Tuesday September 09 2014 01:13 PM


Tags: web-development ux rubyonrails


Comments [0]








10 Web design trends to watch for in 2014

10 Web design trends to watch for in 2014

Trawl the web for long enough and you'll begin to notice patterns occurring, it becomes clear what is growing popular in the world of web design. Here are 10 design trends that I spotted and have a sneaky feeling we'll be seeing much more of in the coming year…


1. Flat design - OK, so this has been popular for much of 2013 but it's still going strong! Flat design removes all unnecessary elements so the content is the main focus - providing the best user experience. Initially, flat design developed as a solution to simplify Web layouts so that they were optimised across different devices but it's not just popular for practical reasons anymore. I can't get enough of this simple, clean style.

2. Grid-Style Layouts - Page elements are scattered to look like a grid. One familiar example of this would be the Facebook timeline. The grid-style provides a solid visual and structural balance. This sophisticated layout structure gives more flexibility and improves the visual experience of visitors as they can follow the consistency of the page much more easily.

3. Endless scrolling - The good thing is, browsing on our mobiles has gotten us used to it. Scrolling through a website is faster and easier than having to click through links upon links to get where we need to be. It's not content-cluttered either as new design techniques means all information is organised and formatted in such a way that it’s easy to digest. The layout often changes as you scroll, creating sections resulting in the user forgetting they're looking at one long page.

4. Simple Colour Schemes - I have a feeling there will be a lot more websites using only one or two colours. A new trend seems to be to use one bright and clean background colour, such as red, orange or teal, and to include images or black or white text over it. This creates a seriously minimalist and user-friendly effect.

5. Video - Instead of the usual written piece about what the company do, businesses are beginning to opt for short videos. This is most likely due to the fact that videos are easy to produce and share on your site as well as on social media. They also appeal to the short attention span many of us have adopted these days, we want everything now! Videos are an effective way of communicating with an audience and having an impact.

6. Fun with fonts - Designers are once again enjoying 'playing' with typography. Fonts seem to be getting bigger (and in my humble opinion, better!) and siting amongst a variety of others. Also, responsive typography should become a bigger part of responsive web design.

7. Mobile-First Design - Here, a higher priority is placed on the mobile experience which then becomes the foundation of the entire layout. The idea is to first mock-up how the website should look as a responsive layout on smaller screens. To make this work 'fancy' design considered unnecessary excess is removed and we are left with the bare essentials.

8. Mega-Navigation Menus - These menus that expand to hold large blocks of content and links, and can often contain product images seem to be particularly popular with e-commerce or news websites. If done well, this type of navigation can be extremely effective, they allow the user fast access to information located deep within the site.

9. Expanding search bars - Building semi-hidden or expanding search bars into your layout is definitely growing in popularity. When the user clicks a magnifying glass icon or clicks into the bar itself, the search bar expands wider allowing for more text input. This can be seen in a lot of responsive layouts.

10. Parallax Scrolling - That nifty technique that lets background images move slower than foreground images to make visuals appear more dynamic certainly makes for an interesting browsing experience. Handle with care though as too much of it can have quite the opposite effect!


As a designer here at Focus I am super excited about applying some of these trends to our work. Throughout the year I'll be looking out for emerging trends so that I can see you back here in 2015 with a whole new list! 

Jordana Jeffrey
Jordana

Created on Thursday January 16 2014 11:04 AM


Tags: website mobile-internet web-design internet userexperience ux web 2014


Comments [0]








Accessibility and the Olympics

Accessibility and the Olympics

World Usability Day 2013 at the M Shed this year had a host of great talks from usability professionals and enthusiasts from around the world. One talk really caught my attention and that was "BBC Olympics: An Accessibility Study" by Alistair Duggin the lead front-end developer at Money Advice Service. The talk looked back on the BBC Olympics website and the huge task taken on by the BBC to cover the Olympics in the digital age They wanted to make 24 HD live streams, over 2500 hours worth of video coverage as well as huge amounts of stats and data available world wide to a massive audience across mobile, tablet, PC and connected TV.

By the end of the project there had been 37 million UK browses, 66% of the adult population had visited the website as well as having 57 million global browses with 111 million video requests across all available platforms. These numbers were not the only difficulties of the project, the team at the BBC had an immovable deadline of a huge profile event and were working with teams of mixed knowledge in terms of accessibility. On top of this for added pressure the Australian olympics had been sued for being inaccessible.

So the team had one page for each of the 10,000 athletes, 205 countries, 36 sports, 304 medal winning events and 30 venues that they had to make usable and accessible for people with a range of visual, auditory, motor and cognitive abilities. This is where I was really surprised by the talk, I was expecting a full range of teams running huge usability studies and endless testing to make sure everything was perfect deploying more resources than is possible in a normal sized project. In reality the methodology and practices followed by Alistair and his team were reusable on any scale and in fact should be used on all web projects. It is not spending a lot of time changing designs and code to make it accessible, if you have accessibility in the back of your head when creating websites then you should only have to do it one time.

They had a library of common html widgets and reusable components that could be dropped into any page promoting the reusability and consistency of their code. Then for content, html, css and javascript they had a few simple rules to help create usable websites. For content having alt text for images, captions for tables and full text for abbreviations as well as having content in a logical order. Using appropriate html elements, not duplicating links as well as coding forms and tables to the correct standards helped create markup that was accessible for users using screen readers or navigating with a keyboard. For css having a non javascript layout, setting style on focus as well as hover, not using !important and checking for colour contrast were all very important. Feature detection in javascript as well as making sure the javascript generated valid html and there were no keyboard traps that stopped a user being able to navigate past certain points with a keyboard were all employed throughout the pages.

These are all the kind of coding practices that we can all follow on our websites but not necessarily something we check as often as how a page looks in IE7 or displays on a mobile device. I learned a lot from Alistair's talk, especially coming from the view point of a front end developer it showed me how important accessibility is for users, we should not be thinking about making it better for a minority of users but instead creating universal accessibility. He also talked about having a website that is one hundred percent accessible as not being realistic and that we need to prioritise in real world projects but that accessibility does not have to compromise design or ingenuity in websites.

Steve Fenn
Steve

Created on Monday December 09 2013 10:00 AM


Tags: accessibility conference userexperience ux usability


Comments [0]








User Experience Lecture

User Experience Lecture

Recently myself and another previous student of UWE returned to the User Experience module of the new Digital Media degree to talk in one of the first lectures of the year. We were asked by Praminda and Paul, lecturers at UWE we were previously students for, to do an introduction to User Experience and to try and talk about what we had learned in our first years as graduates. My partner in crime was Richard Foggin who is working at True Digital, we sat down before hand to try and work out what we would have wanted to learn about User Experience in our introductory lectures and what insights we could give as students who had been there before.

It was a hard decision to either talk about primarily what they would need as students of that module to pass, or what they would need as young professionals going out into digital and web work. User experience is such a vital part of our industry that it is almost certainly going to be part of their job in some way no matter what specialisation the students decide to go into. Rich and I decided that we would give an introduction to ourselves, the subject and what it meant to us but that we would need to get practical in order to give the students a real taste for UX work.

We decided to run the students through a practical that Rich and I had taken part in during a talk at UX Bristol by John Waterworth. We had the students design mini user interviews picking subjects they had an interest in and then took it in turns to be the interviewer and facilitator / note-taker. This was to give the students a feeling for all of the skills required to gain insights and collect requirements from user interviews. I think at the end of this process we had probably learned more than the students, I had not fully understood how hard it would be to run a workshop, keep everyone on track and making sure they got the most out of their time there.

We finished off our talk a bit exhausted with our collection of cheat-sheet / hacks for student life, little techniques and lessons we wanted to pass back as previous students to try and make it easier being a student! It was definitely a real experience going back to UWE, brushing up on our public speaking skills and really surprising just how much information you have that you want to share, it isn't until you start planning your time you realise the extent of the user experience subject. I would definitely recommend to any other professionals to go back to their universities and offer their services, it is a lot of fun and could be a good excuse to meet up with old university friends to work on something together.

Steve Fenn
Steve

Created on Friday October 25 2013 01:19 PM


Tags: userexperience ux usability youngpeople


Comments [0]








Web Analytics 101 - Bounce Rate

Web Analytics 101 - Bounce Rate

At Focus we are believers in keeping things simple - so over the course of a few blog articles I'm going to try and apply that approach to an area of digital marketing that can by it's nature get a bit complex - that being web site analytics.

The information you can gain from software such as Google Analytics (other analytics platforms are available!) can overwhelm - so we're going to pick a few more of the important KPIs and have a bit more of a delve and look at them - including their meaning and usefulness. (For the purposes of these articles I'm going to be referring to Google Analytics - or GA - as it's the most widely used analytics software and we happen to use it at Focus).

We start off with Bounce Rate - generally defined as the percentage of visitors who came to a page on your web site, viewed a single page, and then left - either to go to another site or by closing the browser. Bounce Rate (BR) is an important KPI that people get very excited about - especially when it's high, as this indicates lots of people are hitting your site and leaving straight away.

But is that a bad thing? It might not be - we'll explain more later.

Firstly, back to Google Analytics - which provides an overall bounce rate as part of it's 'Content' overview. But remember this will be for the whole web site, and for that reason, the overall BR isn't the most useful of stats. Instead it's best to focus on bounce rates for individual sections and pages - which is available in the list of pages seen at:
Content -> Site Content -> Pages.

To improve the accuracy of this list we also need to remove statistical anomolies that can skew the numbers (general good practice if you remember back to GCSE Maths). To do this, apply an Advanced Filter in Google Analytics to exclude these outliers - we tend to only include pages where the bounce rate is more than 10% and less than 95%.

Graphic showing Advanced Filters in Google Analytics

(See above 'advanced' surrounded in red - clicking this will allow you to apply a filter, of the type shown in green.)

Google Analytics also allows you to view bounce rates for different visitor types - by adding a Secondary Dimension. For example: if we add a Secondary Dimension of 'Visitor Type' we obtain seperate bounce rates for New and Returning visitors - this can give an insight into how engaging your web site is to different audiences.

There are other Secondary Dimensions - such as Keyword, Campaign and Landing Page - that are derived from your Google AdWord marketing activities. When applied correctly we now obtain bounce rates for individual pay per click (PPC) campaigns running from your AdWords account - this data is gold dust when looking at how successful paid-for campaigns have been (and where changes needs to be made).

So once you've got your bounce rate, how do you know if it's any good? When should the alarm bells start ringing? Whilst there are some general rules (see later), you need to bear in mind that bounce rates will vary between sites and use cases. At Focus we've built quite a few online directories for local authorities - and organisations listed in these directories tend to have high search engine rankings for specific key terms (such as their names). In this case, a user might want some contact information for an organisation - and having done a keyword search in an engine such as Google, they see the details they need in our Directory and leave the site having the information they require. In this instance - a high bounce rate, but the site has fulfilled the needs of the user.

eCommerce sites are a different story - generally we want users to convert, that is, land on a product page, move deeper into the site, use the basket and checkout. So high bounce rates on eCommerce sites are of poor value to the business and these pages need to be reviewed as priority.

Remember what was said before - look at the bounce rates of individual sections of your site rather than the site as a whole. If you are a charity, an overall bounce rate of 65% for the whole site will probably cause panic. What's more important though is to look at bounce rates for sections such as the donation facility - if 65% of users are leaving that section after one page, there's clearly some usability issues that need looking at. Taking each section at a time - with the most important sections addressed first - will help provide structure and reassurance, rather than trying to tackle the whole picture head-on.

Back to those rules then, and these are to be taken as general guides only:

  • bounce rates of 60% or over: take a snapshot, review your content as soon as you can and start planning some changes.
  • bounce rates of 25% to 60%: are generally the average, these should make up the majority of your report.
  • bounce rates below 25%: great, but don't ignore them. Make sure these pages are working really hard as clearly they are engaging the user, so ensure you include promotional news, or offers, or target them to really drive that 'call to action' and web site conversion.

Where you feel that your bounce rate is a bit scary, you'll want to consider making some changes:

  • review your content, is it out of date or innaccurate, does it engage the user? See our article on writing good content for the web, which is aimed at charities but has guidelines for all.
  • look at web site usability, is it obvious enough to the user where to go next? Does the site layout and navigation inhibit users from getting further into your site, and completing the desired 'call to action'? This is particularly crucial for landing pages used as part of PPC campaigns - literally money can be being poured away through poor design.
  • check how quickly your pages load, nothing whacks up the bounce rate like a slow loading web site.

It's also worth noting that Google Analytics allows you to check the bounce rate from mobile devices. If you've got a high bounce rate from iPhones, Androids etc the key reason could be users are hitting your 'non mobile' web site. With more and more people using their phones and tablets to view the web, having a site that's 'mobile-usable' is more important than ever.

So for starters, that's a whole lot of bouncing. We hope you've found the information above interesting and useful (well, about as interesting as stats can be....)

If you've got any questions then do get in touch, and we'll be publishing more web analytics blogs in the near future, so keep an eye out for more hints, tips and advice.

Simon Newing
Simon

Created on Thursday June 27 2013 08:25 AM


Tags: google ux usability analytics101


Comments [0]