Recherche avancée

Sur d’autres sites (6740)

• What Are Website KPIs (10 KPIs and Best Ways to Track Them)

  3 mai 2024, par Erin

  Trying to improve your website’s performance ?

  Have you ever heard the phrase, “What gets measured gets managed ?”

  To improve, you need to start crunching your numbers.

  The question is, what numbers are you supposed to track ?

  If you want to improve your conversions, then you need to track your website KPIs.

  In this guide, we’ll break down the top website KPIs you need to be tracking and how you can track them so you can double down on what’s working with your website (and ditch what’s not).

  Let’s begin.

  What are website KPIs ?

  Before we dive into website KPIs, let’s define “KPI.”

  A KPI is a key performance indicator.

  You can use this measurable metric to track progress toward a specific objective.

  A website KPI is a metric to track progress towards a specific website performance objective.

  

  Website KPIs help your business identify strengths and weaknesses on your website, activities you’re doing well (and those you’re struggling with).

  Web KPIs can give you and your team a target to reach with simple checkpoints to show you whether you’re on the right track toward your goals.

  By tracking website KPIs regularly, you can ensure your organisation performs consistently at a high level.

  Whether you’re looking to improve your traffic, leads or revenue, keeping a close eye on your website KPIs can help you reach your goals.

  10 Website KPIs to track

  If you want to improve your site’s performance, you need to track the right KPIs.

  While there are plenty of web analytics solutions on the market today, below we’ll cover KPIs that are automatically tracked in Matomo (and don’t require any configuration).

  Here are the top 10 website KPIs you need to track to improve site performance and grow your brand :

  1. Pageviews

  Website pageviews are one of the most important KPIs to track.

  What is it exactly ?

  It’s simply the number of times a specific web page has been viewed on your site in a specific time period.

  For example, your homepage might have had 327 pageviews last month, and only 252 this month. 

  This is a drop of 23%. 

  A drop in pageviews could mean your search engine optimisation or traffic campaigns are weakening. Alternatively, if you see pageviews rise, it could mean your marketing initiatives are performing well.

  High or low pageviews could also indicate potential issues on specific pages. For example, your visitors might have trouble finding specific pages if you have poor website structure.

  

  2. Average time on page

  Now that you understand pageviews, let’s talk about average time on page.

  This is simple : it’s the average amount of time your visitors spend on a particular web page on your site.

  This isn’t the average time they spend on your website but on a specific page.

  If you’re finding that you’re getting steady traffic to a specific web page, but the average time on the page is low, it may mean the content on the page needs to be updated or optimised.

  Tracking your average time on page is important, as the longer someone stays on a page, the better the experience.

  This isn’t a hard and fast rule, though. For specific types of content like knowledge base articles, you may want a shorter period of time on page to ensure someone gets their answer quickly.

  3. Bounce rate

  Bounce rate sounds fun, right ?

  Well, it’s not usually a good thing for your website.

  A bounce rate is how many users entered your website but “bounced” away without clicking through to another page.

  Your bounce rate is a key KPI that helps you determine the quality of your content and the user experience on individual pages.

  You could be getting plenty of traffic to your site, but if the majority are bouncing out before heading to new pages, it could mean that your content isn’t engaging enough for your visitors.

  Remember, like average time on page, your bounce rate isn’t a black-and-white KPI.

  A higher bounce rate may mean your site visitors got exactly what they needed and are pleased.

  But, if you have a high bounce rate on a product page or a landing page, that is a sign you need to optimise the page.

  4. Exit rate

  Bounce rate is the percentage of people who left the website after visiting one page.

  Exit rate, on the other hand, is the percentage of website visits that ended on a specific page.

  For example, you may find that a blog post you wrote has a 19% exit rate and received 1,000 visits that month. This means out of the 1,000 people who viewed this page, 190 exited after visiting it.

  On the other hand, you may find that a second blog post has 1,000 pageviews, but a 10% exit rate, with only 100 people leaving the site after visiting this page.

  What could this mean ?

  This means the second page did a better job keeping the person on your website longer. This could be because :

  • It had more engaging content, keeping the visitors’ interest high
  • It had better internal links to other relevant pieces of content
  • It had a better call to action, taking someone to another web page

  If you’re an e-commerce store and notice that your exit rate is higher on your product, cart or checkout pages, you may need to adjust those pages for better conversions.

  

  5. Average page load time

  Want to know another reason you may have a high exit rate or bounce rate on a page ?

  Your page load time.

  The average page load time is the average time it takes (in seconds) from the moment you click through to a page until it has fully rendered within your browser.

  In other words, it’s the time it takes after you click on a page for it to be fully functional.

  Your average load time is a crucial website KPI because it significantly impacts page performance and the user experience.

  How important is your page load time ?

  Nearly 53% of website visitors expect e-commerce pages to load in 3 seconds or less.

  You will likely lose visitors if your pages take too long to load.

  You could have the best content on a web page, but if it takes too long to load, your visitors will bounce, exit, or simply be frustrated.

  6. Conversions

  

  Conversions.

  It’s one of the most popular words in digital marketing circles.

  But what does it mean ?

  A conversion is simply the number of times someone takes a specific action on your website.

  For example, it could be wanting someone to :

  • Read a blog post
  • Click an external link
  • Download a PDF guide
  • Sign up to your email list
  • Comment on your blog post
  • Watch a new video you uploaded
  • Purchase a limited-edition product
  • Sign up for a free trial of your software

  To start tracking conversions, you need to first decide what your business goals are for your website.

  With Matomo, you can set up conversions easily through the Goals feature. Simply set up your website goals, and Matomo will automatically track the conversions towards that objective (as a goal completion).

  Simply choose what conversion you want to track, and you can analyse when conversions occur through the Matomo platform.

  7. Conversion rate

  

  Now that you know what a conversion is, it’s time to talk about conversion rate.

  This key website KPI will help you analyse your performance towards your goals.

  Conversion rate is simply the percentage of visitors who take a desired action, like completing a purchase, signing up for a newsletter, or filling out a form, out of the total number of visitors to your website or landing page.

  Understanding this percentage can help you plan your marketing strategy to improve your website and business performance.

  For instance, let’s say that 2% of your website visitors purchase a product on your digital storefront.

  Knowing this, you could tweak different levers to increase your sales.

  If your average order value is $50 and you get 100,000 visits monthly, you make about $100,000.

  Let’s say you want to increase your revenue.

  One option is to increase your traffic by implementing campaigns to increase different traffic sources, such as social media ads, search ads, organic social traffic, and SEO.

  If you can get your traffic to 120,000 visitors monthly, you can increase your revenue to $120,000 — an additional $20,000 monthly for the extra 20,000 visits.

  Or, if you wanted to increase revenue, you could ignore traffic growth and simply improve your website with conversion rate optimisation (CRO).

  CRO is the practice of making changes to your website or landing page to encourage more visitors to take the desired action.

  If you can get your conversion rate up to 2.5%, the calculation looks like this :

  100,000 visits x $50 average order value x 2.5% = $125,000/month.

  8. Average time spent on forms

  If you want more conversions, you need to analyse forms.

  Why ?

  Form analysis is crucial because it helps you pinpoint where users might be facing obstacles. 

  By identifying these pain points, you can refine the form’s layout and fields to enhance the user experience, leading to higher conversion rates.

  In particular, you should track the average time spent on your forms to understand which ones might be causing frustration or confusion. 

  The average time a visitor spends on a form is calculated by measuring the duration between their first interaction with a form field (such as when they focus on it) and their final interaction.

  Find out how Concrete CMS tripled their leads using Form Analytics.

  9. Play rate

  One often overlooked website KPI you need to be tracking is play rate.

  What is it exactly ?

  The percentage of visitors who click “play” on a video or audio media format on a specific web page.

  For example, if you have a video on your homepage, and 50 people watched it out of the 1,000 people who visited your website today, you have a play rate of 5%.

  Play rate lets you track whenever someone consumes a particular piece of audio or video content on your website, like a video, podcast, or audiobook.

  Not all web analytics solutions offer media analytics. However, Matomo lets you track your media like audio and video without the need for configuration, saving you time and upkeep.

  10. Actions per visit

  Another crucial website KPI is actions per visit.

  This is the average number of interactions a visitor has with your website during a single visit.

  For example, someone may visit your website, resulting in a variety of actions :

  • Downloading content
  • Clicking external links
  • Visiting a number of pages
  • Conducting specific site searches

  Actions per visit is a core KPI that indicates how engaging your website and content are.

  The higher the actions per visit, the more engaged your visitors typically are, which can help them stay longer and eventually convert to paying customers.

  Track your website KPIs with Matomo today

  Running a website is no easy task.

  There are dozens of factors to consider and manage :

  • Copy
  • Design
  • Performance
  • Tech integrations
  • And more

  But, to improve your website and grow your business, you must also dive into your web analytics by tracking key website KPIs.

  Managing these metrics can be challenging, but Matomo simplifies the process by consolidating all your core KPIs into one easy-to-use platform.

  As a privacy-friendly and GDPR-compliant web analytics solution, Matomo tracks 20-40% more data than other solutions. So you gain access to 100% accurate, unsampled insights, enabling confident decision-making.

  Join over 1 million websites that trust Matomo as their web analytics solution. Try it 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

  

