Recherche avancée

Sur d’autres sites (7583)

• 9 Form Optimisation Tips to Convert More Visitors

  15 février 2024, par Erin

  Forms might seem boring — that is, until you realise how powerful they are.

  No forms mean no leads.

  No leads mean no sales.

  No sales means you’ll run out of business.

  So, what do you do ?

  Optimise forms to land more leads.

  They’re a critical part of the sales funnel.

  Forms have many different purposes and can be used to :

  • Contact a company
  • Sign up for a newsletter
  • Request a demo
  • Start a free trial
  • And more

  If you want to get more leads (and ultimately more sales), then you need to optimise your forms.

  This guide will show you exactly how to do that (so you can start getting more conversions today). 

  What is form optimisation ?

  Before we dive into form optimisation, let’s back up a bit.

  Form conversion is our primary focus.

  Your form conversion rate is the percentage of visitors who submit a form divided by the total number of visitors who started the form times one hundred.

  For example, if 5,000 people started filling out your form this month and 350 submitted the form, the conversion rate would be : 

  350 / 5,000 x 100 = 7%

  So, what’s form optimisation ?

  

  It’s simply improving your forms to increase conversion rates.

  For most people, form conversion is all about increasing leads.

  Before you begin optimising your forms, it’s important you understand what’s good (and what’s not good) when it comes to form conversions.

  The average form conversion rate across all industries is 2.9%.

  This means you should expect about 3 out of every 100 visitors who start your form to submit it.

  If your form conversion is lower — or hovering around this number — then it’s important to start optimising now.

  With Matomo, you can track your form conversions with Matomo Form Analytics. Gain powerful insights into how your visitors interact with your forms with our intuitive dashboard.

  Why it’s important to optimise your forms

  Most people hear the word “forms” and think it’s boring.

  But forms are the doorway to leads.

  If you want to generate more sales, then you need to generate great forms.

  Here are five reasons you need to optimise your forms today :

  

  1. Improve conversions

  Form optimisation is really just conversion optimisation.

  But, instead of optimising and improving your site to directly improve sales conversions, you’re increasing lead conversions.

  Every smart website owner uses forms to draw people in further.

  The reality is that most of your website visitors will never return to your site.

  This means you need to do everything you can to grab their contact information so you can continue marketing to them day in and day out.

  Otherwise, you’ll lose them forever.

  When you know how to optimise your forms, you’ll be able to get a higher percentage of form viewers to fill it out.

  Higher conversions mean you get more leads, more customers, and ultimately more revenue.

  2. Capture more leads

  When you can increase your form conversion rate from 1% to 2%, it may seem insignificant.

  What’s a measly percentage point in conversions ?

  It’s a lot.

  When you’re dealing with traffic in the tens or hundreds of thousands each month, an increase in conversion rate by a whole percentile is massive.

  Let’s say you take your conversion rate from 2% to 3% on your form, and you have 70,000 visitors view the form each month.

  Well, if 1,400 people used to sign up to your email list each month at a 2% conversion rate, then at a 3% conversion rate, you’d get 2,100 new email signups every month.

  That’s a major difference.

  When you can improve your signup forms, you improve your lead generation (which is conversion rate optimisation). And the more leads you have, the more sales you’ll make in the long run.

  3. Get the most out of your traffic

  If your forms don’t perform well, then you’re wasting your time (and your traffic).

  By analysing your form data, you can quickly see what’s working and what’s not so you can optimise and improve the user experience (and your forms).

  For most people, this means getting more form viewers to fill out the form with their email and name.

  If 50,000 people visit your site each month, but only 1% of them fill out your form, you’re only getting 500 email signups per month.

  Rather than paying money to generate more traffic, why not just work on improving your website by implementing a better form ?

  If you can increase your form conversion rate to 2%, you will immediately go from 500 new subscribers per month to 1,000 per month.

  4. Spend less on acquisition

  If you’re able to get more form signups without having to generate more traffic, you just solved a pricey problem : acquisition costs.

  If you can now get 1,000 of your 50,000 visitors to sign up to your email list through a better form, then you doubled your signups.

  But that’s not all. You just cut your acquisition costs in half.

  If you spend $2,000 per month on acquisition but you’re able to get twice as many leads, then your acquisition costs are at 50% of what they used to be.

  This means you can pay the same amount but get twice as many leads.

  Or, you can pour even more money into acquisition since it’s now twice as effective so you can fuel growth even more.

  5. Grow revenue

  Forms generate revenue. It may not be direct (although, in some cases, it is). 

  But, forms will lead to sales.

  By placing optimised forms throughout your website at the right places, you will be able to capture a percentage of your visitors as leads, which means you’ll eventually make more sales.

  13 tips to optimise your forms for more conversions

  Now that you know what forms can do and why they’re important to grow your business, it’s time to dive into the best practices.

  Follow these 13 tips to ensure you’re getting the most out of your forms :

  

  1. Set form goals

  Your forms are hopeless without a goal.

  Before you set up a form on your website, ask yourself, “What am I trying to accomplish with this form ?”

  It could be :

  • Encouraging customers to reach out through a contact form
  • To get visitors to leave feedback on your product/service
  • Convert visitors into leads by giving you their email

  No matter what your goal is, make sure you’re clear on it ; otherwise, you won’t be as targeted and specific with your forms.

  Matomo Goals helps you set specific objectives for your marketing campaigns so you’re able to easily track conversions. Whether you’re looking to capture feedback or generate leads, you can leverage Matomo to see what’s working and what’s not in seconds.

  2. Remove or improve fields with high average time spent and high drop-off rates

  Delving into your Form Analytics provides invaluable insights into individual field performance. A crucial metric to focus on is the Average Time Spent. 

  If a field stands out with a significantly higher average time spent and experiences a high drop-off rate compared to others in the form, it’s a clear indicator that it’s causing frustration or confusion for your visitors.

  To address this, consider improving the field by converting it into a dropdown menu for easier completion or providing helpful text prompts. Alternatively, if the field isn’t essential, you might opt to remove it altogether.

  When you cut down on time spent and drop-offs, you’ll see your conversion rates go up.

  

  Here’s a standout example from Matomo’s Form Analytics feature : the “Overview of your needs” field is taking on average 1 minute and 37 seconds to complete. 

  To streamline this, we might want to consider a simple fix like converting it into a dropdown menu. This change would offer visitors a clearer and quicker way to select from options.

  

  Likewise, we observe that the “Overview of your needs” field experiences the highest drop-off rate, totaling 1,732 drop-offs. 

  With Form Analytics, it becomes clear what is needed to optimise forms and increase conversions.

  Try Matomo for Free

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

  Start for free

  No credit card required

  3. Start with the CTA

  When crafting and optimising your forms, you need to start with the end in mind. That’s why you need to start with your business goals.

  What are you trying to do with this form ? If you want to capture more emails, then make sure that’s very clear with the call to action (CTA).

  Start building your form by beginning with the CTA.

  For example : “Sign Up Now.”

  Once you have the action you want your potential customers to take, place it on the form. Then, you can work towards crafting the rest of the form.

  4. Put it above the fold

  If your visitors can’t find your form, they won’t fill it out. It’s plain and simple.

  You need to make sure your form is visible above the fold. This is the part of the screen that’s visible to your visitors once they land on your site (without needing to scroll down).

  Always remember to test this out on both desktop and mobile to ensure anyone (using laptops or a mobile device) will see your form upon landing on your site or page.

  Don’t forget about your mobile users. More people view mobile forms than desktop forms. 

  5. Put a CTA in the headline

  Your form needs to be clear.

  You have 1-3 seconds to communicate with your site visitors what your form is all about.

  For example, if you’re trying to get email signups with a lead magnet, then tell them the benefit quickly and concisely with a CTA in the headline, like this one :

  “Subscribe to Save 10% On Your Next Order”

  This is a great example of a headline-CTA combo that tells the visitor what to do and what they get out of it.

  Matomo’s behaviour analytics features like Session Recordings let you see where visitors are clicking and spending time. For example, if people are reading the headline, but not scrolling down to read the form, it’s probably a sign you need to test a different headline.

  6. Ensure you have the right fields

  Your form fields matter.

  What information are you trying to capture from your audience ?

  One beginner mistake people make is requiring too much information and including many fields in a form.

  You want to get as much data on your audience as possible, right ? Wrong.

  If you ask for too much information, people won’t fill it out, and it will harm the user experience. You need to make it super easy.

  If you want more emails to grow your list, then stick with someone’s email (and possibly their name as well). One line for a name. One line for an email address. Keep it simple.

  If you’re after SMS as well, don’t include it on the form. Instead, create a two-step form that pops up an SMS form after someone fills out the email form.

  Multi-step forms enable you to capture those emails easily (and still get a percentage to fill out the second form) without making it seem like too much work for your audience.

  Another path is to include optional fields (that users don’t have to fill out to click submit).

  Just keep in mind that shorter forms perform better than longer ones.

  If you make them too long, it feels like work for the user and will lead to lower completion rates.

  7. Always capture email address

  If you’re unsure of what information to capture (i.e. name, number, email, occupation, age, etc.), always stick to email.

  Email is used by over 4 billion people every single day, and it’s not going away anytime soon.

  When determining which fields to include, start with email.

  

  8. Test different buttons and copy

  You need to track your form performance if you want to get the best conversions.

  One of the best form elements to start testing is your button copy.

  In most cases, form completion buttons will have the word “submit” on them.

  But you don’t have to stick with this word.

  You can (and should) experiment with different submit button copy.

  Here are a few examples of replacement words for your action button :

  • Complete
  • Sign Up
  • Join now
  • Get started

  Remember to experiment with your action button. Try a different copy. Just keep it short.

  You can also try A/B testing your form by experimenting with different colours, copy, and more.

  

  In the example above from Matomo’s A/B testing feature, we found that changing the wording of our call to action made a big difference. The new “Apply Now” button performed much better, with a 3.6% conversion rate compared to just 1.7% for the original one.

  Try Matomo for Free

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

  Start for free

  No credit card required

  9. Test static vs. popup

  There are various types of online forms.

  The most common is the static form that just sits in one place and is always there.

  Another popular form type is the popup.

  This is where a form will appear based on a certain trigger like :

  • A certain amount of time on page
  • A certain distance scrolling down the page
  • If someone is a new or returning visitor

  Depending on the form software you use, you may be able to add conditional logic.

  Start tracking your form conversions

  Form optimisation is all about conversion rate optimisation.

  If you want to increase your conversions and generate more revenue, then you need to test out different forms and know how to optimise them.

  With Matomo, you can easily track, manage, and A/B test your forms so you can improve your conversions. 

  Try Matomo free for 21 days. 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

  

