User blog comment:Rappy 4187/Technical Update: July 20, 2016/@comment-26154973-20160721213248/@comment-24473195-20160723162114

> But the profiler can't tell inefficiencies from just a lot of operations in general, which is what I see in the July 20th NewPP limit report.

The profiler just provides hints to what may be an issue. It is up to the lua scripters to evaluate their code and fix performance bottlenecks as Kirkburn notes.

>If the page is long by design, then I don't see how we can do anything to improve parser speed other than loading sections of the page via AJAX, which would throw mobile users out the window

Sounds like you want to have your cake and eat it too. Huge pages (especially with lots of images) are bad in general, and  often fail to render on mobile anyway because of device memory limits, data requirements, and bad internet connections.

I'd advise you to also read: https://phabricator.wikimedia.org/T21262. While lua may be partly to blame for nothing showing up at all, there are also templates being used on that page.