Recherche avancée

Sur d’autres sites (5618)

• 11 of the Most Effective Conversion Rate Optimisation Best Practices

  14 février 2024, par Erin

  Driving more traffic to your website is hard work, but it’s still only half the battle. 

  You don’t just need to acquire new users ; you need to make sure as many convert as possible to make your digital marketing efforts worthwhile.

  That’s why improving your site’s conversion rate is so important. It will also help you get more value from your existing traffic source and keep you in line with your competitors. It’s also probably a lot easier than you think — especially if you adopt optimisation strategies that have been proven to be profitable time and time again. 

  In this article, we’ll show some of the most powerful, innovative and tried-and-tested conversion rate optimisation strategies you can implement immediately. 

  What is conversion rate optimisation ?

  First, let’s look at what conversion rate optimisation means. Conversion rate optimisation is the practice of improving elements of your website to increase the number of users who take a desired action and turn visitors into customers. 

  Common conversion goals include :

  • Making a purchase
  • Adding an item to a shopping cart
  • Signing up for a newsletter
  • Registering for a free trial
  • Downloading an ebook
  • Watching a video

  It doesn’t matter what your goal is. Using one of the following conversion rate optimisation best practices can send your conversions soaring. 

  11 conversion rate optimisation best practices 

  Are you ready to roll up your sleeves and get to work ? Then use one or more of the following best practices to improve your return on investment. 

  Set a clear goals and hypothesis

  When running an A/B or multivariate test, you need a clear idea of what you are testing and why. 

  A goal (a statement about what you want to achieve) and a hypothesis (a statement about what you expect to happen) clarify the problem you are trying to solve and give you a definitive way to judge the experiment’s results. 

  Confused ? Just use this template :

  We aim to [insert goal] by testing [insert test] on [insert page]. We expect that [insert test] will increase [insert metric] because [insert reason].

  Make sure your goals are directly related to the experiment. If you are testing your CTA button, the goal should be getting more users to click the button. It shouldn’t be a goal further down the conversion funnel, like making a purchase. 

  Start with A/B tests

  A/B testing is one of the easiest and most effective ways to run experiments to improve your current conversion rate. So, it’s no wonder that the A/B testing software market was expected to be worth $1.2 billion in 2023 and hit $3.6 billion by 2033. 

  Also known as split testing, A/B testing allows you to directly compare the conversion performance of two elements on your page, like the colour of your CTA button or your headline copy.

  

  You can go even further with multivariate testing, which lets you test two or more changes against a single control. 

  For example, the screenshot above shows the results of a multivariate test between a standard header, a wide header and a small header using Matomo’s A/B testing tool. As you can see, the wider header has a much higher conversion, and the increase was statistically significant. 

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Tweak your CTAs

  Calls to action (CTAs) are page elements that prompt users to respond immediately. They are usually buttons but can also be images or plain text links. 

  What your CTAs say, how they look, and where they are placed can greatly impact your site’s conversion rates. As such, this is one of the elements you’ll want to optimise first. 

  There are several tweaks you can test, including your CTA’s :

  • Colour 
  • Length 
  • Copy
  • Placement 

  You can even test the impact of removing CTA banners and using text-based CTAs on your conversion rates.

  You should test out personalising CTAs, too. Research shows that personalised CTAs perform 202% better than standard calls to action. 

  Revise your web copy

  You can use several strategies to improve your website’s copy and generate more conversions. 

  Optimising copy for search engines can increase traffic and generate more conversions, for example. But that shouldn’t make your copy any less impactful. Bear search engines in mind, by all means, but make sure you are speaking to the needs and desires of your potential customers. Your copy needs to convince users that your product can solve their problems. 

  Nowhere is this more important than your headlines. These will be the first thing users read, so make sure they sell your USP and highlight pain points.

  Don’t just guess at the kind of messaging that will move the needle, however. Constantly test new headlines and continue doing so even after you’ve started seeing success. The results may surprise you. TruckersReport, a site that helps people become truck drivers, boosted opt-ins by 21.7% by revising its landing page headline, among other changes. 

  Make sure there are no spelling mistakes in your copy, either. Misspelt words, poor grammar and bad formatting make your website look unprofessional and untrustworthy. Even if the rest of your copy is incredibly enticing, these rookie errors can be enough to turn customers off. 

  Simplify your site’s navigation

  A website’s navigation is an often overlooked factor in conversion rate optimisation, but simplifying it can make it much easier for users to take action. 

  If you’ve ever used a poorly designed e-commerce store, you know how confusing and overwhelming bad navigation can be. Research shows that a whopping 82% of stores don’t divide their navigation into manageable chunks. 

  The trick is to simplify your navigation as much as possible. As you can see in the screenshot below, our navigation only has five headers and a call to action. It’s easy to find exactly what you’re looking for, and you can’t miss the big green CTA button. 

  

  Alternatively, you can test what happens when you completely remove your navigation. Brands usually do this on landing pages where the only action they want the user to take is to make a purchase. 

  

  It’s exactly the strategy we’ve used on our free trial landing page. 

  Leverage heatmaps

  Analytics tools — and heatmaps in particular — can help you understand user behaviour and optimise accordingly. 

  Heatmaps are a visual representation of user interaction on your page. Red and yellow represent high levels of user interaction, and blue and green represent low levels of interaction.

  

  As you can see in the screenshot above, our CTA button has some of the highest levels of engagement on the page, telling us that it’s well-positioned. Given the focus on the site’s navigation, we can also assume we are correct to have a CTA button in there — something we can confirm using our web analytics to see how many users click on it.

  Reduce load time

  Speed matters when it comes to conversions. Fact. 

  Research shows a huge difference in conversion rates between quick and slow sites. For example, a site that loads in one second converts three times better than a site that loads in five seconds. 

  That’s why using a web analytics tool is vital to understand page load times and act accordingly if you think slow speeds are hampering your conversions.

  

  Identifying your slowest pages is easy with Matomo. Just sort your pages by the Avg. Use the page load time metric on the page performance report to identify the pages you want to drive conversions. 

  Next, take steps to improve your page’s load time by :

  • Compressing images
  • Compressing code files or using a more lightweight theme
  • Removing unnecessary plugins
  • Using a content delivery network
  • Improving your hosting

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Add more trust signals

  Trust is essential when you’re trying to convince customers to make a purchase. In fact, consumers rate trust as one of the top three buying factors, far above a brand’s reputation and whether they love the brand. 

  Adding trust signals to your landing pages, such as customer testimonials, customer reviews, case studies, and other forms of social proof, can transform your conversion rates. If consumers see real people and businesses buy from you, they’ll feel reassured to do the same.

  

  It’s a strategy we use ourselves. Just look at the screenshot from our homepage above. Immediately after our free trial CTA, we display the logos of well-known brands that use our product. 

  Security-focused trust signals are also powerful if you are an online store. Installing an SSL certificate, showing logos of trusted payment providers (like PayPal and Mastercard) can convince people they are spending money at a legitimate store.

  Improve your site’s mobile experience

  More and more people are accessing the internet via their smartphones. In 2022, for instance, there were five billion unique mobile Internet users, meaning more than 60% of the internet population used a smartphone to browse online. 

  Moreover, 76% of U.S. adults make purchases using their smartphones. 

  That means you need to ensure your site’s mobile experience is on-point to increase conversions. 

  Your site should use a mobile-first design, meaning it works perfectly on smartphones and then scales up for desktop users. 

  Trust the data

  Opinions are a fantastic form of inspiration for new A/B tests. But they should never be trusted over cold, hard data. If your test shows the opposite of what you and your team thought would happen, then trust the data and not yourself.

  With that in mind, ensure you collect qualitative and quantitative data during your experiments. Web analytics should always form the backbone of conversion tests, but don’t forget to also use heatmaps, screen recordings, and customer surveys. 

  Keep testing

  There’s no such word as “finished” in the world of A/B testing. Continual testing is key if you want to convert more website visitors. 

  Make sure you aren’t stopping tests prematurely, either. Make sure every A/B and multivariate test reaches a sample size that makes the test statistically significant. 

  Understand your users better with Matomo 

  Whether you run an e-commerce store, a SaaS company, or a service-based business, implementing these conversion rate optimisation best practices could be an easy way to lower your bounce rate and boost your conversion rates.

  But remember, best practices aren’t clear-cut rules. What works for one website may not work for yours. That’s why running your own tests and understanding your visitors’ behaviour is important. 

  Matomo’s web analytics platform is the perfect tool for doing just that. Not only does it come with the tools you need to optimise your conversion rate (like an A/B testing tool, heatmaps and session recordings), but you can also trust the data. Unlike Google Analytics 4 and other tools, Matomo doesn’t use data sampling meaning you have 100% accurate data from which to make better decisions. It’s GDPR compliant and can run cookieless, so no need for cookie consent banners (excluding in the UK and Germany).

  Discover how you can improve your website’s conversions with Matomo by starting a free 21-day trial, no credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• ffmpeg Non monotonous DTS, Previous DTS is always the same, audio microphone streaming [closed]

  5 février, par adrien gonzalez

  I'm using ffmpeg to stream audio from a microphone using rtp. I'm on Raspberry and use an external sound card (HifiBerry DAC + ADC Pro).
