Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I am using performance analyser to analyse the report performance, but after recording it and export it to the JSON file and using that JSON into the power bi i dont get the tab/pages names so i can go through the particular page who is taking more time to load...any idea how to find particular page load time?
In the dax studio also the name of the tabs/Pages are not displayed.
Solved! Go to Solution.
Hi @Krushnab85 -Performance Analyzer doesn't show page names directly in the JSON file, best approach is to run the Performance Analyzer separately for each page, export the results, and compare them.Repeat this process for each page separately, so each JSON file corresponds to one page.
Though DAX Studio does not directly show page names but to identify the slow queries and optimize them we can use it.
Ref:
Solved: Performance analyzer - Microsoft Fabric Community
Solved: Performance Analyzer / Dax Studio - Microsoft Fabric Community
Hope this information helps.
Proud to be a Super User! | |
Hi @Krushnab85
To analyze the performance of specific pages in your Power BI report and identify which pages are taking more time to load, you can follow these steps:
Record Performance:
Export Performance Data:
The JSON file contains detailed performance data, but it doesn’t directly include page names. To map the performance data to specific pages, you can follow these steps:
Open the JSON File:
Identify Visual Load Times:
Map Visuals to Pages:
DAX Studio can help you analyze query performance, but it doesn’t provide page names either. However, you can use it to identify slow-running queries and then manually correlate them to the visuals and pages in your report.
Create Bookmarks:
Record Performance with Bookmarks:
While the JSON file from Performance Analyzer and DAX Studio do not directly provide page names, you can manually correlate the performance data to specific pages by noting the order of navigation or using bookmarks. This approach requires some manual effort but can help you identify which pages are taking more time to load.
Hi @Krushnab85
To analyze the performance of specific pages in your Power BI report and identify which pages are taking more time to load, you can follow these steps:
Record Performance:
Export Performance Data:
The JSON file contains detailed performance data, but it doesn’t directly include page names. To map the performance data to specific pages, you can follow these steps:
Open the JSON File:
Identify Visual Load Times:
Map Visuals to Pages:
DAX Studio can help you analyze query performance, but it doesn’t provide page names either. However, you can use it to identify slow-running queries and then manually correlate them to the visuals and pages in your report.
Create Bookmarks:
Record Performance with Bookmarks:
While the JSON file from Performance Analyzer and DAX Studio do not directly provide page names, you can manually correlate the performance data to specific pages by noting the order of navigation or using bookmarks. This approach requires some manual effort but can help you identify which pages are taking more time to load.
Hi @Krushnab85 -Performance Analyzer doesn't show page names directly in the JSON file, best approach is to run the Performance Analyzer separately for each page, export the results, and compare them.Repeat this process for each page separately, so each JSON file corresponds to one page.
Though DAX Studio does not directly show page names but to identify the slow queries and optimize them we can use it.
Ref:
Solved: Performance analyzer - Microsoft Fabric Community
Solved: Performance Analyzer / Dax Studio - Microsoft Fabric Community
Hope this information helps.
Proud to be a Super User! | |
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 46 | |
| 42 | |
| 34 | |
| 31 | |
| 21 |
| User | Count |
|---|---|
| 133 | |
| 126 | |
| 95 | |
| 80 | |
| 65 |