Skip to content
Reporting bug practices Article contains How do we define a bug? Submitting bugs When reporting a bug, what information should be included Choose a non-generic subject describing what and where is failing Use plain English, don't use words that only a few might understand Avoid acronyms Is the problem observed persistent or temporary? Actual behaviour Steps to reproduce
Expected behaviour When possible, include logs, screenshots, video recordings, the app version, and any other supporting information Discussing root cause Geek and Poke fun The key to properly processing bugs (defects) is to report them effectively. Let’s then evaluate what a good bug report has to contain.
Continue reading “Reporting bug practices” 4 simple things you should do in optimising website loading performance Article contains Delay loading scripts for improved performanceReduce HTTP connections and download cost Consider download and execution costs Multiple scripts in one line can still result in multiple HTTP requests Be cautious when utilizing User Traffic Analytics Concatenation for efficient script delivery Brotli compression for faster page loading Boost website performance with HTTP/2 Latest update: Optimize the use of multiple SVGs Everyone wants their site to be loaded fast. It’s not only good from the SEO perspective but also from the user experience perspective. However, achieving fast loading website it’s that easy quite often. Some use a one-click solution to magically resolve all loading performance issues. Use that with caution as those won’t resolve all issues you may have.
Continue reading “4 simple things you should do in optimising website loading performance” Looking for automated testing for technical SEO? With SiteLint, you can help search engine spiders crawl and index your site more effectively.
Opens in a new window. Opens an external site. Opens an external site in a new window.
Real-user monitoring for Accessibility, Performance, Security, SEO & Errors (SiteLint)