How to explain a problem to the support?

Modified on Wed, 15 May 2024 at 04:11 PM

If you encounter a problem with the optimisations provided by Fasterize and you have been able to identify the cause, here is the procedure to follow to report it to us effectively:


Access the Fasterize Dashboard 

Log in to your account on the Fasterize dashboard.

Once logged in, click on the technical support widget in the bottom right-hand corner of your screen.


Fill in the reporting form

In the description text box, please provide :


  • Subject: Briefly describe the nature of the problem.
  • Type of problem: Select the type of problem from the drop-down list to help our team better understand the context.
  • Description: Clearly detail what's going wrong, include the URL concerned, a reproduction scenario, and if possible the Request ID associated with the problem.
  • Add screenshots: Attach screenshots of the problem observed to clearly illustrate the anomalies encountered.


Once you have provided all the information, submit the form.

Our technical support team will receive your request directly and process your ticket.


Why use the dashboard? 

Using the dashboard to report a problem enables more direct and structured transmission of the information needed for a quick and efficient resolution.


We're here to help you make the most of your experience with Fasterize and resolve any technical issues as quickly as possible.


By email

You can contact technical support by e-mail at support@fasterize.com, providing as much information as possible to help resolve your problem quickly.

Be sure to include the URL concerned, a detailed description of the problem, the reproduction scenario and relevant screenshots.

These details will help our team to diagnose and respond effectively to your request.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article