Recherche avancée

Sur d’autres sites (10509)

• Introducing Matomo SEO Web Vitals

  13 septembre 2021, par Ben Erskine — About, Analytics Tips, Plugins

  SEO Web Vitals track your critical website performance metrics and are a core element of SEO best practice. 

  Start using Matomo SEO Web Vitals to monitor your website performance, optimise your visitor experience, improve your search result rankings, and see how your site compares to your competitors.

  

  What are SEO Web Vitals ?

  Web Vitals are made up of a number of important metrics, such as your website’s page speed and loading performance, these metrics all play an important role in search engine optimisation. 

  The more technical terms for these metrics are Page Speed Score, First Contentful Paint (FCP), Final Input Delay (FID), Last Contentful Paint (LCP) and Cumulative Layout Shift (CLS).

  Why should you use SEO Web Vitals ?

  SEO Web Vitals are being used more and more by search engines such as Google to rank websites so they help ensure a great page experience for users who arrive via links from their search results. 

  By monitoring your SEO Web Vitals you can see how good or bad a single page performs and then prioritise the optimisation of strategically important pages to help improve the ranking position within search engine results.

  For ease of use you can receive regular reports in your email inbox and you can configure custom alerts to automatically notify you when a page score changes significantly. This saves time by not having to check page performance scores manually while ensuring you will be notified should there be any important change that needs to be actioned.

  You should use SEO Web Vitals to understand how your site performance is impacting your overall visitor experience.

  Four key benefits of using SEO Web Vitals :

  Improve your search result rankings

  • SEO Web Vitals are a core element of SEO best practice and directly impact your search rankings.
  • Pages that load quickly and are more stable deliver a better user experience, so they’re ranked higher by search engines.

  Optimise your website visitor experience

  • Know how quickly pages on your website load to ensure you deliver an optimal visitor experience.
  • Identify page stability issues and implement the changes needed to enhance your visitor experience.

  Automate your website performance monitoring

  • Have peace of mind knowing if your metrics decrease, you can find and fix the root cause quickly.
  • Configure performance alerts and get automated reports sent to you.

  Incorporate website performance into your competitor analysis

  • These performance metrics are essentially open for anyone to inspect, so you can measure and benchmark your site against competitors. 

  How can I improve my SEO Web Vitals ?

  There are so many ways to improve these performance metrics, here are five of the common contributing factors.

  1. Your page speed score is a weighted average of your other performance metrics, so focus on improving the underlying metrics that contribute to this score.
  2. Ensure you use a high quality web host with an appropriate plan for your level of traffic to help improve your FCP time.
  3. Try removing large elements that aren’t required on your page to improve your LCP time.
  4. Optimise against Total Blocking Time to Improve your FID score.
  5. Consider using a Layout Shift Debugger to improve Your CLS Score

  Guide to Matomo SEO Web Vitals

  For more information and to learn how to configure SEO Web Vitals in Matomo, check out our full guide to SEO Web Vitals.

  You will learn :

  • What’s required to measure your SEO Web Vitals
  • How to configure SEO Web Vitals
  • How to analyse your SEO Web Vitals
  • How to understanding SEO Web Vitals metrics
  • How to analyse your page’s SEO Web Vitals over time
  • How to improve your SEO Web Vitals
  • How to monitor changes in your scores with custom alerts

  Need more resources ?

  Matomo Plugin SEO Web Vitals

  Matomo SEO Web Vitals FAQs

• AWS MediaConvert fails when transcoding a video created from an iOS Safari WebRTC

  18 février 2021, par Node.JS

  I am trying to transcode a video using MediaConvert and I get the following error :

  


  


  Error message Demuxer : [ReadPacketData File read failed - end of file
hit at length [1105924]. Is file truncated ?]

  


  


  When I try to run ffmpeg command to get information about the file I see this :

  


  


  non monotonically increasing dts to muxer in stream

  


  


  I am wondering is there a configuration in MediaConvert that can correct the time stamps ?

  


  ➜  Downloads ffmpeg -i 2254.webm -hide_banner -f null /dev/null

[h264 @ 0x7fce2c81d400] Increasing reorder buffer to 1
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '2254.webm':
  Metadata:
    major_brand     : iso5
    minor_version   : 1
    compatible_brands: isomiso5hlsf
    creation_time   : 2021-02-17T19:33:56.000000Z
  Duration: 00:00:01.60, start: 0.000000, bitrate: 5535 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc), 1280x720, 5644 kb/s, 27.95 fps, 29.92 tbr, 600 tbn, 1200 tbc (default)
    Metadata:
      rotate          : 90
      creation_time   : 2021-02-17T19:33:56.000000Z
      handler_name    : Core Media Video
    Side data:
      displaymatrix: rotation of -90.00 degrees
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 187 kb/s (default)
    Metadata:
      creation_time   : 2021-02-17T19:33:56.000000Z
      handler_name    : Core Media Audio
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native))
  Stream #0:1 -> #0:1 (aac (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
Output #0, null, to '/dev/null':
  Metadata:
    major_brand     : iso5
    minor_version   : 1
    compatible_brands: isomiso5hlsf
    encoder         : Lavf58.45.100
    Stream #0:0(und): Video: wrapped_avframe, yuvj420p(progressive), 720x1280, q=2-31, 200 kb/s, 29.92 fps, 29.92 tbn, 29.92 tbc (default)
    Metadata:
      encoder         : Lavc58.91.100 wrapped_avframe
      creation_time   : 2021-02-17T19:33:56.000000Z
      handler_name    : Core Media Video
    Side data:
      displaymatrix: rotation of -0.00 degrees
    Stream #0:1(und): Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s (default)
    Metadata:
      creation_time   : 2021-02-17T19:33:56.000000Z
      handler_name    : Core Media Audio
      encoder         : Lavc58.91.100 pcm_s16le
[null @ 0x7fce2e008200] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8 >= 8
[null @ 0x7fce2e008200] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 31 >= 31
frame=   41 fps=0.0 q=-0.0 Lsize=N/A time=00:00:01.57 bitrate=N/A speed=19.9x    
video:21kB audio:128kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown


  


• Evolution #4301 (Fermé) : Permettre de ne pas installer les plugins_dist qui sont en option

  12 février 2021, par cedric -

  non non par défaut, si tu télécharges SPIP sur spip.net, c’est la distrib SPIP qu’on a éditorialement choisie avec certains plugins-dist.

  Tu peux les enlever manuellement, ou maintenir ton propre zip de spip dans les plugins-dist, ou avec d’autre, mais c’est un choix de packaging en amont, pas un choix d’installation.
  Donc oui #4300 est légitime car on voudrait qu’idéalement le core puisse tourner seul, sans rien d’autre, pour permettre justement d’autres packaging, mais non on veut pas proposer à l’installation de choisir ses plugins (en tout cas c’est pas une roadmap a court ni moyen terme)

  Je ferme car on a deja assez de boulot comme ça :)