• Rendering YUV420P ffmpeg decoded images on QT with OpenGL, only see black screen

  17 février 2019, par Lucas Zanella

  I’ve found this QT OpenGL Widget which should render a 420PYUV image on screen. I’m feeding a ffmpeg decoded buffer into its paintGL() function but I see nothing. Neither noises or correct images, only a black screen. I’m trying to understand why.

  I want to exclude the possibilities of other things being wrong, but I need to be sure first that my code will produce anything. I std::couted some bytes from the ffmpeg just to see if they were arriving and they were. So I should see at least some noise.

  Can you see anything wrong with my code that wouldn’t make it able to render images on screen ?

  This is the widget that should output the image :

  #include "XVideoWidget.h"
  
  #include <qdebug>
  
  #include <qtimer>
  
  #include <iostream>
  
  //自动加双引号
  
  #define GET_STR(x) #x
  
  #define A_VER 3
  
  #define T_VER 4
  
  
  
  //顶点shader
  
  const char *vString = GET_STR(
  
      attribute vec4 vertexIn;
  
      attribute vec2 textureIn;
  
      varying vec2 textureOut;
  
      void main(void)
  
      {
  
          gl_Position = vertexIn;
  
          textureOut = textureIn;
  
      }
  
  );
  
  
  
  
  
  //片元shader
  
  const char *tString = GET_STR(
  
      varying vec2 textureOut;
  
      uniform sampler2D tex_y;
  
      uniform sampler2D tex_u;
  
      uniform sampler2D tex_v;
  
      void main(void)
  
      {
  
          vec3 yuv;
  
          vec3 rgb;
  
          yuv.x = texture2D(tex_y, textureOut).r;
  
          yuv.y = texture2D(tex_u, textureOut).r - 0.5;
  
          yuv.z = texture2D(tex_v, textureOut).r - 0.5;
  
          rgb = mat3(1.0, 1.0, 1.0,
  
              0.0, -0.39465, 2.03211,
  
              1.13983, -0.58060, 0.0) * yuv;
  
          gl_FragColor = vec4(rgb, 1.0);
  
      }
  
  
  
  );
  
  
  
  
  
  
  
  //准备yuv数据
  
  // ffmpeg -i v1080.mp4 -t 10 -s 240x128 -pix_fmt yuv420p  out240x128.yuv
  
  XVideoWidget::XVideoWidget(QWidget * parent)
  
  {
  
     // setWindowFlags (Qt::WindowFullscreenButtonHint);
  
    //  showFullScreen();
  
  
  
  }
  
  
  
  XVideoWidget::~XVideoWidget()
  
  {
  
  }
  
  
  
  //初始化opengl
  
  void XVideoWidget::initializeGL()
  
  {
  
      //qDebug() &lt;&lt; "initializeGL";
  
      std::cout &lt;&lt; "initializing gl" &lt;&lt; std::endl;
  
      //初始化opengl （QOpenGLFunctions继承）函数
  
      initializeOpenGLFunctions();
  
  
  
      this->m_F  = QOpenGLContext::currentContext()->functions();
  
  
  
      //program加载shader（顶点和片元）脚本
  
      //片元（像素）
  
      std::cout &lt;&lt; program.addShaderFromSourceCode(QOpenGLShader::Fragment, tString) &lt;&lt; std::endl;
  
      //顶点shader
  
      std::cout &lt;&lt; program.addShaderFromSourceCode(QOpenGLShader::Vertex, vString) &lt;&lt; std::endl;
  
  
  
      //设置顶点坐标的变量
  
      program.bindAttributeLocation("vertexIn",A_VER);
  
  
  
      //设置材质坐标
  
      program.bindAttributeLocation("textureIn",T_VER);
  
  
  
      //编译shader
  
      std::cout &lt;&lt; "program.link() = " &lt;&lt; program.link() &lt;&lt; std::endl;
  
  
  
      std::cout &lt;&lt; "program.bind() = " &lt;&lt; program.bind() &lt;&lt; std::endl;
  
  
  
      //传递顶点和材质坐标
  
      //顶点
  
      static const GLfloat ver[] = {
  
          -1.0f,-1.0f,
  
          1.0f,-1.0f,
  
          -1.0f, 1.0f,
  
          1.0f,1.0f
  
      };
  
  
  
      //材质
  
      static const GLfloat tex[] = {
  
          0.0f, 1.0f,
  
          1.0f, 1.0f,
  
          0.0f, 0.0f,
  
          1.0f, 0.0f
  
      };
  
  
  
      //顶点
  
      glVertexAttribPointer(A_VER, 2, GL_FLOAT, 0, 0, ver);
  
      glEnableVertexAttribArray(A_VER);
  
  
  
      //材质
  
      glVertexAttribPointer(T_VER, 2, GL_FLOAT, 0, 0, tex);
  
      glEnableVertexAttribArray(T_VER);
  
  
  
      //glUseProgram(&amp;program);
  
      //从shader获取材质
  
      unis[0] = program.uniformLocation("tex_y");
  
      unis[1] = program.uniformLocation("tex_u");
  
      unis[2] = program.uniformLocation("tex_v");
  
  
  
      //创建材质
  
      glGenTextures(3, texs);
  
  
  
      //Y
  
      glBindTexture(GL_TEXTURE_2D, texs[0]);
  
      //放大过滤，线性插值   GL_NEAREST(效率高，但马赛克严重)
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
  
      //创建材质显卡空间
  
      glTexImage2D(GL_TEXTURE_2D, 0, GL_RED, width, height, 0, GL_RED, GL_UNSIGNED_BYTE, 0);
  
  
  
      //U
  
      glBindTexture(GL_TEXTURE_2D, texs[1]);
  
      //放大过滤，线性插值
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
  
      //创建材质显卡空间
  
      glTexImage2D(GL_TEXTURE_2D, 0, GL_RED, width/2, height / 2, 0, GL_RED, GL_UNSIGNED_BYTE, 0);
  
  
  
      //V
  
      glBindTexture(GL_TEXTURE_2D, texs[2]);
  
      //放大过滤，线性插值
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
  
      glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
  
      //创建材质显卡空间
  
      glTexImage2D(GL_TEXTURE_2D, 0, GL_RED, width / 2, height / 2, 0, GL_RED, GL_UNSIGNED_BYTE, 0);
  
  
  
      ///分配材质内存空间
  
      datas[0] = new unsigned char[width*height];     //Y
  
      datas[1] = new unsigned char[width*height/4];   //U
  
      datas[2] = new unsigned char[width*height/4];   //V
  
  }
  
  
  
  //刷新显示
  
  void XVideoWidget::paintGL(unsigned char**data)
  
  //void QFFmpegGLWidget::updateData(unsigned char**data)
  
  {
  
      std::cout &lt;&lt; "painting!" &lt;&lt; std::endl;
  
      memcpy(datas[0], data[0], width*height);
  
      memcpy(datas[1], data[1], width*height/4);
  
      memcpy(datas[2], data[2], width*height/4);
  
  
  
      glActiveTexture(GL_TEXTURE0);
  
      glBindTexture(GL_TEXTURE_2D, texs[0]); //0层绑定到Y材质
  
      //修改材质内容(复制内存内容)
  
      glTexSubImage2D(GL_TEXTURE_2D, 0, 0, 0, width, height, GL_RED, GL_UNSIGNED_BYTE, datas[0]);
  
      //与shader uni遍历关联
  
      glUniform1i(unis[0], 0);
  
  
  
  
  
      glActiveTexture(GL_TEXTURE0+1);
  
      glBindTexture(GL_TEXTURE_2D, texs[1]); //1层绑定到U材质
  
                                             //修改材质内容(复制内存内容)
  
      glTexSubImage2D(GL_TEXTURE_2D, 0, 0, 0, width/2, height / 2, GL_RED, GL_UNSIGNED_BYTE, datas[1]);
  
      //与shader uni遍历关联
  
      glUniform1i(unis[1],1);
  
  
  
  
  
      glActiveTexture(GL_TEXTURE0+2);
  
      glBindTexture(GL_TEXTURE_2D, texs[2]); //2层绑定到V材质
  
                                             //修改材质内容(复制内存内容)
  
      glTexSubImage2D(GL_TEXTURE_2D, 0, 0, 0, width / 2, height / 2, GL_RED, GL_UNSIGNED_BYTE, datas[2]);
  
      //与shader uni遍历关联
  
      glUniform1i(unis[2], 2);
  
  
  
      glDrawArrays(GL_TRIANGLE_STRIP,0,4);
  
      qDebug() &lt;&lt; "paintGL";
  
  }
  
  
  
  
  
  // 窗口尺寸变化
  
  void XVideoWidget::resizeGL(int width, int height)
  
  {
  
      m_F->glViewport(0, 0, width, height);
  
  
  
      qDebug() &lt;&lt; "resizeGL "&lt;code></iostream></qtimer></qdebug>

  Here’s a bit of code from my MainWindow :

  MainWindow::MainWindow(QWidget *parent):
  
      QMainWindow(parent)
  
      {
  
          FfmpegDecoder* ffmpegDecoder = new FfmpegDecoder();
  
          if(!ffmpegDecoder->Init()) {
  
              std::cout << "problem with ffmpeg decoder init"  << std::endl;
  
          } else {
  
              std::cout << "fmmpeg decoder initiated"  << std::endl;
  
          }
  
          XVideoWidget * xVideoWidget = new XVideoWidget(parent);
  
          ffmpegDecoder->setOpenGLWidget(xVideoWidget);
  
  
  
          mediaStream = new MediaStream(uri, ffmpegDecoder, videoConsumer);//= new MediaStream(uri, ffmpegDecoder, videoConsumer);
  
          //...
  
      }
  
      void MainWindow::run()
  
      {
  
          mediaStream->receiveFrame();
  
      }

  My main.cpp makes sure my window run() method runs in the background.

      MainWindow w;
  
      w.setFixedSize(1280,720);
  
      w.show();
  
      boost::thread mediaThread(&MainWindow::run, &w);
  
      std::cout << "mediaThread running"  << std::endl;

  If someone wants to view the entire code, please feel free to visit the commit I just did : https://github.com/lucaszanella/orwell/tree/bbd74e42bd42df685bacc5d51cacbee3a178689f

• Enhanced Privacy Control : Matomo’s Guide for Consent Manager Platform Integrations

  13 février, par Alex Carmona — Development, Latest Releases

  In today’s digital landscape, protecting user privacy isn’t just about compliance—it’s about building trust and demonstrating respect for user choices. Even though you can use Matomo without requiring consent when properly configured in compliance with privacy regulations, we’re excited to introduce a new Consent Manager Platforms (CMP) category on our Integrations page to make it easier than ever to implement privacy-respecting analytics.

  What’s a consent manager platform ?

  A Consent Management Platform (CMP) is a tool that helps websites collect, manage, and store user consent for data tracking and cookies in compliance with privacy regulations like GDPR and CCPA. A CMP allows users to choose which types of data they want to share, ensuring transparency and respecting their privacy preferences. By integrating a CMP with Matomo, organisations can make sure that analytics tracking occurs only after obtaining explicit user consent.

  

  Remember, you can configure Matomo to remain fully GDPR compliant, without requiring user consent.

  Why consent management matters

  With privacy regulations reshaping data collection practices daily, organisations need to ensure that analytics data is gathered only after users have explicitly given their consent. Integrating Matomo with a Consent Management Platform helps you :

  • Strengthen regulatory compliance
  • Enhance user trust through transparency
  • Clearly document consent choices
  • Simplify privacy management

  By making consent management seamless, you can maintain compliance while delivering a privacy-first experience to your users.

  Introducing our CMP integration options

  We’ve carefully curated integrations with leading Consent Management Platforms that work seamlessly with Matomo Analytics and Matomo Tag Manager. Our supported platforms include :

  

  Supported consent management platforms

  • Osano – Comprehensive consent management with global regulation support
  • Cookiebot – Advanced cookie consent and compliance automation
  • CookieYes – User-friendly consent management solution
  • Tarte au Citron – Open-source consent management tool
  • Klaro – Privacy-focused consent management system
  • OneTrust – Enterprise-grade privacy management platform
  • Complianz for WordPress – Specialised WordPress consent solution

  Each platform provides unique features and compliance options, allowing you to select the best fit for your privacy needs.

  Getting started with simplified implementation

  Ready to enhance your privacy compliance ? We’ve made the integration process straightforward, so you can set up a privacy-compliant analytics environment in just a few steps. Here’s how to begin :

  1. Explore our new CMP category on the Integrations page
  2. Select and implement the CMP that best suits your needs
  3. Check our implementation guides for step-by-step instructions
  4. Configure your consent management settings in Matomo
  5. Start collecting analytics data with proper consent management

  Moving Forward

  As privacy regulations evolve and user expectations around data protection grow, proper consent management is more important than ever. With Matomo’s new CMP integrations, you can ensure compliance while maintaining full control over your analytics data.

  Visit our Integrations page and our Implementation guides today to explore these privacy-enhancing solutions and take the next step in your privacy-first analytics journey.