Use Laravel to deliver all the public side content dynamically?

I have a very complicated member area for our registered members which gets about 250,000 unique visitors every day. The pages presented to each user are very dynamic. The same code base supports multiple dating domains for different sex and sexuality genres. The plan is rewrite the existing member area PHP code to use Laravel. At the same time, the public (non-logged in part) of these same sites are currently running at 1.5 million unique new visitors a day (this is unique visitors, not raw page counts and is expected to triple in the next few months). There is a plan in place to publish 100,000 of our profiles so that some of the information is visible on the public side of the site. The objective is to improve SEO rankings so the data only has to be updated about once a month. Google now ranks sites with slower response times lower in search results. The public area and the member area of the site are on different host names so it would be easy to have the member area hosted on different servers than the public area.

There are two solutions proposed:

a. Use Laravel to deliver all the public side content dynamically.

The advantage of the approach is that the code base is the same and easier to maintain.

The disadvantage is that using a framework will put more load than necessary on the servers when delivering public pages.

b. Use static html pages in the public area and create scripts that will publish the pages each month.

Advantage is that it is a lot faster and less server load.

Disadvantage is that it is an entirely new publishing system that would have to be built to support this.

Please suggest/help me which one is the best option to implement.