Embedded Power BI report (publish to web) is suddenly very slow

[Gertjan]

Hi all, 

I have an embedded Power BI report with fake data that is published on the web. Since yesterday, the report is suddenly very slow. Even refreshing text labels takes a lot of time, so you can imagine what happens to slicers and graphs. 

The report isn't refreshed for months, this is not needed. There were no issues with this, until yesterday. More people in different countries experience the exact same issue. 

Some facts: 

- Clearing caches doesn't help

- The report works fine in the Power BI Service

- An embedded link in a website or portal (not published to web) works fine

- The dataset didn't change, since it doesn't need to be refreshed

- Another person even had the following error message: 

My question: is there anything Microsoft changed about public embedded links, because it is so slow?

Looking for help, thanks in advance.

[Anonymous · Accepted solution]

Thanks for the reply from @GilbertQ  , please allow me to provide another insight.
Hi @Gertjan ,

You can try copying the report and then Publish to Web.
You can then view the embedded report on your own, or share it with a select few people.

This is to troubleshoot if the report's performance is slow due to heavy usage of the report that has reached the query limit.

You can refer to the documentation to optimize your report.
Updates to Power BI Publish to web for better public reporting | Microsoft Power BI Blog | Microsoft...
Optimization guide for Power BI - Power BI | Microsoft Learn

You can also refer to the following thread.

Solved: Intensive use: will be tried again soon - Microsoft Fabric Community

Best Regards,
Dengliang Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Gertjan]

Hi @GilbertQ,

Thanks for your quick reply. It doesn't seem to be happening at specific times. I don't expect too many people using it at the same time, it could maybe be around 15 unique users, but that would really be an exception. 

Would that be an issue already?

[GilbertQ]

Hi @Gertjan 

The published web infrastructure runs on shared resources that this could potentially be wide. It is not running on the published web link. It could also be that the report is being heavily used. What happened if you try an access report later in the day, or when you know there's not a lot of people accessing the report? Does it then work?