• Building my JAVA parameter array for FFMPEG

  29 janvier 2016, par user3541092

  FFmpeg Version : N-63893-gc69defd Copyright (c) 2000-2014 the FFmpeg developers
  built on Jul 16 2014 05:38:01 with gcc 4.6 (Debian 4.6.3-1)

  Machine : Amazon Linux t2.micro (free tier)

  Sample File : sample_iTunes.mov
  Sample File URL : https://support.apple.com/en-us/HT201549

  I’m trying to replicate the following FFmpeg command, using a string array and then pass this array into the Runtime.getRuntime().exec().

  ffmpeg -i file:/var/local/ffmpegtest/media_input/sample_iTunes.mov -pix_fmt yuv420p -c:v libx264 -vtag mp42 -metadata major_brand="mp42" -b:v 8000k -minrate 8000k -maxrate 10000k -ac 2 -strict experimental -c:a aac -b:a 256k -metadata:s:a:0 handler="Stereo" /var/local/ffmpegtest/media_output/sample_iTunes.mp4 -y

  NOTE : This works when I pass the full command, as a single string into Runtime.getRuntime().exec().

      String _cmd = "ffmpeg -i %s -pix_fmt yuv420p -c:v libx264 -vtag mp42 -metadata major_brand=\"mp42\" "
  
              + "-b:v 8000k -minrate 8000k -maxrate 10000k -ac 2 -strict experimental -c:a aac -b:a 256k -metadata:s:a:0 handler=\"Stereo\" %s -y";
  
      String _ffmpegCommand = String.format(_cmd, _inputFile, _outPutFile);
  
      p = Runtime.getRuntime().exec(_ffmpegCommand);
  
      BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
      String _line = null;
  
  
  
      while((_line = _reader.readLine()) != null) {
  
          lw.writeLine(_logPath + _logName, _line);
  
          System.out.println(_line);
  
      }

  I started out with just a basic parameter list. As I add add each additional parameter, I re-build the JAR file and upload it to my EC2 instance to test for any errors.

  The following string array works :

  try
  
          {
  
              String[] _params = {"ffmpeg",
  
                         "-i",
  
                         String.format("%s", _inputFile),
  
                         "-pix_fmt",
  
                         "yuv420p",
  
                         "-c:v",
  
                         "libx264",
  
                         String.format("%s", _outPutFile),
  
                         "-y"};
  
  
  
              p = Runtime.getRuntime().exec(_params);
  
  
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
          }
  
          catch (Exception e) {
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
  
  
          }

  However, when I continue to build the array with additional parameters, I begin to experience problems (lets add -vtag mp42) :

  try
  
          {
  
              String[] _params = {"ffmpeg",
  
                         "-i",
  
                         String.format("%s", _inputFile),
  
                         "-pix_fmt",
  
                         "yuv420p",
  
                         "-c:v",
  
                         "libx264",
  
                         "-vtag", // <---- New
  
                         "mp42", // <---  New
  
                         String.format("%s", _outPutFile),
  
                         "-y"};
  
  
  
              p = Runtime.getRuntime().exec(_params);
  
  
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
          }
  
          catch (Exception e) {
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
  
  
          }

  Error Message : Could not write header for output file #0 (incorrect codec parameters ?) : Invalid data found when processing input

  Full Log output for errant trail run :

  29 Jan 2016 03:45:09 UTC - Running FFMpeg...
  
  29 Jan 2016 03:45:09 UTC -  Input file: /var/local/ffmpegtest/media_input/sample_iTunes.mov
  
  29 Jan 2016 03:45:09 UTC -  Output file: /var/local/ffmpegtest/media_output/sample_iTunes.mp4
  
  29 Jan 2016 03:45:09 UTC - ffmpeg version N-63893-gc69defd Copyright (c) 2000-2014 the FFmpeg developers
  
  29 Jan 2016 03:45:09 UTC -   built on Jul 16 2014 05:38:01 with gcc 4.6 (Debian 4.6.3-1)
  
  29 Jan 2016 03:45:09 UTC -   configuration: --prefix=/root/ffmpeg-static/64bit --extra-cflags='-I/root/ffmpeg-static/64bit/include -static' --extra-ldflags='-L/root/ffmpeg-static/64bit/lib -static' --extra-libs='-lxml2 -lexpat -lfreetype' --enable-static --disable-shared --disable-ffserver --disable-doc --enable-bzlib --enable-zlib --enable-postproc --enable-runtime-cpudetect --enable-libx264 --enable-gpl --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-gray --enable-libass --enable-libfreetype --enable-libopenjpeg --enable-libspeex --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-version3 --enable-libvpx
  
  29 Jan 2016 03:45:09 UTC -   libavutil      52. 89.100 / 52. 89.100
  
  29 Jan 2016 03:45:09 UTC -   libavcodec     55. 66.101 / 55. 66.101
  
  29 Jan 2016 03:45:09 UTC -   libavformat    55. 43.100 / 55. 43.100
  
  29 Jan 2016 03:45:09 UTC -   libavdevice    55. 13.101 / 55. 13.101
  
  29 Jan 2016 03:45:09 UTC -   libavfilter     4.  8.100 /  4.  8.100
  
  29 Jan 2016 03:45:09 UTC -   libswscale      2.  6.100 /  2.  6.100
  
  29 Jan 2016 03:45:09 UTC -   libswresample   0. 19.100 /  0. 19.100
  
  29 Jan 2016 03:45:09 UTC -   libpostproc    52.  3.100 / 52.  3.100
  
  29 Jan 2016 03:45:09 UTC - Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/local/ffmpegtest/media_input/sample_iTunes.mov':
  
  29 Jan 2016 03:45:09 UTC -   Metadata:
  
  29 Jan 2016 03:45:09 UTC -     major_brand     : qt  
  
  29 Jan 2016 03:45:09 UTC -     minor_version   : 537199360
  
  29 Jan 2016 03:45:09 UTC -     compatible_brands: qt  
  
  29 Jan 2016 03:45:09 UTC -     creation_time   : 2005-10-17 22:54:32
  
  29 Jan 2016 03:45:09 UTC -   Duration: 00:01:25.50, start: 0.000000, bitrate: 307 kb/s
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:0(eng): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 261 kb/s, 10 fps, 10 tbr, 3k tbn, 25 tbc (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:33
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Video Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : 3ivx D4 4.5.1
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 43 kb/s (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:34
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Sound Media Handler
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] using SAR=1/1
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX AVX2 FMA3 BMI1 BMI2
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] profile High, level 2.2
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] 264 - core 129 r2230 1cffe9f - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=10 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  29 Jan 2016 03:45:09 UTC - [mp4 @ 0x30c21a0] Tag mp42/0x3234706d incompatible with output codec id '28' ([33][0][0][0])
  
  29 Jan 2016 03:45:09 UTC - Output #0, mp4, to '/var/local/ffmpegtest/media_output/sample_iTunes.mp4':
  
  29 Jan 2016 03:45:09 UTC -   Metadata:
  
  29 Jan 2016 03:45:09 UTC -     major_brand     : qt  
  
  29 Jan 2016 03:45:09 UTC -     minor_version   : 537199360
  
  29 Jan 2016 03:45:09 UTC -     compatible_brands: qt  
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:0(eng): Video: h264 (libx264) (mp42 / 0x3234706D), yuv420p, 640x480 [SAR 1:1 DAR 4:3], q=-1--1, 10 fps, 90k tbn, 10 tbc (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:33
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Video Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : Lavc55.66.101 libx264
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:1(eng): Audio: aac (libvo_aacenc), 32000 Hz, mono, s16, 128 kb/s (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:34
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Sound Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : Lavc55.66.101 libvo_aacenc
  
  29 Jan 2016 03:45:09 UTC - Stream mapping:
  
  29 Jan 2016 03:45:09 UTC -   Stream #0:0 -> #0:0 (mpeg4 (native) -> h264 (libx264))
  
  29 Jan 2016 03:45:09 UTC -   Stream #0:1 -> #0:1 (aac (native) -> aac (libvo_aacenc))
  
  29 Jan 2016 03:45:09 UTC - Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input

• Anomalie #2025 : Surlignage intempestif

  20 septembre 2011, par tetue -

  Ceinture et bretelles : la classe pas_surlignable est passée par défaut sur toutes les balises de la dist depuis Changeset 50225 (c’est inutile, du coup ?)