Context

The current website analysis execution limit is 30 seconds. For some websites, this time is not enough, causing the analysis to fail to complete in time.

Goal

Increase the allowed analysis execution time so that heavier websites can be processed correctly without premature timeout.

What to do

• Find the place where the current 30-second limit is set.
• Determine a reasonable new limit taking into account real long-running scenarios.
• Check for any additional timeouts at the level of the HTTP client, queue, worker, reverse proxy, or external service.
• Ensure timeout consistency across all layers involved in the analysis.
• Check the behavior in case of a truly hung or excessively long analysis.
• Add clear timeout handling so that the user receives a controlled result rather than an undefined error.
• Test on websites that previously did not fit within the 30-second limit.

Result

Website analyses that require more than 30 seconds complete successfully within the new limit, while truly hung operations are still safely aborted.

Acceptance Criteria

• The new limit has been applied across all necessary layers.
• Previously problematic websites pass the analysis.
• There are no infinitely hanging operations.
• Timeouts are handled predictably and clearly for the user.