My goal is to stream audio with the lowest latency possible to others Raspberry reading this audio with ffplay. I try not to compress the audio flux and leave it untouched as wav 48000 Hz.
I encounter often some Non Monotonous DTS errors. When this happens I have a latency of hundred of milliseconds adding itself.
I tried to add the +igndts flag but it is not changing anything. Also tried +genpts flag.

  


  What is weird is that the previous DTS is always the same (201165 is the example below) and does not seems to change.
I looked on forums for answers but I'm unable to find one.

  


  Here is my bash command :

  


  ffmpeg -guess_layout_max 0 -re -f alsa -i hw -acodec pcm_s16le -ac 1 -payload_type 10 -f rtp rtp://192.168.1.152:5003

  


  And the result from the terminal :

  


  ffmpeg version 5.1.6-0+deb12u1+rpt1 Copyright (c) 2000-2024 the FFmpeg developers


built with gcc 12 (Debian 12.2.0-14)
  configuration: --prefix=/usr --extra-version=0+deb12u1+rpt1 --toolchain=hardened --incdir=/usr/include/aarch64-linux-gnu --enable-gpl --disable-stripping --disable-mmal --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sand --enable-sdl2 --disable-sndio --enable-libjxl --enable-neon --enable-v4l2-request --enable-libudev --enable-epoxy --libdir=/usr/lib/aarch64-linux-gnu --arch=arm64 --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-vout-drm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
