It takes a long time for the nuxt.js server to render the first screen before it can be used.

after the original vue project has been modified by Nuxt.js, there are some problems.
when the first screen is loaded, the list data is obtained in asyncData and can be quickly rendered through the server, but at this time, the page is inoperable, and you need to wait for the header and other data not obtained in asyncData to be rendered on the client side.
I don"t know whether I need to wait for the client to render and then wait for the client to finish rendering on the first screen. Or is it because the client rendering is not complete (the list image has not been loaded yet)? How to solve the problem?
there is also a question about the pictures mentioned above. How to deal with lazy loading and unfinished loading when the image list is rendered on the server? Using @ load in the img tag of the page component to determine whether the picture has been loaded or not to switch between preset images does not seem to achieve the desired effect:

< template >

<img class="product-img" v-if="loading" :src="AList.product_img." @load="loadImg"  alt="img">
<img v-else src="~assets/image/timg.gif"   alt="img">

< / div >
< template >
< script >

export default{
    ...
    data(){
        return {
            loading:false
        }
    }
    ...
    loadImg () {
      this.loading = true
    },
}

< / script >
the actual effect is that the server rendering directly displays the list data image, and then (should be the client rendering) displays the preset image, and then redisplays the data image after the image has been loaded. The
picture is in the accounts sub-component, not in the

in the page routing level page.
Nov.02,2021
Menu