Input #0, alsa, from 'hw':
  Duration: N/A, start: 1738663653.066577, bitrate: 1536 kb/s
  Stream #0:0: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (pcm_s16le (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
Output #0, rtp, to 'rtp://192.168.1.152:5003':
  Metadata:
    encoder         : Lavf59.27.100
  Stream #0:0: Audio: pcm_s16le, 48000 Hz, mono, s16, 768 kb/s
    Metadata:
      encoder         : Lavc59.37.100 pcm_s16le
SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 192.168.1.152
t=0 0
a=tool:libavformat LIBAVFORMAT_VERSION
m=audio 5003 RTP/AVP 10
b=AS:768

[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201160; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201155; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201149; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201142; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201134; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201124; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201114; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201102; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201089; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201075; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201060; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201044; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201027; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 201009; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 200990; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 200970; changing to 201165. This may result in incorrect timestamps in the output file.
[rtp @ 0x558b48ea90] Non-monotonous DTS in output stream 0:0; previous: 201165, current: 200949; changing to 201165. This may result in incorrect timestamps in the output file.


  


  I tried to add the +igndts flag but it is not changing anything. Also tried +genpts flag. I expected the DTS to restore itself but I still have the same issue

  


• ffmpeg : Unrecognized option 'alpha_quality'

  16 avril 2024, par László Monda

  I want to make transparent videos work in Safari, which doesn't support WebM for this purpose but only H265 with alpha transparency.

  


  According to this post, I used Shutter Encoder, but only some of its versions work for this purpose on Mac.

  


  Instead of using Shutter Encoder on Mac, I want to use ffmpeg on my Linux PC. Shutter Encoder uses the following command in the background :

  


  ffmpeg -threads 0 -hwaccel none -i input.mov -c:v hevc_videotoolbox -alpha_quality 1 -b:v 1000k -profile:v main -level 5.2 -map v:0 -an -pix_fmt yuva420p -sws_flags bicubic -tag:v hvc1 -metadata creation_time=2024-04-14T14:53:08.734684Z -y output.mp4

  


  which yields the following output on my PC :

  


  ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  WARNING: library configuration mismatch
  avcodec     configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libaribb24 --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc --enable-libsmbclient
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
Unrecognized option 'alpha_quality'.
Error splitting the argument list: Option not found


  


  When googling for "Unrecognized option 'alpha_quality'.", there are no results, which I find very odd.

  


  What's going on, and how can I make ffmpeg work for this purpose without Shutter Encoder ?